Skip to content

Latest commit

 

History

History
46 lines (38 loc) · 2.63 KB

File metadata and controls

46 lines (38 loc) · 2.63 KB

Documentation

Use these topic guides to understand, change, create content for, and operate Globulation 2. Each index orders its tutorials, procedures, explanations, and references so you can start with an overview and follow the task you need.

Topics

Topic Start here
Development Setup, builds, tests, contribution, dependencies, troubleshooting
Architecture Engine responsibilities, simulation, rendering, persistence, compatibility
Features Gameplay and interface behavior, supported experiments
AI Opponents, implementation, configuration, evaluation, telemetry
Map generators Design, authoring, framework, controls, generator catalog
Assets Artwork, terrain, music, production workflows, provenance
Scripting Script authoring, execution model, APIs
Multiplayer Platform, identity, clients, rooms, relay, protocols
Browser Browser development, storage, rendering, transports, decisions
Mobile Android/iOS development, interaction requirements, verification
Hosting Local setup, production configuration, maintenance, recovery
Releases Packaging, distribution, store procedures
Tools Contributor tools and workflows across topics

Reader paths

  • Contributors: contribution guide, development, architecture, then the relevant subsystem. Repository instructions record the shared compatibility and review policies.
  • Content creators: assets, map generators, and scripting; feature references explain the behavior your content can configure.
  • Operators: hosting, multiplayer, and releases.
  • Players: public guides and downloads and the browser game. In-repo feature pages explain current capabilities and experimental controls.

Maintain the library

Follow the documentation maintenance guide. Licensing indexes code and asset notices. Support explains how to report a problem.

Keep temporary notes and draft narratives in ignored docs/.work/; keep generated review evidence in ignored root artifacts/. Attach evidence needed for review to the pull request or an accessible evidence branch. Git history preserves retired designs and reports; current guides describe maintained behavior.