Scraps is a vehicle combat game where you build your vehicle from parts.
Scraps is a bit like the multiplayer melee mode in Interstate ’76, except you build your vehicle from the chassis up instead of just bolting on weapons and armour. It’s kind of like how you put stuff together in Stratosphere: Conquest Of The Skies except that it’s a vehicle instead of a floating platform.
Scraps is sort of like building a vehicle in LEGO Racers except that when you build your vehicle, every part actually does something and has mass and aerodynamics, instead of the result being mostly cosmetic. It’s something like Robot Wars, except you drive what you’ve created directly.
Scraps didn’t come out last century like everything above! It’s a game I’ve been thinking about and wanting to play for so long that I gave up waiting and I’m making it myself.
Scraps lets you create a vehicle that sucks. A car that falls over whenever it corners or only has enough power to fire its guns once a minute. It gives you a lot of power over what you’re creating. Do you trade speed for firepower? Do you add weapons at the expense of your power supply draining faster? What about armour? At the same time, it tries to avoid needless complexity like wiring components together, and tries to keep things intuitive. When you take out other players, you can scavenge their parts too.
Scraps is currently in development with no specific release date or final pricing. It will be sold at a reduced price at Alpha stage, building up to release. Purchase at any stage will grant access to the release version when it’s done. This is an indie game, currently a solo project, so don’t hold your breath – but it is coming.
TL;DR: It’s like Kerbal Space Program except the spaceships are vehicles and they fight. It is not a retro 2D platformer.
On Sunday I did some proper LAN play testing. The basic game mechanics are all working and synchronising nicely over the network. I've now got a whole lot of notes on minor bugs and issues, and game mechanics that need to be tweaked, but none of it is serious stuff. No crashes, no major synchronisation issues, no terrible problems with the game mechanics, and my playtesters didn't want to stop playing which has to be a good sign.
The game's still a ways from being publicly testable because I've got to set everything up in just the right way - player's can't join after a game starts yet, and they can't quit either. Cleaning up properly after people quit should be easy enough but correctly synchronising everything when people join mid-way through a game will be more difficult, mainly due to how players can transition between different states in the game as they're playing (in-game, evac in progress, build screen after evac, waiting for respawn...). That's not necessarily needed in time for demoing at events like PAX though.
I did a quick 1v1 playtest on Saturday and as I suspected, the DustBowl map was way too big for games with few players, so I threw together a sort of mini version in literally about an hour:
"SmallMap." It's sort of a figure 8 with a plain untextured bridge in the middle. This is not a map that'll be in the game, but something similar might be, just without being a blatant copy of the DustBowl map.
On Sunday I had a couple of people over to play a three-player game. The map actually played well apart from some awkward terrain around the bridge area. And here's some video of it!
Yes, I'm still using a 4:3 monitor. And a trackball mouse.