TheGreyGhost

When your client joins to a multiplayer server, the FMLServerStartingEvent doesn't run on the client because it's not running a server. For some background info, see here http://greyminecraftcoder.blogspot.com/2020/02/the-client-server-division-1144.html Just to make sure - do you realise that the multiplayer server will need to be running your mod as well as the client that you're using to connect to it? You can create client-only mods but they are very limited in what they can do. -TGG

Howdy I haven't tried this since 1.12.2 but you might find useful clues in this mod, which uses several other mods as dependencies (see its build.gradle) https://github.com/Vazkii/Botania https://github.com/Vazkii/Botania/blob/master/build.gradle -TGG

Howdy The model loader parses a json file into a model.The last two parameters are required to supply the json information. The easiest way is to let forge load the model for you by using it as a block model with a "dummy" parameter; for example see this working example https://github.com/TheGreyGhost/MinecraftByExample/tree/master/src/main/java/minecraftbyexample/mbe21_tileentityrenderer https://github.com/TheGreyGhost/MinecraftByExample/blob/master/src/main/java/minecraftbyexample/mbe21_tileentityrenderer/RenderWavefrontObj.java https://github.com/TheGreyGhost/MinecraftByExample/blob/master/src/main/resources/assets/minecraftbyexample/blockstates/mbe21_ter_block_registry_name.json -TGG

That depends on what the valid range of numbers is. If the numbers you are trying to store are heavily restricted (eg 100 different possible values) then use blockstates (more efficient). You can cache the block instances in a custom data structure that you don't need to save (since you can easily regenerate it by iterating through all blocks when (eg) loading a chunk.) Otherwise, use a TileEntity. The list of all (loaded) tileentities is maintained by vanilla automatically, you just need to filter it. Down that road lies nothing but pain and suffering.... Chunks loading in and out, other mods manipulating your blocks, multithreaded access, loss of synchronisation... -TGG

Howdy This tutorial project has some examples of screens https://github.com/TheGreyGhost/MinecraftByExample -see mbe30, mbe31, mbe32 -TGG

// ------------- Custom recipes // you can even register your own custom IRecipe class to match complicated inputs - see for example RecipeFireworks // There are a few useful vanilla recipes and Serializers you can base your Recipe on // eg AbstractCookingRecipe, SpecialRecipe and SpecialRecipeSerializer // or go the whole hog and write your own. Lots of vanilla inspiration to keep you on the right track. // All you need to do is register your serializer (assuming you know how to use @SubscribeEvent) // @SubscribeEvent // public void registerRecipeSerializers(RegistryEvent.Register<IRecipeSerializer<?>> event) { // event.getRegistry().register(yourRecipeSerializer); // } -TGG

Howdy I think - if your json works, just leave it as is. A long json isn't a problem really, and it could take you hours to figure out a "more efficient" method. If you are very keen - you could take inspiration from redstone wire. They change the colour based on the power as well, using multistates to build up appearance based on properties. -TGG

Howdy This working example of particles might be helpful https://github.com/TheGreyGhost/MinecraftByExample/tree/master/src/main/java/minecraftbyexample/mbe50_particle -TGG

Howdy you might find this tutorial project useful https://github.com/TheGreyGhost/MinecraftByExample see mbe04 but probably a TileEntity and TileEntityRender is more suited to what you're trying to do (mbe20, mbe21). -TGG

It seems to still be correct for me // we have previously registered digitsTexture in StartupClientOnly::onTextureStitchEvent AtlasTexture blocksStitchedTextures = ModelLoader.instance().getSpriteMap().getAtlasTexture(AtlasTexture.LOCATION_BLOCKS_TEXTURE); TextureAtlasSprite digitsTextures = blocksStitchedTextures.getSprite(digitsTextureRL); These compile fine Check you build.gradle? mappings channel: 'snapshot', version: '20200514-1.15.1' minecraft 'net.minecraftforge:forge:1.15.2-31.2.0' @OnlyIn(Dist.CLIENT) public class AtlasTexture extends Texture implements ITickable { private static final Logger LOGGER = LogManager.getLogger(); @Deprecated public static final ResourceLocation LOCATION_BLOCKS_TEXTURE = PlayerContainer.LOCATION_BLOCKS_TEXTURE; @Deprecated public static final ResourceLocation LOCATION_PARTICLES_TEXTURE = new ResourceLocation("textures/atlas/particles.png"); private final List<TextureAtlasSprite> listAnimatedSprites = Lists.newArrayList(); private final Set<ResourceLocation> sprites = Sets.newHashSet(); private final Map<ResourceLocation, TextureAtlasSprite> mapUploadedSprites = Maps.newHashMap(); private final ResourceLocation textureLocation; private final int maximumTextureSize; public AtlasTexture(ResourceLocation textureLocationIn) { this.textureLocation = textureLocationIn; this.maximumTextureSize = RenderSystem.maxSupportedTextureSize(); } and ModelBakery:: public SpriteMap getSpriteMap() { return this.spriteMap; }

Yes it is https://github.com/TheGreyGhost/MinecraftByExample/blob/master/src/main/java/minecraftbyexample/mbe06_redstone/StartupClientOnly.java

Howdy The problem is that you're breaking the minecraft conventions to do that, for an arbitrary coding implementation reason. Minecraft convention is: 9 nuggets per ingot 9 ingots per block 1 block = 1 bucket (think lava or water being filled into a bucket and back again). This magic number 1296 (16*81) is only important behind the scenes, as a coding implementation, the user doesn't need to know about it at all. The whole millibuckets question is actually a bit of a red herring, because there are really two parts to this 1) what's the internal representation of a fluid (the "atoms" or "voxellites" or whatever) 2) what do we do with the currently-accepted user convention of "millibuckets" personally I think the best answers are: 1) 4096*81 = 331776 units per block (i,.e. final int FLUID_AMOUNT_ONE_BLOCK = 4096*81;) which allows exact representation of all the standard objects that we're interested in (and hence gives conservation of mass with no round-trip-gain-or-lose-mass problems); 2) leave milliBuckets as 1/1000 of a bucket, and present it to the user in an (inexact) metric format eg "one nugget = approximately 111 mB" -TGG

Hi You don't appear to spawn your entity? Look at BowItem::onPLayerStoppedUsing worldIn.addEntity(abstractarrowentity); -TGG

Yes, I mean your getElementPropertyOverride functions. Have you put a breakpoint into there, then traced back out into the caller to see how it is using your returned value?