Archiving

[cpw]

I intend to archive this repository at the end of July 2025. Post reasons not to in this issue. Thank you!

[Asbestosstar]

Integrating it completly into NeoForge makes it harder for projects which use ModLauncher or projects which want to build against only ModLauncher but not NeoForge itself for the purpose of writing services to be run across more than 1 loader which uses ModLauncher.

[TelepathicGrunt]

In my honest opinion, I think ModLauncher repo should not be archived. There's no reason for archiving tbh. I would like to see it remain up. Maybe an unlikely someone will come along and help contribute to it to revive for things not NeoForge.

It is a great project with a lot of history and work poured in. It should remain up

[zaaarf]

Uh, I haven't really been following the Neo/Forge side of things. Is this gonna be inseparable from NeoForged now? Is NeoForged gonna fully replace it? What about regular Forge?

It's kind of a shame for this to go. I have a project a project that works with this. Though I haven't used it with this in a while, I imagine it still works fine. I imagine that this getting archived would mean that I have to make loaders specific to forge/NeoForged, which I'd hoped to avoid.

[FinnT730]

@zaaarf Forge has their own fork of it, so that wont be a problem

[Asbestosstar]

That lilloader looks pretty cool,i prefer to write my transformations with byte[] in javassist but sometimes still use classnode El vie, 25 de jul de 2025, 16:28, zaaarf ***@***.***> escribió:

…

*zaaarf* left a comment (McModLauncher/modlauncher#135) <#135 (comment)> Uh, I haven't really been following the Neo/Forge side of things. Is this gonna be inseparable from NeoForged now? Is NeoForged gonna fully replace it? What about regular Forge? It's kind of a shame for this to go. I have a project a project <https://github.com/zaaarf/lillero> that works with this <https://github.com/zaaarf/lillero-loader>. Though I haven't used it with this in a while, I imagine it still works fine. I imagine that this getting archived would mean that I have to make loaders specific to forge/NeoForged, which I'd hoped to avoid. — Reply to this email directly, view it on GitHub <#135 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC76KQQMOGSQBWV76GDREED3KK4TDAVCNFSM6AAAAACAGL457WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMRQGY3DSOBWHE> . You are receiving this because you commented.Message ID: ***@***.***>