Skip to content

Centralize MUD branding configuration#465

Open
sarahmaeve wants to merge 1 commit intoGoMudEngine:masterfrom
sarahmaeve:upstream-fix/centralize-branding
Open

Centralize MUD branding configuration#465
sarahmaeve wants to merge 1 commit intoGoMudEngine:masterfrom
sarahmaeve:upstream-fix/centralize-branding

Conversation

@sarahmaeve
Copy link
Copy Markdown
Contributor

Summary

  • Add branding fields (Tagline, Description, URL, DiscordURL, AdminName, AdminEmail) to Server config section
  • Add {{ branding "Field" }} template function so templates read from config instead of hardcoding strings
  • Update login splash and about templates in both default and empty worlds to use the new function
  • Operators can now rebrand entirely from config.yaml without editing templates or recompiling

Test plan

  • go vet ./... passes
  • go build ./... compiles cleanly
  • gofmt -l . reports no unformatted files
  • Connect via telnet, verify login splash shows branding from config
  • Run help about, verify it shows branding from config
  • Change Server.Tagline in config.yaml, restart, verify it updates on the splash screen

🤖 Generated with Claude Code

Add Tagline, Description, URL, DiscordURL, AdminName, and AdminEmail
fields to the Server config section so operators can rebrand entirely
from config.yaml without editing templates or recompiling.

Templates now use {{ branding "Field" }} calls instead of hardcoded
strings for the MUD name, tagline, project URL, and Discord link.

Closes #84

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@sarahmaeve sarahmaeve requested a review from Volte6 as a code owner April 6, 2026 00:38
Copy link
Copy Markdown
Member

@Volte6 Volte6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good: New branding fields
Request change: Use a more generic template function name that can be used for any config value

},
"map": makeMap,
"t": language.T,
"branding": func(field string) string {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious - why a branding keyword instead of a config keyword with a path to the value you want to display? I think that would be more generally useful.

For example: {{ config "Server.Description" }}, {{ config "GamePlay.Death.ProtectionLevels" }} etc.

I do like the additional fields, though.

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.

2 participants