ViaVersion / ViaForge

Client-side Implementation of the Via* projects for Minecraft Forge
GNU General Public License v3.0
120 stars 33 forks source link

My suggestions for this mod #37

Closed MIOGMIOG closed 1 year ago

MIOGMIOG commented 2 years ago

These features will be good to add: 1. Textures and models for blocks, items, armors and entities (likely patching ViaVersion will be required) 2. Add compatability for CubicChunks - support higher build limits for 1.18+ and classic servers (probably requires patching viaversion)

  1. Per-server version setting; For each server, ability to set different versions (so we dont have to switch global version setting)
  2. For version list, add "automatic" option - it will ping server and get supported versions and it will use closest supported server version (it already is in ViaFabric)
  3. Implement ViaLegacy *6. Qol features for ViaLegacy (remove hunger bar when version is beta 1.7-, etc... Like in this project: ViaLegacy for Multiconnect)

For this to work with other mods, ViaForge will have to split to 2 jars - ViaForge core (current project plus features here without star) and ViaForge QOL (will require ViaForge core installed in mods folder with it and it will add features with stars)

HowardZHY commented 2 years ago

Project 1 is like the labymod plugin one Project 3 is "easy" with Optifine Project 4 would be really hard

HowardZHY commented 1 year ago

Project 1 is like the labymod plugin one Project 3 is "easy" with Optifine Project 4 would be really hard

ok but it would have to be an optifine mod REQUIRED DEPENDENCY which we don't want, just add new items and change viaversion mappings (I don't think you can put nbt tags / something like that in viaversion mappings)

using names like 1.16 xx is just enough, and VB has an NBT tag for items. I don't really know will placed blocks work or not

MIOGMIOG commented 1 year ago

These features will be good to add: 1. Textures and models for blocks, items, armors and entities (likely patching ViaVersion will be required) 2. Add compatability for CubicChunks - support higher build limits for 1.18+ and classic servers (probably requires patching viaversion) 3. Per-server version setting; For each server, ability to set different versions (so we dont have to switch global version setting) 4. For version list, add "automatic" option - it will ping server and get supported versions and it will use closest supported server version (it already is in ViaFabric) 5. Implement ViaLegacy *6. Qol features for ViaLegacy (remove hunger bar when version is beta 1.7-, etc... Like in this project: ViaLegacy for Multiconnect)

For this to work with other mods, ViaForge will have to split to 2 jars - ViaForge core (current project plus features here without star) and ViaForge QOL (will require ViaForge core installed in mods folder with it and it will add features with stars)

Splitting to 2 jars will be good, because for example entity models for new entities or removing hunger bar can break other mods

MIOGMIOG commented 1 year ago

This should move to ViaForgePlus repo