Leaderboard

Commands are registered on both the IntegratedServer and DedicatedServer. The IntegratedServer is on the client so you can register it in FMLServerStartingEvent.

Currently, the Report Bugs button in game menu sends you to the official bug tracker, which isn't very helpful, since Mojang doesn't care about issues with modded game. It would make sense if it would send you to Forge Support & Bug Reports instead. Also, it could tell you to contact mod author first if you are having issue with specific mod.

This is correct. Post the error.

You need to create and register an EntityType<T extends Entity> now in order to make an Entity.

And remove this entirely.

Use SlotItemHandler instead of Slot.

After you're in downloads, type "dir forge*" (there's a * with no spaces after forge) to make sure it's there. If it is, you want to use java -jar forge-1.15.2-31.1.34-installer.jar cd means "change directory", that's why you got an error trying to cd into the installer.

The only thing I can find which could be causing this error is this. You are not allowed to have an resources with capital letters.

Hi I did something similar with another mod I was working on, you might find some inspiration in there. https://github.com/TheGreyGhost/dragonmounts2-1.12.2/tree/configurable-checkpoint2 See the classes: DragonVariantTag DragonVariants DragonVariantsReader Typical usage is a config file like : dragon1.json { "breedinternalname": "fire", "lifestage": { "size5adult": 5, // size of the adult in metres "healthbase": 50.0, // base health of the adult "armorbase": 10.0 // base armour of the adult }, "egg": { "size": 1.0, //the size (width and height) of the egg in metres "particlesname": "townaura" //what particle effect does the egg produce while incubating? as per the /particle command } } with code that looks like this: private static final DragonVariantTag EGG_SIZE_METRES = DragonVariantTag.addTag("size", 0.5, 0.05, 2.0, "the size (width and height) of the egg in metres").categories(Category.EGG); private static final DragonVariantTag EGG_INCUBATION_DAYS = DragonVariantTag.addTag("incubationduration", 1.0, 0.1, 10.0, "the number of days that the egg will incubate until it hatches").categories(Category.EGG); private static final DragonVariantTag EGG_WIGGLE = DragonVariantTag.addTag("wiggle", true, "should the egg wiggle when it gets near to hatching?").categories(Category.EGG); private static final DragonVariantTag EGG_GLOW = DragonVariantTag.addTag("glow", false, "should the egg glow when it gets near to hatching?").categories(Category.EGG); and final String TEST_FOLDER = "testdata/testdvr1"; DragonVariantsReader dragonVariantsReader = new DragonVariantsReader( Minecraft.getMinecraft().getResourceManager(), TEST_FOLDER); Map<String, DragonVariants> allVariants = dragonVariantsReader.readAllVariants(); DragonVariants dragonVariantsFire = allVariants.get("fire"); double eggSizeMetres = (double)dragonVariantsFire.getValueOrDefault(modifiedCategory, EGG_SIZE_METRES); I don't have a standalone test harness at the moment unfortunately, but the classes are reasonably self-contained and (hopefully) fairly intuitive to figure out. The code also includes functionality for "modifiers" and "ariantTagValidator" to check for config tag problems and/or initialise resources based on the tags, but those are optional. Cheers TGG

FTB Continuum is a 1.12.2 pack, which is out of support. The supported versions, 1.14.4 and 1.15.2 have parallel mod loading, which speeds up loading SUBSTANTIALLY. And are we going to get into the amount of disk space such a system would eventually build up to? I don't feel like periodically cleaning my disk of cached texture atlases, especially since different packs with the same mods would cause a new atlas set to be cached, and a resource pack change would cause a re-cache, and pack devs would see their test installation bloat with every mod added to the pack. To be honest to me it sounds like effort that would save maybe a second or two of loading at the cost of disk space. I'd rather wait a couple seconds.