You might be wondering: why haven’t I been posting Stick Ninjas DevLog videos lately?
The reason is that I’ve been helping the folks over at Conatus Creative with River City Ransom: Underground.
Specifically I’m helping them with their network code. So when you sit down for some satisfying beat-em’-up action in River City, you won’t have to do it alone. Up to four people will be able to play in peer-to-peer co-op (there’s also local co-op).
Peer-to-peer is a different network model to what I’m using in Stick Ninjas, so that’s an exciting challenge. The peer-to-peer model we’ve gone with means that, on a low-latency connection, you get a game that is extremely responsive – perfect for the beat-em’-up genre.
Here’s me, about to beat-up some input-buffering latency:
(This fantastic sprite of me is from this announcement on the game’s Kickstarter)
River City Ransom: Underground is an officially licenced sequel to the NES game River City Ransom, originally released in 1989. It was backed on Kickstarter in October last year to the tune of $217 634 CAD.
Visit the River City Ransom website, or follow along on Twitter @RiverCityRansom.
I’ve shut down the Kickstarter campaign due to poor performance.
I’ve made a productivity tool called Connect for a Reason. It helps you avoid mindless web surfing. And I’m using Kickstarter to raise the funds to develop my internal prototype into a releasable product.
Removing the physics engine presence enables one-way platforms.
I’m now using the “topmost lines” algorithm that I demonstrated in the last episode to handle player movement.
Just a quick video showing my “topmost lines” algorithm and talking about how it will be used.
Today I take a detailed look at prediction glitches and how they happen.
Worked on server-side lag-buffer to smooth out jitter in the input packet stream.
Posted Tuesday 17 September 2013 to Stick Ninjas
| Comments Off
Currently I’m working on fixing prediction errors in Stick Ninjas.
I’ve been coming up with ideas for fortnightly videos I can do, to slot in between my DevLog videos. And what I came up with is the idea of “Let’s Examine…” videos.