Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading from Forge to NeoForge, from 1.20.1 to 1.21.1, reduce the stored stacks to 1 item. #173

Closed
fabianofa opened this issue Nov 10, 2024 · 2 comments

Comments

@fabianofa
Copy link

Issue type:

  • ❓ Question

Question:

Hi dev, I'd like to check if I'm taking a step too long here with the upgrades.

I have a server currently running on Forge: 47.2.0, and a client on: 1.20.1.
We wanted some new feature from the 1.21.1 then I decided to try to upgrade both things at once, from Forge to NeoForge, from 1.20.1 to 1.21.1.

All booted fine, but once I opened Colossal Chests and/or IronChests entities, all the item stacks that were stored into them were reduced to a single item.

In your experience, would it perhaps give us a better result going from Forge to Forge, between 1.20.1 to 1.21.1 first, then from Forge to NeoForge?

The alternative for us would be of course storing items in vanilla chests, those didn't lose the stacks for whatever reason. But that's quite a painful process and I'd like to check with you first if that's known and if there is an alternative for it.

Thanks in advance.

@rubensworks
Copy link
Member

Someone will answer your question soon. In the meantime, you might be able to get help more quickly on our Discord server.

@rubensworks
Copy link
Member

The Forge->Forge update first may go better, but I'm not sure tbh.
When porting across MC versions, I don't keep things backwards-compatible, just like most (all?) other mods.
I'm surprised this update worked out for you, even just partially.

In theory, custom logic could be added to enable this transition in a backwards-compatible manner. But this would require changes to the code.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 25, 2024
@github-project-automation github-project-automation bot moved this from On hold (awaiting input) to Done in Maintenance Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants