Skip to content

Refactor Spoutcraft client for multiloader support#5

Open
noramibu wants to merge 2 commits into
ModernSpout:masterfrom
noramibu:master
Open

Refactor Spoutcraft client for multiloader support#5
noramibu wants to merge 2 commits into
ModernSpout:masterfrom
noramibu:master

Conversation

@noramibu

Copy link
Copy Markdown

Most of the client code and assets are in common now, and Fabric & NeoForge only keep loader-specific files, on their own subfolders ^^

Also while adding support for NeoForge, I removed Fabric API requirement to make mod more dependency free, and if needed it can support other mod loaders more easily in future, without depending to Forgified Fabric API or any other dependencies.

In NeoForge, I used network-thread payload handling on NeoForge because custom content needs to be registered before chunk packets decode custom block IDs which may (will) cause crashes ^^

Also did some other changes such as:

  • Added block-state ID mapping clear on disconnect
  • Simplified disconnect states
  • Added /spoutcraft command
  • Removed duplicate loading overlay logo mixin & removed no-op loading overlay mixin
  • Cleaned some compiler/IDE warnings

Builds can be find at /spoutcraft-mod/neoforge/build/libs/ and /spoutcraft-mod/fabric/build/libs/

Additionally mod works fine on Quilt because it no longer depends to Fabric API

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.

1 participant