This is neat and - also - I like it.

Hey JarMustard, thanks for the feedback.

Yep, the Halos appear on everyone who is proven innocent by the clues only in Easy mode.
In Normal mode, they only appear on people you have directly accused.
Hard & Precarious mode do not keep track of anyone for you, so it's a real challenge.

I'll try to work in some ways to communicate this to the player, although I despise lengthy help screens and I feel ours is too verbose already

We are definitely going to work in more deaths, as well as a narrative to begin the game.

Thanks again for taking the time to play and giving such lengthy feedback, it really helps.

[Murder Mystery]

First things first, PLAY HERE:

http://www.kongregate.com/games/jotapeh/dr-precarious-case-of-the-deadly-party

Second: This is a Murder Mystery type of game. You play as Dr. Precarious and attempt to determine which of the people attending your lovely party is a murderer. Inspect the patrons, assess them to your liking, and then make an accusation of one of them. Every guess you make incorrectly will result in the horrific death of a partygoer.

Feedback is appreciated (that's why this is here!) In particular:

- Do you feel like we missed anything obvious/simple (in design, presentation, gameplay?)
- Do you enjoy the core mechanic? Is the game fun?
- Do you feel it is too difficult even on the easiest setting? Do you feel the Precarious difficulty is difficult enough or too easy?

Cheers everyone, looking forward to replies

what was your game droqen?

Definitely not Mario, anyway. I started with Tetris and it wasn't too bad. You're basically dealing with a 2D array of booleans and shifting things around every second or so. If you need you can even implement Tetris as a turn based game, where you have to press 'down' to make the block fall. That might simplify it

Cool, didn't get a chance to play yours. I did however play The Monster King's game which was pretty fun.

it's not so bad, though it struck me a monochrome planet rather than the moon due to the contrast.

A Picture taken through my crappy telescope

Awesome how'd you manage that?

It's weird when you read a comment like ^ and you know you're in the same room but you have no idea what that other person looks like so it's pretty much moot

See you folks later today.. I'll be rushing over after work. You'll recognize me as the guy wearing a button up shirt for no good reason. Also, a motorcycle helmet.

Fuckin' wallpaper'd

Some kinda meh photos.





Taken with iPhone 4, Camera+ app.

Sometimes the best way to learn someone's code is to delete it and write your own.

Yeah it's okay. I played it a bit when they had their 'secret' demo going around the net.

It's very cute and certainly decent time waster with a friend.

You had my girlfriend hooked for hours on this game, then she hit a nasty bug where she was stuck in an infinite loop of death.

Thanks all for the suggestions. I'm not sure I entirely yours, Triplefox, but it sounds very interesting (although it would require a significant rewrite of my existing game.)

Anyway, I was under time pressure so I went with a fairly simple system:

1. I set up a Transition in the first state, which attaches a screenshot of the state.
2. This is passed to a Singleton (let's call it TransitionManager for the sake of it) for storage.
2(b). The state terminates itself with a message noting which state should follow.
3. The next active state that knows about Transitions will pick up the last transition in the Singleton, attach itself and execute it.

This is really messy and isn't a permanent solution, but this game is very linear so it works. Once it's delivered and I have a little more downtime I'm going to look into a better way.

I can't believe I missed the release of this. Loving it. So many fantastic details.

Hey all, I'm sure there is an established solution for this but I'm a bit torn between a few ideas.

Basically I have my game which implements a state machine. States don't know about the game they're in, all they know is that they are instantiated and they know when to end themselves and which state should follow them based on how they ended.

States are created and destroyed independently by the state machine and never overlap. One will be terminated prior to the next one beginning.

Now my problem is of course I want to pass persistent data between the states. I've always done this with a Singleton, which is fairly dirty and doesn't seem like a great idea in all cases. It makes sense for things that should persist throughout the game (eg., maybe the World, or the Player, or something.)

But now I'm writing a transition manager that can do stuff like blur, crossfade, slide. All I need is a bitmap of the last frame of the terminated state and the new state to do this. I want states to be able to call a transition, die, and then the next state to pick up the bitmap frame of the last state (or if it blurred out, eg., the blurred image of the last frame of the transition.)

So I could easily do this with a TransitionManager sort of Singleton, but then I thought I should look into alternatives. Maybe there is a clean way to do a transition on a state, store the bitmap and pass it along to the next state. If the next state didn't know about transitions it would ignore it. If it did it could use it. I want to make this as decoupled as possible, and preferably I'd like the main state machine to know nothing about transitions.

Sorry if that was longwinded.. Anyone have ideas on this?

Well this is pretty rough.

It's going to be a very difficult four years.. I just don't understand how Canadians could possibly have voted in a man who literally broke every possible rule in the book.

Hey guys! Working on a bunch of illustrations for me and inanimate's card game.

I gotta say Jared I like this a lot more than your earlier stuff. This really knocks my proverbial socks off.