Jump to content

nasuellia

Members
  • Posts

    2
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Personal Text
    I am new!

nasuellia's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. Sorry I posted in the wrong section, it was very late in the night when I posted. I suppose you have the permission to move the thread, otherwise tell me what I should do (I can repost if you want). For now I'll just keep going with this. If the capital C was the problem, the lang file wouldn't be accessible too, and the localization wouldn't work. Instead, it does. Also, my filesystem has nothing fancy, I'm under Windows 8.1 with NTFS filesystem. I'll install everything on a second PC and try it here asap. quote: "The fact that it 'was Caveman before' is your issue" this isn't very gentle, and more importantly, it doesn't make any sense. The modid is caveman right now, but it gets renamed in "Caveman" on build for some reason, and I would like a helping help finding out what it could be. Any ideas to investigate it are appreciated. I'm convinced it's not a Forge problem, it's for sure a problem with my system. My point is that Forge developers know the inner workings of it and can help me troubleshooting. For example, you suggested to kill all the folders and recreate them. I tried it: same behavior: the C and the I are capitalized automatically on build. I also noticed (by accident) that only certain specific paths are getting renamed: while recreating the folders the first time I did an error, I didn't create the "textures/items" folder inside "/assets/caveman/", but instead on the upper level "/assets/". The curious thing about it, is that the I from items DIDN'T get capitalized.
  2. Hi everyone and thanks for giving us Forge! Excellent job, Minecraft wouldn't be the same without people like you! I'm back to Minecraft modding after a few years, a lot of stuff has changed and I'm now doing a test mod to get back on track. (I'm working in Eclipse, with forge-1.7.10-10.13.0.1200). I did a custom item: a "Cooked Egg". Everything's fine when I test it with the default run configuration launched from Eclipse : the egg is registered, it's in the right creative-mode tab, stacks correctly, it's edible, it restores hunger & saturation, the localization works, the texture is shown, recipes for it are working. Everything's fine. Then I build the .jar file, and test it on my current minecraft installation, and... the texture is not shown. Having a look at the log, the exception raised is: Using missing texture, unable to load caveman:textures/items/cookedegg.png, java.io.FileNotFoundException Curiously, the jar file contains everything in the right path. In fact, the localization works perfectly: that means the .lang file is found and there are no stupid typo errors or wrong path. The only thing I noticed is an incoherence in capital letters for some of the folders. Given that my modid is: "caveman", and that the unlocalized name of my item is "cookedegg" the texture's path I expected in the jar (as in the folder structure in my project) should be: /assets/caveman/textures/items/cookedegg.png instead, what I get in the jar is: /assets/Caveman/textures/Items/cookedegg.png As you can see, the C from caveman and the I from items are getting the capitalization during build. Is this normal? Why is it? my modid is lowercase, just as the item folder is! What I want to stress again, is that the texture is working like a charm if I launch minecraft from Eclipse. I've been trying to understand this for several hours, I tried lots of obvious things but none have resulted in any change of behavior. Things tried: - A clean installation for my minecraft client and forge - several different forge versions - avoiding strange characters in the unlocalized name (it was cooked_egg before) - avoiding capital letters in the unlocalized name and in the modid (it was Caveman before) - changing the texture's dimension, re-doing the texture, using a very simple one - probably a lot of other stuff I can't remember Thanks in advance to whoever tries to help.
×
×
  • Create New...

Important Information

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