Spin Battle Simulator
Modelling spinning-top combat as a service, to see what falls out.
A Java service that models customisable spinning tops, their parts and loadouts behind a small REST interface — an exploration of the simulation, not a product.
Worth knowing
An experiment with no released build and no connection to any commercial toy brand. Names, parts and rules are generic.
What Spin Battle is
Spin Battle Simulator is an exploratory back-end: a Spring Boot service that models spinning-top combat as data. Parts, inventories and loadouts are first-class records, exposed through a small REST surface so different match models can be tried against the same equipment without rewriting anything. It exists to answer a question — how much of the feel of this kind of battle comes from the physics and how much from the combination rules — rather than to become a published game. It is listed here as laboratory work, with no build, no interface and no plan to ship.
What it does
- Parts, inventories and loadouts modelled as first-class records
- A small REST surface so match models can be swapped without rewriting equipment
- Java 21 on Spring Boot 3, built with Maven
A question, not a product
The interesting part of this kind of battle is not the collision maths on its own — it is how much of the outcome is already decided by the combination you brought. Modelling the equipment properly first, and the match second, is the only way to find out.
Getting Spin Battle
Spin Battle Simulator is still in development and is not distributed yet. It is roughly 25% of the way to a first public release.
At a glance
- Status
- Prototype
- Runs on
- Web
- Offline use
- Needs a connection
- Last updated
Privacy
A local development service with no deployment, no accounts and no user data.
Permissions
This project requires no special permissions.
Technical details
Technical details
Built with
How it is put together
- A Spring Boot service models parts, inventories and loadouts behind a small REST surface.
- An exploratory build: the physics and match model are the point, not a finished product.
Development workflow
Built through Codex.
Related projects
DropCore
Rotate. Drop. Chain. Break through.
Active DevelopmentAndroid · Windowsv0.2.0