
AmeliaLotus
Members-
Posts
25 -
Joined
-
Last visited
AmeliaLotus's Achievements

Tree Puncher (2/8)
1
Reputation
-
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
I feel a little better about this then, for sure. Thank you for your help! At the very least, I've learned quite a bit about API's and how to use them. Thanks! -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
ItemMultiTexture requires two blocks and a String array for the meta names. Sorry, but that makes no sense as to why I'd use that here. Looks like I'm just going to give up the Metadata thing... No one even uses it anymore(Shown by the fact that only a few people on this forum understand Metadata in the first place)... I'll just be happy with what I've got on LightMod and call it good. I appreciate your help! I've learned quite a bit doing this for the past few days. Thank you! -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
You're confusing me by telling me to look at the type hierarchy for ItemBlock. That's just "Item". Inside item, it's the same issues. Code is below to how I reached this point. I know I have to switch "lighted_glass_block" with something, but I don't really know how I'd do it. Metadata is just so difficult, I would've been done by now if I just made a separate block for all 16... CommonProxy.registerBlockWithCustomItem(blockGlassLight, new ItemMetaBlock(blockGlassLight), "lighted_glass_block"); -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
So I "Cheated" and copied your ItemOreBlock class... it works ! Now I just need to find a way to name them... They're all named with the same exact name ... Now how would I even go about fixing that.... Hmmmm -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
Yeah. That was my bad. Used MODID instead of "lighted_glass_block. Here's some updated code: //Easy Register everything with CommonProxy(Server) and ClientOnlyProxy(Client) blockGlassLight = new LightedGlassBlock(Material.GLASS); CommonProxy.registerBlockWithCustomItem(blockGlassLight, new ItemBlock(blockGlassLight), "lighted_glass_block"); //Call forth the proxy events! MinecraftForge.EVENT_BUS.register(proxy); This gives no errors, the item textures are FINALLY working, but they're all an identical block when placed(the item textures are appropriately working, however). They're all the white block instead of multi-colored. Also, I have absolutely no idea how to name each of them in my en_US.lang if they're all the exact same name in the Item list. Meta data in F3 when hovering over each block placed is all color=white... so it's not giving me all the blocks that BlockColored places? -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
At this point, I'm just entering random things and trying it out. Here's my main class: https://pastebin.com/0fLSYYSi Here's my console error: https://pastebin.com/dAcuTEyK I even used comments to show you how I did the other ones. Maybe I'm just really screwing things up in my main class... (Probably the issue here...) And blocks don't show up anymore. Just the purple/black again. EDIT: WOOPS. I set the registryName to MODID instead of "lighted_glass_block" ... Still gives me an error for the items, and only gives me 16 of the exact same block instead of multiple variants... (Each and every item-instance gives me a white lighted block (perfectly textured on the block but not the item!) -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
That's the whole error. { "parent": "block/cube_all", "textures": { "all": "blockstatetraining:blocks/lighted_glass_block" } } That's my model json { "variants": { "color=white": { "model": "blockstatetraining:lighted_glass_white" }, "color=orange": { "model": "blockstatetraining:lighted_glass_orange" }, "color=magenta": { "model": "blockstatetraining:lighted_glass_magenta" }, "color=light_blue": { "model": "blockstatetraining:lighted_glass_lightblue" }, "color=yellow": { "model": "blockstatetraining:lighted_glass_yellow" }, "color=lime": { "model": "blockstatetraining:lighted_glass_lime" }, "color=pink": { "model": "blockstatetraining:lighted_glass_pink" }, "color=gray": { "model": "blockstatetraining:lighted_glass_gray" }, "color=silver": { "model": "blockstatetraining:lighted_glass_lightgray" }, "color=cyan": { "model": "blockstatetraining:lighted_glass_cyan" }, "color=purple": { "model": "blockstatetraining:lighted_glass_purple" }, "color=blue": { "model": "blockstatetraining:lighted_glass_blue" }, "color=brown": { "model": "blockstatetraining:lighted_glass_brown" }, "color=green": { "model": "blockstatetraining:lighted_glass_green" }, "color=red": { "model": "blockstatetraining:lighted_glass_red" }, "color=black": { "model": "blockstatetraining:lighted_glass_black" } } } This is my blockstate json. It all works perfect if I used RegisterBlock (Items don't work, of course...), and if I use BlockWithItem then it all breaks. -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
I thought so! That was my first try, but it doesn't load the blocks nor the items correctly. Exception loading model for variant blockstatetraining:blockstatetraining#color=cyan for blockstate "blockstatetraining:blockstatetraining" It works with RegisterBlock, just not RegisterBlockWithItem... -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
How do I use the -withVariant version if I don't technically have any 'variant' to give it? I am simply extending BlockColored and the other "RegisterItems" doesn't seem to work at all. -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
Alright, so I have attempted (to the best of my ability) to register with your api. I get no error, but the blocks aren't showing anymore. https://pastebin.com/XTuBCxSf Here's the github for all of the code! EDIT: I figured out that it's just not running the registerBlocks and registerItems SubscriberEvents. Fun... -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
If I just copy pasted into my Client and Common proxies, would I need your API files, such as IMetaLookup, MeshDefinitions, etc? It's a whole lot of files for a little register item thing... -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
Truthfully, I've never done dependencies or tried modifying someone's entire class codes to fit mine. It just never works. But I tried, and failed miserably...Now I have to redo everything by downloading on GitHub because I don't have a clue what broke... -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
I ended up scrapping it since it broke the entire thing after messing with it. Back to the drawing board for registering this entire thing... Do you happen to have anywhere to point me to as a tutorial for registering the item textures for this situation? -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
This code should be having no problems register the item stack from the metadata And yet this code in the json: Doesn't even work for "textures". I made sure to re-read forge documentation as well. No errors at all. This should 100% work... the Blocks work perfectly, just not the items in your hands. -
Trying to learn blockstates and config files...
AmeliaLotus replied to AmeliaLotus's topic in Modder Support
I cannot believe I just made a rookie mistake like that. I'm used to initials and for some reason I went with a full name this time... Thanks a whole bunch!