Files
gregWiki/docs/guides/mod-developers/overview.md
Marvin e818c78baa docs: update terminology and improve clarity across documentation
- Revised the tagline in `docusaurus.config.js` to reflect the focus on Data Center.
- Enhanced descriptions in `getting-started.md`, `intro.md`, and various mod documentation files for consistency and clarity.
- Updated references to the game name, removing "Waseku" for a more streamlined presentation.
- Improved the structure and readability of tables and lists throughout the documentation.

This commit aims to ensure the documentation is clear, consistent, and accurately represents the project, enhancing usability for both mod developers and players.
2026-04-10 04:44:12 +02:00

19 lines
1.2 KiB
Markdown

---
title: Mod developers
sidebar_label: Mod developers (hub)
description: Getting started, mod config, debugging — curated docs for FMF mod authors.
---
# Mod developers
**Mod authors** — build your own mods (hooks, configuration, debugging). **Players** → [/players](/players).
- [Greg hooks showcase](/wiki/guides/mod-developers/greg-hooks-showcase) — sample mod (`GregShowcaseMod`) and `GregPayload` usage
- [System architecture & documentation principles](/wiki/meta/system-architecture-principles) — layer model **ModManager → Framework → Plugins → Mods**, priorities, wiki rules
- [Getting started](/wiki/getting-started) and [Documentation hub](/wiki/developers)
- [Framework overview](/wiki/mods/framework) — runtime capabilities and repo layout
- [FMF hooks](/wiki/framework/fmf-hooks) — hook surface (generated article)
- [FMF hook naming](/wiki/reference/fmf-hook-naming); runtime map: [greg hooks catalog](/wiki/reference/greg-hooks-catalog) (see also [FMF hooks catalog (legacy redirect)](/wiki/reference/fmf-hooks-catalog))
- [Contributor workshop](/wiki/guides/contributors/contributor-workshop) — builds, CI, and PRs
- [Mods](/wiki/mods/) — gameplay mods (`FMF.*`) and release pages