LexManos

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.

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.

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

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.

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.

You don't. MCP is Dead.

MCP is dead let it rest.

1.8 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.

"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.

We have decided that it is a far better user experience to get real feedback if you install a mod incorrectly. In the cause of mods for wrong versions this is doubly important because if you share the same worlds directories, and load a world in the wrong version/mod set, then you could easily lose data from that world. What you're advocating for is explicitly to make it LESS clear to people who do not get the correct versions of mods, by almost silently ignoring them and pretending like everything is fine. We find that the use of launcher profiles is not a overly complicated ask, and most people can figure it out fine. So that is our recommended approach.

As he has already told you. We no longer release the 'windows installer' Just use the jar installer it works on all operating systems.

Use 109+ I'll rebuild the handfull of installers when i get a chance.

Use 109

"I launched the vanilla server, why didn't it make a mods folder?" Also, 1.12 is old you can find the answers yourself if you do some searching, as they have been answered a thousand times while 1.12 was still supported.

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.

https://maven.minecraftforge.net/net/minecraftforge/eventbus/3.0.5/eventbus-3.0.5-service.jar https://maven.minecraftforge.net/net/minecraftforge/accesstransformers/2.2.0/accesstransformers-2.2.0-shadowed.jar TLDR: The vanilla launcher is crap, so we have to do a work around which is screwing up on creeperhost.

You have some extension installed on your web browser that is hijacking connections to adfoc.us. If you don't want to support us by looking at ads, then you can use the direct links.

That is something to ask your 'paid host', as you're kinda paying them.

Unfortunately, this just isnt something that the forums supports. Especially the deletion of your own account. We have to do all that stuff manually, which is really annoying.

1.8 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.

u301 should have the LetsEncrypt certs. You can try J11 or J9. Make sure to be sure you're running the lava you think.

Installed TCon, Mantle, and Tag Tooltips. Looks like it loads the data just fine. I would blame some other mod you have installed interfering with the tag system. Most likely, you have another mod that is loaading after TCon that is overwriting the ingots tag. Which is why adding the json as a datapack after the fact makes it 'work'

Your report is very hard to actually understand. Your best bet is to stop trying to 'describe' the issue and provide the actual tag files and what you are expecting to happen. Because all of our tests in tags work just fine. Also, there is no 'registering' of tag in the sense you're talking about. All tags are 'registered' when they are read from disc in one pass. So ya, provide us a test case of your tags and we'll see if it's a real issue or not.

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.

Keep avoiding answering my question by asking other unrelated questions. But i'll humor you. It's been something we've been thinking of doing ever since the first person ran the wrong jar. So probably about the 1.3 days. So, now answer my question.