mirror of
https://github.com/mleem97/gregWiki.git
synced 2026-04-11 03:29:19 +02:00
331847013d
- Revised the tagline in `docusaurus.config.js` for improved clarity on the documentation's focus. - Removed German localization support from the configuration to streamline the user experience. - Updated navigation items in the sidebar to better reflect the current structure, emphasizing player and developer resources. - Enhanced the README and various documentation files to clarify the repository layout and improve accessibility for users. - Adjusted links and descriptions throughout the documentation to ensure consistency and accuracy. This commit aims to enhance the overall clarity and usability of the documentation.
1.7 KiB
1.7 KiB
id, title, slug, description
| id | title | slug | description |
|---|---|---|---|
| modding-language-requirement | Modding language (C# only) | /reference/modding-language-requirement | Mandatory language for mods, MelonLoader plugins, and extensions — C# only. |
Modding language (C# only)
Requirement
All logic for mods, MelonLoader plugins, and framework extensions must be implemented in C#.
That applies to anything shipped as a gregMod.*, gregExt.*, or FFM.Plugin.* / FMF.* module that loads through the MelonLoader / IL2CPP stack: gameplay code, Harmony patches, UI, networking hooks, and data handling belong in C# (typically targeting .NET compatible with your MelonLoader build).
Rationale
- MelonLoader loads managed .NET assemblies; Harmony and the interop layer are built around C#.
- A single language keeps reviews, debugging, and CI consistent for contributors.
What this does not restrict
- Framework core (
gregCore) may still contain non-C# components maintained by core maintainers (for example the Rust FFI bridge undergregCore/bridges/gregSta.RustBridge/, build scripts, or tooling). Those are not substitutes for implementing mod/plugin/extension behavior outside C#. - Documentation, config (JSON/YAML), and assets are not “logic” in this sense.
- gregStore, gregWiki, and other non–in-game stacks may use other languages as appropriate.
See also
- System architecture & documentation principles — stack model and documentation rules
- Framework — runtime surface for mod authors
- FMF hook naming