Skip to content

docs(base.yaml): document custom substitution settings (06 of 06) - #7528

Open
MahtraDR wants to merge 2 commits into
elanthia-online:mainfrom
MahtraDR:docs/custom-substitution-keys
Open

docs(base.yaml): document custom substitution settings (06 of 06)#7528
MahtraDR wants to merge 2 commits into
elanthia-online:mainfrom
MahtraDR:docs/custom-substitution-keys

Conversation

@MahtraDR

Copy link
Copy Markdown
Collaborator

Companion to elanthia-online/lich-5 PRs #1512#1516 (01–05 of the series), which add Lich::DragonRealms::CustomSubstitutions and the settings keys below. Independent of those PRs — no code dependency; this only aids discoverability.

Problem

The lich-5 series lets players extend Lich's built-in scroll / creature / box / trash / summoned-weapon / flavor-text substitution lists from their own settings, without a Lich release. But a player won't know those keys exist unless they're documented in the sample profile.

Fix

Document the OPTIONAL keys in profiles/base.yaml as commented examples (so behavior is unchanged):

  • custom_scroll_substitutions
  • custom_creature_normalizations
  • custom_box_woods, custom_box_containers, custom_box_substitutions
  • custom_trash_storage
  • custom_summoned_weapons_adjectives
  • custom_flavor_text_patterns

Each entry explains its type and shows a copy-pasteable example. The keys work with or without this change (core Lich reads them straight from settings, merging on top of its built-in defaults); this just helps users find them.

Tests

spec/valid_yaml_spec.rb passes (base.yaml still parses). Addition is ASCII-only.

🤖 Generated with Claude Code

Companion to elanthia-online/lich-5 PRs 01-05, which add
Lich::DragonRealms::CustomSubstitutions and the settings keys that let players
extend Lich's built-in scroll/creature/box/trash/summoned-weapon/flavor-text
substitution lists without a Lich release.

This documents those OPTIONAL keys in base.yaml (as commented examples, so
behavior is unchanged) for discoverability: custom_scroll_substitutions,
custom_creature_normalizations, custom_box_woods, custom_box_containers,
custom_box_substitutions, custom_trash_storage,
custom_summoned_weapons_adjectives, and custom_flavor_text_patterns.

The keys work with or without this change (core Lich reads them straight from
settings); this only helps users find them. Independent of the lich-5 PRs.

Tests: spec/valid_yaml_spec.rb passes (base.yaml still parses). ASCII-only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 455c1953-f249-48a7-86b0-82adc7ae4c89

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

…view)

Peer review of elanthia-online#7528:

- The "picked up on a Lich restart or ;reload" line promised a ;reload that
  doesn't exist; the companion lich-5 change now clears CustomSubstitutions'
  cache in DRInfomon.post_startup_checks (per login), so the accurate statement
  is "picked up the next time you log in."
- Three examples duplicated built-in defaults verbatim (the scale scroll,
  'lesser naga', ['ironwood','iron']), so uncommenting them was a silent no-op
  after CustomSubstitutions' .uniq. Swapped for values that aren't defaults
  ('tattered goblin-hide scroll', 'razorclaw wolverine', ['driftwood','drift'])
  so a curious player who uncomments one sees it actually take effect.

profiles/base.yaml still parses (valid_yaml_spec: 1 example, 0 failures).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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