Skip to content

Explain the lava mechanic behind each generator type, and sync the locales - #175

Merged
tastybento merged 2 commits into
developfrom
feature/clarify-generator-type-button
Aug 12, 2026
Merged

Explain the lava mechanic behind each generator type, and sync the locales#175
tastybento merged 2 commits into
developfrom
feature/clarify-generator-type-button

Conversation

@tastybento

@tastybento tastybento commented Aug 11, 2026

Copy link
Copy Markdown
Member

Follow-up to #173 / #174.

Generator Type button

The generator type is what decides which of the vanilla lava mechanics activates a tier, and it is the setting an admin needs when players start pouring lava onto open water. It is already in the Admin GUI, but the Generator Type button in the generator edit panel only said:

Defines which generator type will be applied to the current generator.

The useful part — that COBBLESTONE means a lava stream meeting water, STONE means lava flowing down onto water, and BASALT means lava on soul soil next to blue ice — was only visible after clicking through to the type picker. As a result it is easy to read "Stone" as "produces stone" and never realise a STONE tier fires on any water a player can reach, oceans included.

The button description now lists the mechanic behind each type, so it is visible before opening the picker.

Locale sync

While adding that to the other languages it turned out every translated file was 28 keys behind en-US, some of them for several releases: the admin reset command, the custom block conversation prompts, the accept_generator, activate_on_unlock, add_custom_block and required_generators buttons, the phase / block-count / required-generator requirement lines, the select generator title and the generator-data-reset message. All 23 files now have them, translated, and each one gets the new type explanation using the type names it already uses in its own picker.

Two placeholder lists were stale as well, which silently disabled features per language rather than just showing English:

  • the generator lore was missing [height-range], so height ranges never appeared;
  • the requirements list was missing [phase], [block-count] and [required-generators], so those requirements were never shown;
  • several files had the placeholder tokens themselves translated ([biomas], [缺失权限], [missing-permission]), which never matches what the code substitutes.

Both lists are now the canonical tokens in every file.

All 24 locale files parse, every non-English file is key-for-key in sync with en-US, and the test suite passes (165 tests).

A docs PR covering the same ground (type table, and the two ways to keep STONE tiers off the ocean: do not hand them out, or give them a height range that excludes sea level) is open at docs#91.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SDLdE5LSXRwc6NQhYvzyiv

The generator type controls which of the vanilla lava mechanics activates
a tier, but the Generator Type button in the edit panel only said that it
"defines which generator type will be applied". The hint about the
mechanic behind each type was only visible after opening the type picker,
so admins could easily miss that a STONE tier fires on any water a player
can pour lava onto, oceans included.

The button description now lists the mechanic for each type.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SDLdE5LSXRwc6NQhYvzyiv
Every translated locale was 28 keys behind en-US: the admin reset command,
the custom block conversation prompts, the accept_generator,
activate_on_unlock, add_custom_block and required_generators buttons, the
phase / block-count / required-generator requirement lines, the select
generator title and the generator-data-reset message. Those keys fall back
to the English text (or to the raw reference) in game.

Translate and add all of them, and give the Generator Type button the same
per-type explanation that en-US just gained, reusing the generator type
names each file already uses in its type picker.

Two placeholder lists were also stale, so features could not render at all
in those languages: the generator lore was missing [height-range] and the
requirements list was missing [phase], [block-count] and
[required-generators]. Some files had the placeholder tokens themselves
translated (for example [biomas], [缺失权限], [missing-permission]), which
never matches what the code substitutes. Both lists are now the canonical
tokens everywhere.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SDLdE5LSXRwc6NQhYvzyiv
@tastybento tastybento changed the title Explain the lava mechanic behind each generator type in the GUI Explain the lava mechanic behind each generator type, and sync the locales Aug 11, 2026
@sonarqubecloud

Copy link
Copy Markdown

@tastybento
tastybento merged commit 68d6ec0 into develop Aug 12, 2026
4 checks passed
@tastybento
tastybento deleted the feature/clarify-generator-type-button branch August 12, 2026 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant