mlangkabel/dota_factory
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

name recipes after their process, not their product

Browse Source 
Recipe display names come from the id, so a recipe that shared its id with
its output item showed the item's name back to the player. Every recipe id
now names the process that runs it: iron_mining, quartz_reduction,
steel_rolling, chip_etching, the *_framing hulls, the *_kit module prefabs,
and the drop-only shortcuts as direct_rolling/-etching/-hardening.

The three shortcut unlock groups are renamed with their recipes, since a
group's name is derived from its id the same way.

Blueprints and replays store recipe ids, so files recorded before this
rename lose their miner and assembler recipe selections.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ne3mejABZoLWKLh8fgpM3x
This commit is contained in:
Malte Langkabel
2026-08-12 09:16:19 +02:00
parent bd8fe5157e
commit 8d0dd6f454
3 changed files with 61 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/balancing/derived.md
View File

@@ -44,9 +44,9 @@ move. Combat stats were tuned empirically against the arena suite in
| capital_core | 2 voidsteel + 1 capacitor_bank + 1 control_chip | 10 | 1 | 240 |
Shortcut recipes (drop-only; item threat stays defined by the base path
via the max rule): `shortcut_steel_plate` 3 iron_ore → 1 plate (2 s,
level 1), `shortcut_control_chip` 2 quartz → 1 chip (4 s, level 2),
`shortcut_hardened_steel` 4 iron_ingot → 1 hardened (8 s, level 2).
via the max rule): `direct_rolling` 3 iron_ore → 1 plate (2 s,
level 1), `direct_etching` 2 quartz → 1 chip (4 s, level 2),
`direct_hardening` 4 iron_ingot → 1 hardened (8 s, level 2).
Ratio curve realized: t1 all 1:1 (miner:smelter); t2 clean 2:3
(ingot→plate, wire→coil); t3 strange — 2:5 (silicon→chip), 3:5
@@ -122,13 +122,13 @@ range 120, scrap 40. Enemy station: 3000+1500x HP, 25+12x dmg,
## Pacing
**Unlock ladder** (level → unlocks; ← marks `unlock_requires`; starting
set at −1: drone, frigate, railgun_s, salvager, building_block recipe):
set at −1: drone, frigate, railgun_s, salvager, block_pressing recipe):
| level | ships | modules | recipes |
|---|---|---|---|
| 0 | destroyer | repair_tool, armor_plates | |
| 1 | | maneuvering_thrusters, sensor_booster | shortcut_steel_plate |
| 2 | cruiser | railgun_m, afterburner | shortcut_control_chip, shortcut_hardened_steel |
| 1 | | maneuvering_thrusters, sensor_booster | direct_rolling |
| 2 | cruiser | railgun_m, afterburner | direct_etching, direct_hardening |
| 3 | | weapon_stabilizer | |
| 4 | battlecruiser ← cruiser | weapon_primer, weapon_upgrade | |
| 5 | | drone_bay | |