-
Notifications
You must be signed in to change notification settings - Fork 7
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
[1.16, Bug] Crash with Futurepack mod #204
Comments
I… am pretty sure I fixed that crash at some point, but I guess I never uploaded it? |
Yeah, its a super weird issue. Two things i forgot to mention in my initial post:
If you need any more info on the subject please ask! |
SU was truthfully designed for forge 36.2.20 |
That could explain it. The crash only happens with Futurepack installed, Small-Units works fine standalone |
Ok nvm then |
Np! Take your time with the fixes, better safe than sorry. Thank you for looking into it! |
-- Describe how you caused the bug --
When you have Futurepack mod (https://www.curseforge.com/minecraft/mc-mods/futurepack) and Smaller-Units mod installed, putting an block into a Smaller-Units tile causes the game to crash.
The Unit tiles are also broken with Futurepack installed. In the screenshot i have 1/3 unit on the left, and 1/16 unit on the right, but theyr both the same size. This does not happen when only Smaller-Units is installed.

If this is something that should be reported to Futurepack instead, please let me know and i will re-direct this!
-- Describe the expectation --
The game doesent crash when placing blocks on unit tiles and the unit tiles are the intended size
-- Describe what happened instead --
The game crashes when placing blocks on unit tiles and the unit tiles are not the intended size
-- Additional info --
SU Version: 1.3
Futurepack Version: 31.3.7008
Exact MC Version: 1.16.5
Loader: Forge
Any optimization mods: No
-- Logs if the game crashed --
Crash report: https://pastebin.com/PetJAX89
Log: https://pastebin.com/1Lcejaq6
Thank you for your time!
The text was updated successfully, but these errors were encountered: