A 1.16.4 release. Please consider the following.

[WilliamBlaze]

Quote from TCreopargh >>
"Currently have no plan to port it to other versions because most big modpacks are on 1.12 and I believe higher versions usually do not have low memory problems."

That is a misconception.
For you see the very issue your mod is made to correct is triggered in all versions of minecraft whenever a set of mods or a "mod pack" has 51 or more mods active at a time. And for each single mod added past that 51, the issue compounds exponentially.

Especially if your trying to play newer version(s) of minecraft on an older pc.

Let me give you an example of such a PC:
A Desktop, made by dell from 2012, with all the standard parts, save for the extra component of an old Nvidia GeForce GT 530 graphics card on top of that standard build.

Not everyone can afford a fancy new gaming PC specialized purely for high end gaming to play their PC games on, and your mod fixes a problem that has existed since the beginning of the Minecraft moding scene.

A problem mind you that really should have been addressed by its own developers; but has been grossly overlooked in favor of milking their product for more money in place of perfecting it before adding newer content.

My case and point being though is, as someone developing a mod pack with 75+ mods for 1.16.4 - it's a real pain in the arse trying to run tests on mod compatibility for this thing when the damn low memory issue keeps screwing up the works in every 5 mins.

if you need an exact time. its every 4 mins and 32 seconds of gameplay and then the stuttering begins. and then from there, after 8 mins and 12 second, everything begins freezes if I'm not in a menu screen. And finally after 10 mins Minecraft becomes absolutely unplayable. Forcing me to use task manager to force an End Task on Java itself to close out because at that point Minecraft has become "unresponsive"

I've had issues like this with modded Minecraft back in 1.12.2 when attempting to make custom mod packs, but never were these issues occurring as fast as there happening in 1.16.4

It usually would take almost a full 2 hours in 1.12.2 before I would hit a snag that forced me to fully close out the Minecraft client and reload the entire game from the launcher. Your mod Fixes that issue for 1.12.

What I'm trying to say is, You've made an amazing mod that fixes to a piss poor problem that no one has had a correct solution to correcting in literal years. A problem that has only gotten worst in the later versions.

This could be THEE most essential mod in Minecraft moding history; and if I have to I will screenshot all the mods I'm working with just so you can attempt recreating the pack yourself to see just how bad the memory issues get in 1.16.4 if necessary to prove it.

So I would beg you to reconsider.

[TCreopargh]

Hmm maybe not that essential because this mod just does explicit garbage collection and jvm is collecting garbage all the time, but maybe I'll do a 1.16 version when I have time for this.