LtxProgrammer / LtxProgrammer/Changed-Minecraft-Mod

REWORK: Reorganize entity naming conventions, class structures, and species organization

Offen
#1,584 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

documentation long-term
Vorherrschende Sprache
Java
Sterne
83
Forks
58
Ø Merge
1 T. 16 Std.
Gemergte PRs (30 T.)
2

Beschreibung

Related to #772.

Over the nearly 4 years of work put into the mod, the understanding of the world that Changed presents has been evolving. This issue presents the opportunity to fix naming errors and to improve species organization.

- [ ] Rename "Gas Wolf" (and other related terms) to "Wolf".

This entity name was derived from calling the resulting transfur from breathing the transfurring gas an "Aerosol Latex Wolf." This was changed to "gas wolf" in the middle of 2024. Since then, we have added the "Gas Wolf Pup," whose origin of transfur is completely unrelated to its name (from the fennec tf). Discarding the term "Gas" from these names will also remove the origin of transfur from the name, allowing its presence to make sense in more contexts.

- [ ] Rename entities that resemble their anthro counterpart to "Anthro" **AND/OR** rename entities that resemble their feral counterpart to "Feral."

Deciding which shape of the entity gets the name will make naming entities more consistent, and more descriptive. For example: should the name "Latex Crow" go to the anthro (human sized, w/ arms) or feral (bird sized, w/ wings) entity?

- [ ] Organize entities more strictly to their "species."

What I mean by this broad terminology is to more clearly organize class structures (and therefor behavior inheritance) to better reflect the relationship of one entity to another. For example:

```
Non-latex biological (flesh and blood, probably)
├ "Gas Wolf"
├ "Gas Skunk"
├ "Beifeng"
├ "Dark Dragon"
└ ...
Dark latex
├ "Dark Latex Wolf"
├ "Dark Latex Yufeng"
├ "Phage Latex Wolf"
└ ...
White latex
├ Hivemind white latex
│ ├ "Pure White Latex Wolf"
│ └ "Behemoth"
├ Specialized white latex (has a form suited to their environment)
│ ├ Aquatic
│ │ ├ Shark
│ │ │ ├ "Latex Shark"
│ │ │ ├ "Latex Mermaid Shark"
│ │ │ ├ "Latex Shark Feral"
│ │ │ └ ...
│ │ ├ "Latex Squid Dog"
│ │ ├ "Latex Crocodile"
│ │ └ ...
│ ├ Volcanic (Not actually in the mod yet)
│ │ └ ...
│ ├ "Latex Stiger"
│ ├ "Latex Squirrel"
│ └ ...
├ "White Latex Wolf"
├ "Milk Pudding"
└ ...
Currently not categorized
└ "Pool-toy Wolf" (Maybe a specialization of white latex)
```

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Es werden keine Dateien, Tests oder Einstiegspunkte genannt. Beginne damit, die Entity-Klassen zu finden und ihre aktuelle Vererbungs- und Benennungsstruktur zu lesen; für den Abschluss wären abgestimmte Benennungskonventionen und eine neu organisierte Arten-/Klassenhierarchie erforderlich, die die aufgeführten Entitäten abdeckt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
java
Bereich
game-dev
Issue-Typ
Refactoring
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.