Jump to content

LexManos

Forge Code God
  • Posts

    9264
  • Joined

  • Last visited

  • Days Won

    66

Posts posted by LexManos

  1. Yes people always fuckup systems because they think they know best.

    The problem is people fail to understand what were trying to do. Or how the system works.

     

    `it does not affect existing worlds` this is a prime example. Its MEANT to not effect existing worlds because in theory server side configs would cause issues if changed during the worlds life.

     

    But yes people do stupid things and we do need a system that is better for pack dev's and users. The problem becomes implementation. How do we figure out what values in the world folder were intentional edits to the config. And what just happened to be different because the defaultconfigs changed. How do we write partial config files to disc with only those changes...

    How do we know if the code calling the save function actually changed anything.

     

    It's a annoying implementation solution that needs to be solved.

    And just not writing it to the world folder doesnt work, as wed need to compare the entire config set to a copy from the defaults to see what folder we need to save it to. Mod and Forge code can call the save function quite often. And the NightConfig implementation also has issues with monitoring the files. Do we reload server configs automatically for every world when the file is modified? 

     

    It's not as simple as just `if !(wolrd/config/mymod.toml).exists(): file= defaultconfigs/mymod.toml`

  2. As a note, All versions of Forge work just fine on 'MACOS' it's just some graphics cards screw up LWJGL.

    If you want to update LWJGL yourself in your own install, got for it.

    But as Daemon said, we don't have anyone who can verify the issue or who can test the fix. And we are not going to by default ship native files compiled by random 3rd parties to our millions of users.

    There is however, nothing stopping you from using a text editor and updating the lwjgl dep yourself. We just dont support it for the above reasons.

  3. Actually it is, because there is a major difference between the shape of a block in game for logical things such as physics, collision, pathfinding, and what the model looks like. Unless you're planning on making something that can fit between the whitespaces in your camera.. there is no reason to make it that complex on the simulation side. 

  4. Ya, this has nothing to do with the registration code. It has everything to do with the fact that you're running a stupidly complex, useless function every time you initialize your class. There is no reason for your shape to be that complex, there is also no reason you have to recalculate the rotated shapes EVERY TIME you init the class..

  5. It's in the logs folder. It's named debug.log.

    Also, do not post a log of a non-Forge instance. We can not control what coremods/other hacks downstream projects might have. So if you're using them you have to get support through them.

    If this is reproducable on JUST Forge. Then post the correct log, and include your world so that we can try and reproduce ourselves.

  6. Again you are expected to understand the java side of the issues you're raising.

    We are not a school for basic java. We CAN address things specifically related to Minecraft/Forge. However the bulk of the issues come down to "You need to call this method" "Code no compile!" "You're trying to pass a string into a int.. that is not something we need to help you with"

     

    Either way, the specifics of that example/code  examples has nothing to do with your initial message. It may be aggressive to you. But we don't really care about that. Things being 'overly aggressive' is purely subjective. Hell, it doesn't even work, 90% of the issues posted in tech support don't follow those rules. Either way, do you have something constructive to contribute or are you just wanting to let us know you feel a thread title is 'aggressive'?

  7. I am unable to reproduce this issue in any environments.

    As Dies said, from external views it'd look like java is eating all the memory, but that's becuase that's how the JVM works it manages its own memory without releasing it to the OS.

    If its inside MC/Java, you can try making a meory dump with jprofiler or something, may give you a better idea whats holding the memory.

    But like I said, I can't reproduce this in any environments.

×
×
  • Create New...

Important Information

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