Jump to content

LexManos

Forge Code God
  • Posts

    9264
  • Joined

  • Last visited

  • Days Won

    66

Everything posted by LexManos

  1. The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.18.1/1.18.2 (Latest) and 1.16.5 (LTS).
  2. Some zip managers like to take control of the .jar file extension away from Java. Make sure you have Java installed and try running Jarfix once, then try the installer again.
  3. Buy the game and use the vanilla launcher. We do not support pirate launchers. {Yes I am aware it claims to let you login to a real account, but the fact that it also lets you not, means its a piracy launcher}
  4. Again people HAVE done this. It's not just draw strings and widgets. Because configs can have a lot of config value types that dont exist in vanilla. All I can say is just go do it and see what happens.
  5. Most likely its the later. But the cost is quite a lot with mojang liking to re-write the rendering system. Again, there are already a few 'generic config gui' mods out there that work. We provide a fairly simple data layer for defining config objects, so a few people have taken it upon themselves to make them into mods.
  6. More specifically, we used to have one, but then our rendering guy got stolen by Mojang. And thee cost of updating it everytime they changed something upstream got too much. There are mods out there that add generic screens. The main reason there isn't one in Forge is manpower to maintain them in the future.
  7. That's not the entire log, it is curring off the important bits. The log is a text file found in your logs folder.
  8. This is most likely an issue with JEI's caching of the recipe items not properly taking the tag changes in 1.18.2 into account. Try to reproduce the issue without JEI, using the normal recipe book/testing the recipes. Or it could be some other mod resolving the tags way to early . Tags were the big change in 1.18.2, some mods may have not addressed those changes.
  9. Some zip managers like to take control of the .jar file extension away from Java. Make sure you have Java installed and try running Jarfix once, then try the installer again.
  10. The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.18.1/1.18.2 (Latest) and 1.16.5 (LTS).
  11. https://github.com/MinecraftForge/MinecraftForge/commit/fcb81aa6605ab467071e6ee242b34f0b1255cd64 Didnt have a .isEmpty check, just a null.
  12. Serious answer, if the server provider has not taken the few mins to update to support the new system in 5 years {java 9 released in 2017} then you should not be patronizing them. Cancel your account and get a refund/chargeback.
  13. You do realize that this is not something that's possible to detect on our end. Nore will this popup be helpful. By the time you see this message the bad code will of already been ran and your data will be gone. Do not download untrusted mods, especially do not download any mod from untrusted sources. At the end of the day, it's on you to be diligent when you're on the internet.
  14. 1.18.2 has a "full release" has for a while. But yes we are close to a recommended build. But no we do not go out of our way to notify random people about it. We have a twitter/forum/github you can follow.
  15. Wow you're horrible at explaining things. But it looks like you're data driving your data generation. Little weird but it works. Typically we just tell people to you know.. write that in java... This is nothing close to what we'd want to expose on our end.
  16. Do not make custom Minecraft Launchers, messing with user auth is a bad idea. Also, we do not encourage/support automated installations of Forge. The Minecraft launcher is already portable. You do not need to make a custom one.
  17. Forge Version: 40.0.0 Minecraft Version: 1.18.2 Downloads: Changelog: (Direct) Installer: (AdFocus) (Direct) MDK: (AdFocus) (Direct) However, as this is the start of a new version, it is recommended that you check the Downloads Page and use the latest version to receive any bug fixes. Intro: It's another minor update, which means another major pain! Kidding, but tags and registries were majorly reworked in this update, so proceed with caution. Additionally, Mojang have begun to transition to SLF4J for logging, so make sure to use LogUtils.getLogger() rather than the Log4J variant. Not much to report change-wise since the 1.18.1 39.1 release. Major things to not on Mojang's end tho, is tags have been completely re-written, and vanilla registries are now locked by vanilla code. We unlock them during Registry events so people using those events are fine. However, anyone still constructing their objects in static init will be broken. We told you to stop doing that years ago. We have figured out how we wish to address the major changes with Tags and Registries. So expect a RB in a few days.
  18. Forge Version: 39.1.0 Minecraft Version: 1.18 Downloads: Changelog: (Direct) Installer: (AdFocus) (Direct) MDK: (AdFocus) (Direct) However, as this is the start of a new version, it is recommended that you check the Downloads Page and use the latest version to receive any bug fixes. Intro: 1.18 (38.0.x) is bundled in with this release because it was only out for a very short time. It's been a long time coming - with 1.18.2 dangling over our heads for a while we prolonged the RB, but it's here, and it's stable. Not much API has been added, we spent a lot of time refactoring and slimming unused API. Additionally, we used this time to transition to a new build server, so our capacity to make new builds of Forge has greatly increased. Changelog: New: Add Client-sided Commands Add renderable API to allow easier rendering of OBJ and other custom models The vanilla Gametest framework is now integrated with Forge The character "-" is no longer allowed in modids. VanillaGameEvent was added to allow for globally listening to vanilla GameEvents GameEvents for shears and elytras were added Items can hide parts of their tooltips by default StructureFeatures can be added to tags MobEffects can be added to tags Added the ability to get a Codec for a ForgeRegistry Add ShieldBlockEvent Add RenderArmEvent Added server ping data compression - solves some situations where servers are wrongly marked as incompatible Allow dimension JSONs to specify that the dimension should use the overworld's seed Fixes: Log4J security mitigations for every version released, past present and future Fixed double registry injection when loading single player worlds Fixed RegistryObject not working if created after registry events are fired Missing or unsupported dependencies are now logged, in case they cause a crash before we can show a screen Creating config files also creates parent directories if they do not already exist, as they used to Fixed particles being fullbright for a few frames when first spawning Fixed TerrainParticle rendering black under certain conditions Fixed comparison of custom ParticleRenderTypes leading to broken particle effects Fixed clients being unable to deserialize tags for custom registries Fixed being unable to fetch blockstate in BucketPickup#getPickupSound (for multipley-logged blocks) Fixed custom climbable blocks not sending a death message Fixed modded tools not working on glow lichen Fixed issues when multiple mods declare the same optional tag Fixed `MinecraftLocator` not respecting non-`MOD` FML Mod Types Fixed server side release of custom payload packet buffers Fixed ScreenEvent accepting null screens Fixed getPickupSound not being implemented on ForgeFlowingFluid Fixed LivingExperienceDropEvent not firing, expecially for dragons Fixed String.format calls not having a Locale parameter Fixed LivingDropsEvent not having all drops for foxes Fixed Mob Spawner logic with CustomSpawnRules Fixed regressions for onAddedTo/RemovedFromWorld and related events
  19. Ya I think this is getting along the line of trying to skirt their license for the sake of trying to abuse users for profit. I also reject your assertion that its impossible to produce good mods unless you're paid too do so. Yes, being paid helps you not have to worry about income and other jobs. But that is no guarantee that you won't get "distracted" by other things. Or run into burnout from the Minecraft upgrade grind. However the ONLY legal way to make a mod for profit without violating the EULA is to get explicit permissions from Mojang to form a business relationship with them to utilize their IP for profit. Good luck doing that. I don't think this needs to be discussed any further because your intention seems clear.
  20. TLDR: We live in Mojang's good graces and legal grey areas. Forge is not `designed to allow profiting` It was designed too help people not violate the EULA's 'dont distribute our stuff' part. Basically, if you're asking this question then you're most likely going to violate their EULA. Just make mods for fun, and if you host it yourself feel free to put non-intrusive ads on your page. Do not say "Pay be $10 and you can have access to my mod" But again, nobody here is lawyers, nore would it have any effect if Mojang decided to go after you as Microsoft has more money then you do, and we all know the side with the most money wins thee lawsuit.
  21. 1.8 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.
  22. "Multi-threading" isnt a magic fix. Often times throwing more threads at something can actually be MORE detrimental to performance. Because of all the stuff that needs to be done to make things talk safely across threads. Beyond that, we can not speak to what Mojang intends to do in the future as we are not them. What we can say is that they know performance is an issue and will address it as they see fit.
×
×
  • Create New...

Important Information

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