Files
Space-Theme/planning/rulebook_aufgaben.md
2026-02-09 00:05:29 +01:00

35 lines
2.0 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Rulebook offene Punkte Umsetzungs- & Doku-Plan
Quelle/SSOT: `docs/game_rulebook_v1_2.md`
## Ziele
- Rulebook-konforme Implementierung der fehlenden Mechaniken (Auto-Cost, Blueprint-Baukasten, Build-Queue).
- Vollständige, verständliche Entwickler-Dokumentation unter `docs/wiki/`.
## Aufgaben (geordnet)
1. [ ] Auto-Cost-Score/Budget-Mechanik definieren (Rulebook §10)
- [ ] Score-Modell pro Effect-Typ festlegen (produce/consume/convert/capacity_add/queue_slots_add/points_add/modifier_add/grant_capability).
- [ ] Ressourcen-Werttabelle übernehmen und in Score-Formel einbauen.
- [ ] Budget pro Blueprint-Kategorie (building/ship/research/race/specialization) definieren.
- [ ] Ableitung von cost/build_time/upkeep (monoton) spezifizieren.
- [ ] UI-Breakdown-Format (transparente Scores) definieren.
2. [ ] Blueprint-Effects/Requirements/Access-Regeln vollständig abbilden (Rulebook §7)
- [ ] Requirements: building_count, building_tag_count, research_level, has_capability, player_race_in/_not_in, player_spec_in/_not_in.
- [ ] Access: allowed_/blocked_races sowie allowed_/blocked_specializations.
- [ ] Capabilities/Unlocks: grant_capability & menu:* Mechanik dokumentieren.
3. [ ] Build-Queue/Queue-Slots-Workflow definieren (Rulebook §8)
- [ ] Queue-Slots-Formel: base_slots + Σ(queue_slots_add).
- [ ] Job-Start-Flow: update_resources → slots → requirements/access → auto-cost → resource withdraw → job anlegen.
- [ ] Job-Finish-Flow: apply count/level, job entfernen, optional Event/Report.
- [ ] Destroyable-Flag/ Bombard-Handling (Rulebook §9) für Gebäude berücksichtigen.
4. [ ] Dokumentation in `docs/wiki/` ergänzen
- [ ] Rulebook-Mechaniken als neue Seite (z.B. rulebook.md) oder Erweiterung bestehender Seiten dokumentieren.
- [ ] API-Seiten (blueprints/build_queue/economy/planet_generator) mit Regel- und Datenmodell-Details ergänzen.
- [ ] Verweise auf SSOT und Decision Log aufnehmen.
## Notizen/Entscheidungen
- TBD