Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Nayrisian

Members
  • Joined

  • Last visited

  1. Omg... I cannot believe I missed that. Thank you for that quick evaluation...
  2. Description of the issue: Textures, registration and item localisation all work correctly, but I am currently stuck on getting tiles to localise. Here's a visual example of the issue... As you can see from the pictures, my copper ingot works perfectly, but the tile (Copper ore) doesn't. Here is the code stuff: Here is the directory in the IntelliJ IDE And finally the main attraction... en_us.lang # Blocks tile:copper_ore.name=Copper Ore item:copper_ore.name=Copper Ore block:copper_ore.name=Copper Ore # Items item.copper_ingot.name=Copper Ingot I was testing with numerous ways of trying to get the localisation file to recognise the block but to no avail. Note: I do not use the mod id of the mod in my localisation files because I pass in the registry path string, I would doubt blocks and items have different unlocalised names based on the same parameters inputted... But feel free to explain if they do. [17:43:57] [main/INFO] [tau/tau]: Copper Ore unlocalised name: tile.copper_ore [17:43:57] [main/INFO] [tau/tau]: Copper Ore registry name: tau:copper_ore [17:43:57] [main/INFO] [tau/tau]: Copper Ore Item unlocalised name: tile.copper_ore [17:43:57] [main/INFO] [tau/tau]: Copper Ore Item registry name: tau:copper_ore [17:43:57] [main/INFO] [tau/tau]: Copper Ingot unlocalised name: item.copper_ingot [17:43:57] [main/INFO] [tau/tau]: Copper Ingot registry name: tau:copper_ingot Finally the registry names and unlocalised names of the blocks/items in question, outputted using the logger during post initialisation, for my own verification that I haven't missed anything when registering the objects. On the same context as the post itself, is the technique I am using to register blocks better or the same as doing: public CopperOre() { super(Material.ROCK); setRegistryName(new ResourceLocation(Ref.MOD_ID, Ref.COPPER_ORE)); setUnlocalizedName(getRegistryName().toString()); } Or does it not exactly matter for Forge conventions? fml-client-latest.log

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.