One of our goals for version 0.4.0 of co.llide was to provide a small but fairly balanced set of building blocks, called modules, for all players to use in constructing ships. However, variety is the spice of life, and we plan to eventually release a large number of unlockable modules for players to add to their personal collections. In this post, I’ll be discussing some ideas for these future modules. I’ll also be talking about a potential problem that we face as designers, and one particular source of inspiration that we believe offers the solution.
Last week, we released version 0.3.0 of co.llide, unveiling the ship editor! Whereas in previous versions you could only play with a set of default designs, now you can build your own ships from an array of modules. Sharing your designs works exactly like sharing an arena. Copy the URL of your design and share it with your friends, who can then test, modify, save, and even use it in battle.
Give it a try here: http://co.llide.com/editor
The core concept behind co.llide is for players to be able to build and then pilot their own customized, physically simulated spaceships. This means that when a player stitches together a bunch of pieces into a ship, the game needs to figure out how that ship should move depending on player input. Ours is certainly not the first game to ever address this problem, but we thought an explanation of our specific solution would make an interesting post. But why just tell when I can show?