[TEAM] Modloader GitHub Repository

[Daemian]

I'd love to help out, but I don't know Java.

You could help by testing and giving advice on how to solve stuff or what to implement.

I think the loader is ok to use right now -I use it while testing my mod-, but it would be better if we add some more functionality to it.
Cause right now it just makes a list of mods and runs them depending the OS.
It's a good start, easier for modders and users, but it needs more.

For the shaders deal, how about this:

Whenever the user starts a given mod, the loader:

• Checks for .glsl files inside the mod dir
  
• If any, it moves them to [game_dir]/core/shaders (just temporally)
  
• Instead of replacing the original files, it renames those to .glsl_back (or whatever)
  
• Runs the game, user plays.
  
• When the loader closes, it makes a check: looks for any .glsl_back, and renames them back, removing the custom ones.
  

Example, let's say I upload a mod, let's call it Rabbit. I include my custom shader in Rabbit/MyShaders

When people use the loader with my mod, it finds my shader in there, and places it in my game dir/core/shaders but it does not replace any files, it just renames the originals and places the custom ones.

So, my custom shaders get included when the users launch my mod. And it gets rid of them later, when the user is not using them.
Would this work? I think this it's the proper way to go.

As for the %my documents% issue, you could save the file (modloader.properties) in the same dir the loader was opened from.
If the user starts moving the loader around his disk, hopefully, he moves both files or the whole folder /ModLoader.
The worst thing that could happen is that he/she has to set his/her preferences again.