Off-topic
334 topics in this forum
-
- 0 replies
- 4.8k views
-
- 1 reply
- 4.7k views
-
- 4 replies
- 4.7k views
-
- 1 reply
- 4.6k views
-
- 1 reply
- 4.6k views
-
- 1 reply
- 4.5k views
-
- 1 reply
- 4.5k views
-
- 2 replies
- 4.5k views
-
- 0 replies
- 4.5k views
-
- 1 reply
- 4.4k views
-
- 1 reply
- 4.4k views
-
- 3 replies
- 4.4k views
-
- 4 replies
- 4.3k views
-
- 0 replies
- 4.3k views
-
- 0 replies
- 4.3k views
-
- 1 reply
- 4.3k views
-
- 2 replies
- 4.3k views
-
- 0 replies
- 4.3k views
-
- 1 reply
- 4.3k views
-
- 2 replies
- 4.3k views
-
- 1 reply
- 4.3k views
-
- 2 replies
- 4.3k views
-
- 1 reply
- 4.3k views
-
- 3 replies
- 4.2k views
-
- 2 replies
- 4.2k views
Announcements
-
Posts
-
By MutedKitty · Posted
I already have balm-forge installed. How do I know if it is an issue with balm-forge? And how can I fix it? -
-
-
By perromercenary00 · Posted
thast right kapenjoe says something about not going up from 1.20.2 for some package issue i have the mine working messing around until the code start working still seems like you have some more complex than the mine //in mi main class //########## ########## ########## ########## ########## ########## ########## ########## private void commonSetup(final FMLCommonSetupEvent event) { ModMessage.register(); } ModMessage.class -
By EagleOfFire · Posted
Hello, for educational purpose I am trying to port a mod from 1.20.1 to 1.20.2+ but I can't understand how the new networking system works. I manage to get through it for the most part, but I'm stuck on how to register packets. The previous method was: INSTANCE.registerMessage(id++, CPExecuteSkill.class, CPExecuteSkill::toBytes, CPExecuteSkill::fromBytes, CPExecuteSkill::handle); with instance being of type SimpleChannel. (The forge document is not up to date for this part unfortunatly) Any help or clear documentation would be welcome.
-
-
Topics
-
