Skip to content

Ronstation custom content needs to be placed into specific _Ronstation folders. #291

@Merrokitsune

Description

@Merrokitsune

Description

Recently, I began to see some Ronstation-specific custom content being scattered around the Resources folder, outside of the _Ronstation folder created specifically to house such custom content. This can not only cause confusion, but also merge conflicts. It is imperative that we put these content to their rightful places inside specific _Ronstation folders.

Guide for _Ronstation folders

Within each Content.<name> folder, or within each folder below the Resources folder, a _Ronstation folder should be provided whenever theres custom content, though some exceptions (e.g. Resources/Locale/en-US/_Ronstation) exist. Every folder within each _Ronstation folder must follow the organization of the parent folder, for example:
If the path to machine.yml is…
Resources/Prototypes/Entities/Structures/Machines/machine.yml
Then the path to the machine.yml within a _Ronstation folder should be…
Resources/Prototypes/_Ronstation/Entities/Structures/Machines/machine.yml
If you’re adding custom content, and a specific prototype or folder fitting for said content does not exist or is not fitting enough, then a custom folder should be provided.
I hope this guide helps.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3: StandardPriority: Default priority for repository items.T: CleanupType: Code cleanup, without being a full refactor.documentationImprovements or additions to documentation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions