
Agenta
A authserver and skin fix for legacy versions of minecraft.
Screenshots






About this Mod
Agenta
A authserver and skin fix for legacy versions of minecraft.
Compatibility
Requires Java 7. (In theory this can be built for Java 5, but I lack the build tools required for that.)
If running this on Java 12 and newer, please add the following JVM argument: --add-exports java.base/sun.net.www.protocol.http=ALL-UNNAMED
- As a mod: The same Jar will run on forge, bukkit and Risugami's modloader for Minecaft versions Alpha 1.0.4 to Minecraft release 1.7.10 (These are merely the versions I tested)
- As a JavaAgent: Add the following JVM argument:
-javaagent:{path}/agent.jar(replace path with the location of the agent.jar) - Inline/static: In this setup, Agenta is essentially taking over the role of Launching minecraft. Add the following JVM argument and change out
{mainClass}as needed depending on which minecraft version you are launching:-Dagenta.main.class={mainClass} - As a Bukkit plugin (Tested with bukkit for Minecraft Beta 1.2_01)
JVM/Congig settings
Non of these are needed to launch Agenta. The available contexts are
"*" => ALL
"static" => When Agenta is launched as the main class with the expectation of chainloading another class manually.
"config" => Only appears in the config file.
| Context | property | Argument | description |
|---|---|---|---|
| * | agenta.assets.fml | -Dagenta.assets.fml={value} | A link to an archive Agenta should forward legacy forge download requests to |
| * | agenta.assets.index | -Dagenta.assets.index={value} | The URL for the asset index Agenta should use as a base |
| * | agenta.assets.routing | -Dagenta.assets.routing=true | Should agenta reroute requests the mojang's asset servers? (default: "true") |
| * | agenta.assets.url | -Dagenta.assets.url={value} | The URL for the resource server Agenta should pull assets from | * | agenta.prt.color | -Dagenta.prt.color=false | Pass the value 'false' to disable colour printing. |
| * | agenta.prt.debug | -Dagenta.prt.debug=false | Should agenta show debug messages? |
| * | agenta.save.file | -Dagenta.save.file=saves.json | When handling saving for certain versions of old Minecraft that relied on long dead mojang endpoints, what should agenta call the save file? (default: "saves.json") |
| * | agenta.skin.resize | -Dagenta.skin.resize=true | Should agenta try to resize skins from 64x64 to 64x32 for better compatibility? (default: "true") |
| * | agenta.skin.merge | -Dagenta.skin.merge=true | Should Agenta take multi layered skins and attempt to flatten the layers down? (default: "true") |
| * | agenta.skin.cache | -Dagenta.skin.cache=true | Should agenta cache skin lookups? (default: "true") |
| config | agenta.config.version | The version of agenta that generated a set config file. Will be used to detect if agenta should upgrade a set config file | |
| static | agenta.main.class | -Dagenta.main.class={value} | The class Agenta should try to load next when running in static/inline mode |
Fixes
- Skin support for pre 1.7.10 versions
- Cape support for pre 1.7.10 versions
- Sound for versions of the game that predate 1.6
- World savings for certain pre-alpha builds (experimental)
- Forge 1.5.2 being unable to fetch it's library files (experimental)
Note
- The same jar will work for almost every version of minecraft that predates Release 1.8
- Any miscellaneous fabric based modloader should be supported.
- NilLoader can load Agenta. (Agenta doesn't meet the criteria of a NilLoader mod)
- Some ancient versions of Forge/modloader may require you to load Agenta as a jar mod.
- LiteLoader inforces compatibility checks and so can never be fully supported
Available Versions
How to Install Agenta on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set babric Loader
In the panel under "Egg", select the babric loader and matching Minecraft version (1.7.10).
Install Mod
Open the mod browser in the dashboard and search for "Agenta". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.7.10, 1.7.10-pre4, 1.7.10-pre3 (+158 more)
Server-side
~ OptionalRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Agenta server crashes on startup – what to do?
Most common cause: wrong babric version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.7.10). You can switch loaders with one click in the panel.
Is Agenta compatible with babric and bukkit and fabric and forge and java-agent and legacy-fabric and modloader and nilloader and ornithe and quilt?
Agenta officially supports babric, bukkit, fabric, forge, java-agent, legacy-fabric, modloader, nilloader, ornithe, quilt for Minecraft 1.7.10, 1.7.10-pre4, 1.7.10-pre3. Note: Forge and Fabric mods are NOT cross-compatible – pick one loader and stick with it. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Agenta – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Agenta consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install Agenta with just one click on your server.