.png.d8c41283a4d2e33b73585fbc69977fc1.png)
sciwhiz12
-
Posts
391 -
Joined
-
Last visited
-
Days Won
1
Posts posted by sciwhiz12
-
-
A fix was pushed to Forge (32.0.25), but it seemed that dedicated servers still have the issue (or at least, before doing a /reload). Check this PR: https://github.com/MinecraftForge/MinecraftForge/pull/6876.
-
This is a known issue with tags and dedicated servers. Check this PR: https://github.com/MinecraftForge/MinecraftForge/pull/6876.
Also, can you please clarify for me: you used the vanilla server, and connected using a Forge client, yes? And then you used the MDK to recreate the issue?
Forge 1.16.1 is currently in BETA. Crashes and bugs are expected to occur while the Forge team is fixing what broke during the update.
-
This is a known issue with dedicated servers and tags. Check on this PR: https://github.com/MinecraftForge/MinecraftForge/pull/6876.
Forge 1.16.1 is currently in BETA. Crashes and bugs are expected to occur while the Forge team is fixing what broke during the update.
-
The PR was closed by a Forge dev, because a fix was pushed (32.0.25) which seemed to fix the issue. However, it was discovered that the issue still exists on the dedicated server. Check on this PR: https://github.com/MinecraftForge/MinecraftForge/pull/6876.
-
This is a known issue. It was thought to be solved with 32.0.25, but it seems that, as you have discovered, dedicated servers are still affected. Check on this PR: https://github.com/MinecraftForge/MinecraftForge/pull/6876.
Forge 1.16.1 is currently in BETA. Crashes and bugs are expected to occur while the Forge team is fixing what broke during the update.
-
I must be getting tired. Did not catch that on first try. Sorry.
OutOfMemoryError. Please allocate more memory to the game.
-
return stack.getItem() == ModItems.THING1 || stack.getItem() == ModItems.THING2;
Use equality checks and OR conditionals.
-
Please update to 1.15.2, as 1.14.4 will become unsupported soon.
That said, backup your config directory, and then delete it.
-
Please post your game version, Forge version, and post your debug.log on a paste site (pastebin, hastebin, GitHub Gists).
We cannot diagnose your issue without information. -
Forge 1.16.1 is currently in BETA. Crashes and bugs are expected to occur while the Forge team is fixing what broke during the update.
While 1.16.1 is now in active development and support, it will be some time until a stable/recommended release for Forge 1.16.x.
If you want to test and find bugs, please do so and report them to this forum. If reporting a bug, please search if another topic is already made about it.
If you're just wanting to play modded 1.16, please wait until Forge is out of beta and a recommended Forge version is released.
Please try 32.0.25. A fix was very recently pushed about issues of this type.
-
I confirm that this issue exists on 1.16.1 and 1.15.2 latest forge versions as of writing this post, using hopper insertion. Filed a bug report (MinecraftForge#6873)
-
I confirm that this issue exists on 1.16.1 and 1.15.2 latest forge versions as of writing this post, using hopper insertion. Filed a bug report (MinecraftForge#6873)
-
Latest forge? As in 1.16.1?
-
1
-
-
Are you using bukkit/spigot? I see no mention of Forge, so...
-
Forge 1.16.1 is currently in BETA. Crashes and bugs are expected to occur while the Forge team is fixing what broke during the update.
Please do not comment if what you are just saying 'same', as this is already a known issue.
-
Forge 1.16.1 is currently in BETA. Crashes and bugs are expected to occur while the Forge dev team is still fixing what got broken during the update.
While 1.16.1 is now in active development and support, it will be some time until a stable/recommended release for Forge 1.16.x.
If you want to test and find bugs, by all means do so and report them to this forum.
If you're just wanting to play modded 1.16, please wait until Forge is out of beta once again, and until a recommended Forge version is released.
It seems that this is related to a known issue. (MinecraftForge#6857 and MinecraftForge#6871)
-
Forge 1.16.1 is currently in BETA. Crashes and bugs are expected to occur while the Forge team is fixing what broke during the update.
While 1.16.1 is now in active development and support, it will be some time until a stable/recommended release for Forge 1.16.x.
If you want to test and find bugs, by all means do so and report them to this forum. If reporting a bug., please search if another topic is already made about it.
If you're just wanting to play modded 1.16, please wait until Forge is out of beta once again, and until a recommended Forge version is released.
You seem to have already reported this issue on the issues tracker. (MinecraftForge#6871)
-
14 minutes ago, TheGoat1254321 said:
forge 1.12.2
1.12.2 is outdated and not supported on these forums.
Please update to a modern version to receive support.
-
Forge for 1.16.1 is in BETA. This means crashes and bugs are expected to occur while the Forge dev team is still fixing what got broken during the update.
While 1.16.1 is now in active development and support, it will be a few days/weeks until a stable/recommended release for Forge 1.16.x.
If you are wanting to test and find bugs, by all means please do so and report them to the issues tracker. But, if you're just wanting to play modded 1.16, please wait until Forge is out of beta once again, and until a recommended Forge version is released.
-
27 minutes ago, Cinderous said:
hyperl:hyperlane
// ChangeDimensionTrigger.class, MC version 1.15.2, mappings 20200514-1.15.1, L23 (partial) DimensionType.byName(new ResourceLocation(JSONUtils.getString(json, "from"))) // DimensionType.class, MC version 1.15.2, mappings 20200514-1.15.1, L102-105 @Nullable public static DimensionType byName(ResourceLocation nameIn) { return Registry.DIMENSION_TYPE.getOrDefault(nameIn); }
Use the registry name that you used in your DeferredRegister: "hyperl:hyperlane_dim"
-
The most recent crash report is a recurring issue in Forge currently. (revelant issue) Try running it again.
10 minutes ago, ChromaKey81 said:Could you briefly explain what I need to change in the build.gradle (or direct me to some documentation)?
The 'archiveBaseName', 'group', and replacing 'examplemod' and 'examplemodareus' with respective modid and your author name.
12 minutes ago, ChromaKey81 said:By the way, do I need to compile all of my .java files to .class? How would I do that in VSCode?
I am not familliar with java coding with VSCode. Although VSCode has an associated task built for it (genVSCodeRuns), as said above, you are better off using IntelliJ IDEA or Eclipse. (unless you wish to stick to VSCode, in which case I wish you good luck and fun)
-
The default branch is still 1.15.x, as of my writing this. As 1.16 is now in active development, shouldn't the default branch be 1.16.x?
-
Try changing the option 'Dynamic Updates' in one of the video settings menu. It trades off FPS for chunk loading, if I recall correctly.
-
6 minutes ago, Curle said:
This is a known bug, and we're working on fixing it.
It should be solved in one of the next few updates.
Curle is a new member of the Forge team. See the announcement post for more details.
please help 1.16.1
in Support & Bug Reports
Posted
Looking at the CurseForge pages for Xaero's Minimap and WorldEdit, they do not have a version for 1.16 Forge, only Fabric. So, you are most likely using the wrong modloader.
Forge 1.16.1 is currently in BETA. Crashes and bugs are expected to occur while the Forge team is fixing what broke during the update.
While 1.16.1 is now in active development and support, it will be some time until a stable/recommended release for Forge 1.16.x.
If you want to test and find bugs, please do so and report them to this forum. If reporting a bug, please search if another topic is already made about it.
If you're just wanting to play modded 1.16, please wait until Forge is out of beta and a recommended Forge version is released.