An Adventure Game - WIP

[Nyhm]

Just a tidbit of advice - don't worry about performance until you've proven that it's necessary to tweak. That is, implement whatever you want using TCP, thread-per-connection handling, per-pixel (twitch) movement, full broadcast, etc. Then, figure out if it's to slow, and only speed up what is needed. Or, make game design decisions that work around the performance issues (maybe there's nothing wrong with discrete movement).

Navigation in my game isn't perfect, but it's fairly simple. Movement is, indeed, discrete steps, but the GUI fills in the step-by-step position with a smooth animation. That way, the networking doesn't care what pixel you're at; just what (much larger-grained) nav coord you're on.

Certainly it's good to think ahead when designing your architecture, but that'll come with experience. If you have the time to experiment, just take it step by step and learn along the way.

[Cruiser]

@Nyhm - Of course you're right. Many games fails because we programmers do too much "gold plating" and focus on the last 5 % of the game, instead of focusing on the gameplay.

Your suggestion about smooth animation transistion between tiles is defninitely something I'm thinking about, and is a very good suggestion. At least it could be an intermediate steps towards smooth movement.

If anybody tests the multiplayer code - please tell me how it "felt" :-).

[Nyhm]

I ran your game last night, but only ran one client. I think it felt the same as the prior version, which implies that the client-server code works fine. One time I swear I walked _through_ a zombie without attacking it, but maybe it side-stepped and I missed the movement (it was at night). I still became dominated by zombies in about 1 night.

Games published by our own members! Check 'em out!

[Cruiser]

Nice!! :-)))

@Nyhm - Thanks a lot for the feedback.

The "moving through a zombie" bug has been verified, will fix :-).