Jump to content

LexManos

Forge Code God
  • Posts

    9273
  • Joined

  • Last visited

  • Days Won

    68

Everything posted by LexManos

  1. Working with bspkrs right now to get his end done. Forge's end there are ~100 failed hunks. I'll be pushing at least a beta tonight.
  2. Json and lang files are data. Not code. You can not reference code in them. Simple as that. If you MUST have a weird setup like this then write a script to generate the lang and json files.
  3. 1.9.4 support will be done Soon I've finished the bulk of the updates for the pre-forge stuff. Just waiting on someone else to finish their work so I can start on Forge.
  4. One of your mods is sending an invalid packet, there is no way to know which so you'll have to start removing them. Also, you REALLY should update to 1.8 if you want support 1.7.10 is old as hell..
  5. Mystcraft issue, also update to 1.8+
  6. CAN you require J8 in your mod? Yes. SHOULD you? No, Minecraft targets J6, so should you. Simple as that.
  7. That is called layers, you can use normal textures layered on top of each other just fine. No need for custom generated code. It would work JUST FINE with resource packs. As for the physics shit, you can do the substitution system we have in the registry to take control. And leave it as is. Generating context, be it blocks, items, textures, whatever is bad because it 1) breaks the data driven design that we at forge, and mojang are trying to do 2) It breaks a lot of functionality when it comes to external modification for resource pack makers, server owners, etc.. 3) It makes life hell when trying to manage data and keep worlds/servers clean and synced up 4) It opens up a PLETHORA of potential security issues depending on the routes which you go. 5) It screws with the caching and performance of the re-written rendering pipeline causing major downgrades to end user's experiences. There are A LOT of issues with doing dynamic content like that. If you run into issues, then you can get them addressed. 1) Fixed with multilayer models 2) Fixed with some re-working of the entities nothing hard just needs to be brought it properly. 3) Should never need to be done.
  8. That is you running the game -.- not the installer -.- Just watch the video in my signature and run the installer jar manually. Use the command: java -XMx2G {InstallerFileName}.jar If that doesnt work give the logs of the screen and if you get a 'file not found' error then you didnt use the correct installer name or are in the wrong directory rewatch the video -.-
  9. That is not your log -.- the log is a file created in the same directly as the installer that will tell us WHY you couldn't install those files -.- 9/10 times its because your computer gave the installer to little ram. Which we have explained how to fix a plethora of times on these forums if you would search or read the eaqs.
  10. Prepackage the data, and in all honesty what you've described doesnt need to do anything special or replace blocks, just listen for block change events and create falling entities. 'Dynamic' mods/block are a BAD IDEA. Do not do them.
  11. Last warning, post your logs or be banned -.- Its not a hard rule.
  12. There isn't supposed to be one. Minecreaft is a library not source.
  13. Logs, logs are ALWAYS required for tech support. Beyond that go manually install the libraries then.
  14. Do not create the json or dynamic blocks from code. You can create the data externally once and then ship it out. Creating models/textures/jsons with code is bad.
  15. I would advise killing the profile and reinstalling it something went wonkey with the install.
  16. 1.9.4 will be coming soon. I am waiting for bspkrs to finish up his side of the MCP update and then i'll start on Forge.
  17. One or more of your mods that adds entities to the wold has set an invalid spawn random. You'll have to start removing mods until it stops happening to figure out which one.
  18. It works as long as the mod tells us what version is it for. If the modders doesn't give that information we can only assume it's for the current version so we have to try and load it. Side not, you should use the version folders to sort your mods. /mods/{MCVERSION}/{PutStuffHere}
  19. Ya we usually wait about a week or so for users to point out all these minor bugs and fix them before bumping for another RB. I'm not perfect, people who submit PRs arnt perfect. We just try to fix things as soon as they are verified.
  20. IC2 {and any other 'API'} Should have a maven repository. If they do all you need to do is add that info to your build.gradle. Just like any other depeandancy. Go yell at the IC2 people for their maven info.
  21. Always get mods from either the Minecraft Forums, or here. Almost all other sites that list mods are bad and lie to you. If you ever see an 'mod installer' that's almost always mal/adware. I can't guess what a random mod is targeting based on file names. Well sometimes I can because mods will usually include the MC version in their file name. MCA-1.9-5.1.2-universal.jar is potentially safe to say it's 1.9. However go to the miencraft forums, find the official post for it and make sure you get the correct download link.
  22. There is always a log. ALWAYS. And It may be worth closing that 20 version gap down a little if you can. A lot of things can change in 20 versions. Tracked it down to this commit, seems that oredicting 'paper' screwed it up. Fixed in latest build.
  23. It found them and discarded them because they are not mod files. Side note why the hell are you trying to install 1.7.10 mods on 1.9 minecraft? That won't work.
  24. Somehow you've registered the itemstack itself as needing to serialize.. itself... hence the infinite loop.
×
×
  • Create New...

Important Information

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