piinecone

In this first round I want to see how players respond to the composure-driven knockdown system, and if they find the sample boss fight difficult enough to be interesting, but genuinely fair. In the background, I'm thinking about how to improve the training mode (it only kind of worked on my daughter), so the game can teach you how to play without telling you how to play.

My friend and I are trying to do this with a matching tool we've been working on lately. You describe what you're looking for (pay, schedule, etc.) and then you only hear about jobs that match your criteria:

1. Apply to US remote jobs on the east coast and mention working from Europe. I’ve had a lot of luck overlapping for half a day. Not so great in a leadership position though.

2. Contact colleagues you like working with at US companies and see if they’re open to working with you. Someone vouching for you on the inside helps a lot.

3. Specialize in something valuable, pitch contract work, and try to convert that to full-time (or part-time or whatever).

Plug: my friend and I made a thing to address this problem because we have it too:

I attempted the standard prediction/correction implementation used for deterministic movement systems and got it working for the deterministic aspects of the vehicle's movement system, but naturally couldn't make it work for the core, non-deterministic physics, as that will require fixing the timestep and probably doing other things I haven't thought about / don't understand yet.

For now, the system works like this:

- basic client vehicle movement is non-deterministic physx + deterministic overrides

- special moves are deterministic but client-predicted

- weapons systems are deterministic but client-predicted

- server-side anticheat model is derived from me moving around and generating believable movement curves so the server can check that any given client move it receives is appropriate given its history / state of the world

- server also (supposedly!) handles noclip and flying cheats (this was a fun month)

- clients predict hits, server authorizes them

- simulated proxies (other clients in your world) mostly move according to projective velocity blending[0], though there are special cases for some of the special moves (spins)

- collisions are blended between the replicated state of the world and the client's local simulation [1]

- probably most importantly, the server creates replay files during matches which the game coordinator/serving system scoops up and saves, so I can (at some point) generate useful statistics and review matches to detect and improve cheat handling

I would have loved to do the networked physics really right, like Rocket League did, but I couldn't quite pull it off (I'm one guy with kids and a job and just not enough brainpower!), so I opted for what I hope is "good enough" for a small project like this: give the client a great experience, put all vehicles and projectiles in mostly the same position at the same time in all worlds (since they're momentum-based entities latency-based predictions are usually quite accurate), run an anticheat model on the server, and save replays to find and review anomalies.

If the game does okay and people are enjoying it I will get that fixed timestep/rewind replay PR done.

I hope that was a good answer! Let me know if I can tell you anything else. Something I didn't mention here is the networked projectile movement, which was the most fun to work on. I plan to write about that, too, at some point.

I’ve been working on King of Kalimpong [0] on and off since playtesting a one-week prototype of it in 2014. I had no idea how much work a networked physics vehicle/movement shooter game would be. (I should have, I was 8 years into a programming career).

Working part-time was critical (for many reasons), but so was learning that progress is a product of discipline, not motivation, and that I needed to learn “infinite endurance” (I think that’s what Chris Hecker called it).

Once I adopted the perspective that I was some finite number of 3-4 hour blocks of concentration away from turning a goofy idea into a game that anyone could play, finishing became something that felt inevitable — as long as I kept going.

I’ll take the time to write about my experience after I release (which is now months instead of years away) in case any other game developers get anything out of it. Until then, thanks for another reminder that I’m not alone!