Jump to content

dougclarknc

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by dougclarknc

  1. There we go. Thanks for breaking that down. Now, why is MC forcing .toLowerCase()? A MC personal preference? Where specifically is this industry standard practiced? I dont ship jars or deploy enterprise java, just writing qa automation, so idk which "standards" are just in-shop practices and which are "never use default package" standards
  2. Ok, I'm almost following. I'm not making the connection where if I have a FileOne.png (Windows, case-insensitive) and my classes only reference "FileOne.png" (Win, case-insensitive) and I zip both (jar, case-sensitive), who is trying to call "fileone.png"/who is storing it in lowercase? and why cant I point to "FileOne.png"? I can only see the problem going the other direction, from a case-sensitive jar to a case-insensitive format If I put CamelCase.txt into a jar and unzip it anywhere, i expect to always be able to call "CamelCase.txt" Only took 1 OS class in school so please bear with me
  3. I don't know an awful lot about compression. Since google isn't returning any useful links as to why a jar cant handle CamelCase, please link or elaborate why this is. Does this only affect jars? I've never heard of this "industry standard" Now if some dev on *nix makes FileOne.png and fileone.png and a windows dev wants to reference one of those a) i can see the benefit of enforcing lowercase and b) *nix dev needs to change naming convention
  4. Jingus crimbus. Well you right, it works now. Thanks. Does anyone know why this OUTRAGEOUS rule was enacted? Who does it benefit?!
  5. the folders are all lowercase, you mean the files also have to be lower and not camelCase?
  6. I'm stumped. No compile time errors, no runtime errors (that i can find) and yet my textures wont load for a block and 2 items. The intended functionality is there, the block behaves like a block, the item like an ingot, and the tool like a tool. The jar that gradle builds includes the assets in the recommended file paths. I'm just shy of completely rebuilding the mod, but I feel like I'm so close. The jar worked on 1.10.2 but when I updated the accepted mc versions to include 1.11.2 the textures stopped loading Code repo: https://github.com/dougclarknc/MinecraftMod 1.10.2 jar and 1.11.2 jar attached I'll attach any log requested, but the only one I see is the server startup console output which gave me no errors to go on. minerseyemod-1.10.2-1.1.jar minerseyemod-1.11.2-1.4.jar
×
×
  • Create New...

Important Information

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