bal·lis·tic: physics of an object in motion; behaving like a projectile.
-ica: collection of things relating to a specific theme.
The Ballistica project is the foundation for the next generation of BombSquad. It will be debuting with the upcoming 1.5 release of the game and lays the foundation for some of the big changes coming in 2.0.
Head to the project wiki to get started, or learn more about the project below.
- BombSquad's codebase, and especially its scripting layer, have grown a lot over its lifetime, but not always in a 'designed' way. It was overdue for a major refactoring, which should keep it more maintainable for years to come. Examples of this include breaking up the monstrous twenty-six-thousand-line bsUI.py file into a much cleaner individual subpackages, updating all code from Python 2.7 to 3.7, and adding type annotations to the entire codebase.
- Provide modders and tinkerers with the best possible development environment
- I've spent a lot of time incorporating auto-formatters, type-checkers, linters, and smart IDEs into my development workflow and have found them to be an enormous help. By sharing my setup here I hope to make them easily accessible to everyone.
- Improve transparency
- I get a lot of "what's in the next update?" or "how is 2.0 coming?" questions. By working here in the open I hope to make many of these questions unnecessary.
- Increase community involvement
- Provide a single place for tracking issues related to the engine/game
- Allow people to submit their own bug fixes or improvements, making myself less of a bottleneck
- Migrate modding documentation to this repo's wiki, allowing other modders to add their own bits of wisdom
Frequently Asked Questions
Q: What's with this new name? Is BombSquad getting renamed?
A: No, BombSquad is still BombSquad. 'Ballistica' is simply the new name for the engine/app-framework. This way it can also be used for other game/app projects without causing confusion (though that is mostly theoretical at this point). As a modder, the biggest changes you will notice is 'ba' prefixes in the API instead of 'bs' and naming that follows Python PEP8 standards (underscores and lowercase instead of camel-case). So
bs.playSound(mySound)in the old system might look like
ba.playsound(my_sound)in the new. You may also see the word 'BallisticaCore' show up various places, which in actual releases gets replaced by 'BombSquad'.
Q: Does this mean BombSquad is open source?
A: Yes and no. All code contained in this repo is MIT licensed and free for use anywhere. This includes game scripts, pipeline tools, etc. Over time I hope to expand this to include at least some of the binary engine sources. Anything not directly contained in this repository, however, even if automatically downloaded by build scripts, is still proprietary and cannot be redistributed without explicit consent. This includes assets and game binaries. So in a nutshell: create and share mods to your heart's content, but please don't distribute your own complete copies of the game without permission. Please email firstname.lastname@example.org if you have any questions about this.
Q: Will my existing BombSquad 1.4.x mods still work?
A: Not 'out of the box'. All mods will need to be explicitly updated to work with the new ballistica apis in 1.5+. This may or may not be a significant amount of work depending on the mod. I would highly suggest tinkering around with some of the new features in 1.5 such as type-safe Python and dynamic assets before attempting to port any old mods, as some things are done significantly differently now. You may also want to consider simply sticking with 1.4 builds for a while longer, especially for server duties, since they will remain fully compatible with clients running 1.5. The new ballistica APIs may be changing significantly for at least a while as the dust settles, but they will be worth switching to in the end, I promise!