Jump to content

lightningdragonx5

Members
  • Posts

    38
  • Joined

  • Last visited

Everything posted by lightningdragonx5

  1. Finally got it to work (along with an item), thanks.
  2. hmm apparently models is supposed to have "block" as a subdirectory and not "blocks" edit: still "filenotfound" Edit 2: I'm just going to read that tutorial I was linked and try again, and if that fails I'll come back here
  3. I didn't do that, that was just my way of saying all those folders were in one folder (my modid folder). This is the inside of my modid folder:
  4. Ok it gives a slightly different error now: (note the extra "block" not sure why that's there) My path is now src -> main -> resources -> assets -> modid -> blockstates/textures/models Vanilla's is assets -> minecraft -> blockstates/textures/models. It still causes FileNotFound errors though, now what?
  5. Just moved all of my assets to resources/volcanodim, with resources being a sibling directory to java. Got the exact same FileNotFound exception, now what?
  6. So I'm trying to start off by adding one simple block. I got it to register after a while but it's got missing texture now due to lack of model. When I try to add a model/blockstate file I get a FileNotFound error (among a few others). Can someone help me find out exactly what I'm doing wrong? I need to know if I'm structuring my assets folder right (I'm most likely not but this is my first time, have to learn somehow), and if the code looking in the right place for blockstates/models/textures, and if there is a problem with my model/blockstate files (and how to fix it if possible).
  7. I finally was able to register my block but unfortunately now it's just using the missing texture file, so I need to link the model and blockstate to the block somehow. But the Forge documentation doesn't really give a good example. Is there any simple step-by-step tutorial project out there that just adds a couple blocks with models?
  8. Just curious how (from technical viewpoint) would that cause the package to not be found though?
  9. lmao, apparently the extensions just flat out don't show on intellij (at least not by default) Thanks for helping me out btw, now I know to watch out for that kind of thing in the future
  10. By "compile" I mean either attempt to run the MC client, or right-clicking the individual file and selecting "Recompile filename.java". How am I building the mod? Not quite sure, I followed the directions on the readthedocs site (https://mcforge.readthedocs.io/en/latest/gettingstarted/#terminal-free-intellij-idea-configuration) as best as I could but I may have missed something. I have no idea what I'm missing so that's why I'm here to begin with, to see if packages not finding each other is a common error that could be solved by something I don't know about. Anyhow it worked fine when I didn't have files referencing each other - for instance when it was just the main mod class by itself it compiled and showed up in the Mods section of the MC client.
  11. Version: forge-1.12.2-14.23.5.2768-mdk Using IntelliJ Community 2018.3 I'm relatively new to this whole thing, and I'm having an issue where importing certain classes within the same packages into a certain other file fails for some reason. "MessageMod" is the main "@Mod" class. So my issue is that in MessageEvent I can do "import a.b.MessageMod" just fine. I've compiled MessageEvent repeatedly but no issues with that so far. The same with the other three classes calling any other things from within the package. But I need to register the MessageEvent, and so from MessageMod I have to import MessageEvent. But inside MessageMod.java, "import a.b.event.MessageEvent" invariably fails: I've tried building the other packages and files all first, restarting, clearing the cache, compiling the whole project all at once, etc. but still haven't gotten it to build properly yet. Also checked the import names a bunch, used the "auto-complete" one from IntelliJ (didn't work) and typed it myself (still didn't work). in short IntelliJ can auto-complete the package name and "knows" it's there, but the error doesn't show up until I try to compile, at which time it tells me that the package does not exist. Googling doesn't do much as the few things that do pop up tell me to do things I can't find or have no idea how to do, or are several years old. Anybody know how to fix this?
×
×
  • Create New...

Important Information

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