LexManos

Because of people like you who insist on taking our time harping about old versions. If you guys kept it private or elseware then sure people could help you. But you don't, you make mod packs, have issues, or whatever, and then you/your users come to us and waste our time. Combined with what you just said, all issues that you have for old versions have been asked and answered many times while the version was relevant. We have a limited manpower thing, so we've decided that it's best to focus on things that actually need fixing, and not 5 year old tech. We don't care that you like spam clicking your sword instead of waiting on the cooldown. We work on Modern Minecraft.

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

Forge Version: 36.2.0 Minecraft Version: 1.16.5 Downloads: Changelog: (Direct) Installer: (AdFocus) (Direct) MDK: (AdFocus) (Direct) Intro: Lots of new features and bug fixes. However 1.16.5 has been super stable for the last several months so we've spent most of development time has been focused on the 1.17 update. Changelog: New: Added a custom TextureAtlasSprite loaders for blocks that want dynamic textures without a fancy renderer Added a data generators for sounds.json files AbstractFurnaceTileEntity now uses the more versatile `IRecipe.assemble` function result SmallFireballEntity no longer checks the mobGriefing gamerule, in favor of the MobGriefingEvent Piglins now use the MobGriefingEvent when deciding when to pick up items Furnaces now use the IRecipeType of the current recipe when calculating burn time Draining FluidSources is now respectful of the FluidStack being removed PlayerEntities now have a knockback attribute The knockback calculation in `PlayerEntity#attack` has been updated to use the attribute added above Potions have had some Quality Of Life improvements Allow custom ladders to make trapdoors climbable Added some ATs to DimensionSettings to ease their use Allow any Block to announce itself as a potential respawn point Added a new `ProjectileImpactEvent.FishingBobber` event Removed a Nullable annotation from `canCreatureSpawn` which was causing misleading assumptions Removed a faulty patch from the `Entity` class Allow mobs to use custom ranged weapons Allow customizable damage from Lightning Entities Added a dummy `connection` to FakePlayers Fixes: Fixed an ongoing issue where removing a mod from a LAN world would make it unconnectable Fixed an issue where sometimes the gradle runClient/runData/runServer tasks failed with the message "Unable to locate class file LaunchTesting" Fixed Forgedev environments so that they no longer crash with classloading issues when running the "forge forge test server" configuration Synchronized `ResourcePackList#addPackFinder` in an effort to remove a race condition Fixed some vanilla block model mirroring and rotation issues (MC-227255, MC-134110) The URL button for a mod in the Mods menu has been realigned with the text `PacketBuffer#readLongArray`, `#readSectionPos` and `#readString`'s are no longer removed on one side Fixed an obscure chunk loading deadlock when calling `getChunk` Fixed shift-scrolling on Macs Fixed mob kills not being assigned properly (MC-121048)

Yes, old versions are not a priority, and are easily fixed if you google/search for yourself. But you're right seems the mirror that the EAQ was linking to went down. I've fixed that.

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.

Dormant chunks wont solve networking issues. It just saves IO time on the server. So it all depends on what actually is taking all the time. There really isn't much you can do until you identify what the issue is.

The license is clear, but we prefer you do not. As people downloading the installer is how we pay for the severs to run this.

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

1) This isn't a suggestion so it shouldnt be in the suggestions forum 2) Yes, there are tons of virus sites that package freeware in their adware/virus installers. Only ever download things from the original source. Here. 3) We do not place actual links to those sites here because web crawlers like google will use the fact that we have a reference to them to boost their results in search engines. ESPECIALLY don't do it 7 times in 20 mins -.- That is what's called spam and makes us think you're just advertising for their site.

You don't run mods. You put them in the mods folder.

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

https://forums.minecraftforge.net/announcement/15-java-16-and-you-how-to-avoid-crashes/

1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Also, common sense/and actually putting in effort by using the search feature of this site would answer your questions. That is the reason we lock old threads, because the questions have been answered a thousand times before during the supported lifecycle of that version.

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

Javadocs are built off crowdsourced mappings/docs that change depending on the status of the crowdsourced projects. So, no there is no good javadocs project or website because they always change. You're more then free to build the javadocs yourself for your workspace. And/Or use your IDE's built in javadoc reader. The only/best official docs are https://mcforge.readthedocs.io/en/latest/ created by users in this repo: https://github.com/MinecraftForge/Documentation

The official documentation, IS minecraft itself. Forge only ever officially supports the version of Java that Minecraft was built for. Any other version of java may or may not work. There is no guaranteed. Forge 1.16 DOES work on 8->17. But you have to do some extra things for 16+ And thus is not supported.

The only thing we 'zip' is the world folder when it detects that something might be broken and/or might break. So just unzip your backup into the world folder and it should be fine. Nothing just randomly zips things.. so there is no way to make it 'stop' because it shouldnt be doing it.

This should have nothing to do with the disc it's on. I constantly work on the Z drive and it works just fine. Also, i would advise against using MCreator, as using a normal modding system is recommended so you actually understand what you're doing.

No. Microsoft wants to charge stupid amounts of money to stop marking unknown exe's as viruses. The Jar works on all operating systems that have java installled. All the exe was was a wrapper around the jar that automatically found java for you. So no. Unless you wanna pay the crapload of money it costs per year to shut up Microsoft's 'anti-virus'.

Try 1.16.5-36.1.25 and provide us with the logs from both sides. I added some extra logging to make it easier to figure out what packet is being bad.

Really old Minecraft versions are no longer supported on this forum. Please update to a modern version of Minecraft to receive support.

I guess they could edit the level.dat... but why would you. Stop trying to work around a system designed to do what you need

Data packs are config files

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`

If it says the mod is not valid, then it's not valid. You'll have to make sure you got your mod from a legitimate website. Also, whenever you're asking for help, post your log file.