Change Impact Guide
Practical guide to where to make changes in BattleScore and which other areas are likely to be affected.
Engineering
Impact Analysis
Change Safety
How to use this page
Start with the thing you want to change, then review:
- primary tables
- primary API folders
- primary frontend pages
- secondary areas likely to break
Change: race / faction / canonical unit data
| Area | Main places to look |
|---|---|
| SQL | race, factions, units, unit_aliases |
| API | meta, armies imports, units, factions, faction units |
| UI | armies, units, import pages, TO entrant armies |
| Admin | race_edit, faction_edit, faction_unit_edit |
Likely side effects: imports, army selectors, filters, stats, TO army linking.
Change: army creation or army structure
| Area | Main places to look |
|---|---|
| SQL | army_lists, army_units |
| API | armies, units, import commit endpoints |
| UI | armies, units, import pages |
| TO | event_entrant_armies |
Likely side effects: imports, game setup, TO entrant armies, performance stats.
Change: gameplay turn structure or score events
| Area | Main places to look |
|---|---|
| SQL | games, game_turns, game_player_turns, game_units, game_events |
| API | games, turns, events |
| UI | game_setup, game_play, game_breakdown, tournaments |
Likely side effects: play-state rendering, finalisation, breakdown views, standings.
Change: tournament scoring or standings
| Area | Main places to look |
|---|---|
| SQL | tournaments, tournament scoring tables, games |
| API | tournaments, to, games/finalise |
| UI | tournaments page, TO event edit, events/entrants flows |
| Admin | tournament_edit |
Likely side effects: round interpretation, standings history, event setup behaviour.
Change: user/auth/subscription logic
| Area | Main places to look |
|---|---|
| SQL | users, user_sessions, password_resets, email_verifications |
| API | auth, subscription, user |
| UI | login, signup, verify, forgot, reset, profile |
| Admin | users, user_edit, login |
Likely side effects: every surface, because auth and ownership are system-wide.
Highest-risk change areas
- Identity/auth
- Canonical unit/reference data
- Game event logic
- Tournament scoring systems
- Admin write endpoints
Recommended change process
- Start with the relevant SQL tables and data model docs
- Review the owning API endpoints
- Review all UI/TO pages that consume them
- Check admin tooling if reference/configuration is involved
- Update reference docs if the architecture or interactions change