Version Strings - skipping the mod the correct way...

[Botjoe]

I'd like my mod to only load on versions I expect (1.9 after 1887 or 1.9.4, and not be attempted to be loaded on forges for MC 1.8.x or 1.7.x, or any 1.10) forge.

 

I have dependencies set, but that's not really what I want, nor is accepted version. I am used to maven version strings, but I just want to know, how do I get forge to not generate an error on any newer or later version of anything. I'd like it to skip my mod correctly.

 

Most mod seem to use dependencies=""

 

@Mod(modid = CommandRunnerMod.MODID, version = CommandRunnerMod.VERSION, acceptedMinecraftVersions = CommandRunnerMod.ACCEPTED_VERSIONS,dependencies=CommandRunnerMod.REQUIRED_AFTER)
public class CommandRunnerMod
{
    public static final String MODID = "CommandRunnerMod";
    public static final String VERSION = "1.9.4";
    public static final String REQUIRED_AFTER = "required-after:Forge@[12.16.0.1887,]";
    String [] strFiles;
    public static final String ACCEPTED_VERSIONS = "1.9,1.9.4";

[Botjoe]

Thank you. Currently, my installed Forge 1.9.x (e.g 1887) does not activate some 1.7.10 mods ('sureen') in the same directory, with out error or comment. The 1.7.10 mods are only active (Instantiated) in 1.7.10 forge, and they don't activate in 1.9 forge. OK, I see that fml is no more, so it's supporting a prior behavior. 

 

Adding and deleting mods in a directory I'm used to, but not pleased with.

 

Is there a better practice, that I'm missing? since it's not acceptedSaveVersions or anything else. Is there a way to self disable before the loader? 

 

I'm looking for a quiet dontLoadMod.

 

Is there another (looking at Loader.java for one, i don't see one) practice, that I am missing?

[LexManos]

https://github.com/MinecraftForge/MinecraftForge/blob/master/src/main/java/net/minecraftforge/fml/common/Mod.java#L104

You need to use a range notation, what you want is [1.9,1.9.4]

[LexManos]

Errors are good, if he wants to 'silently ignore' then write his mod class as a slim class and don't do anything if it's the wrong version.

[Botjoe]

Errors are good, if he wants to 'silently ignore' then write his mod class as a slim class and don't do anything if it's the wrong version.

 

Not really looking to ignore errors, I prefer the mod to be ignored, in the any unsupported versions. Errors are good, but only when it's obvious what to do next.

 

What I'd have as my use case is ...

1) Loader checks versions.

2) If not in versions, then ignore mod. Not ignore errors, handle errors by not activating.

 

Does the slim class still show up a loaded mod? Yes. A slim class is OK, but is out of common practice.

 

The alternative use case is to be obvious to the user. Either having some better help message saying 'Recommend to have a separate game directory for each forge version's profile', or a help screen available from the ForgeGuiFactory config (About Mods).

 

 

[Botjoe]

It's that the error is displayed and the game stops. I have no big objection to a displayed error, i do object to errors that don't have a clear resolution for the end user.

[Draco18s]

You can handle the versioning error yourself, if you'd like.  There's an event for it IIRC, and you can display your own error screen.

The "easy end user solution" for using the wrong version is "stop being an idiot and use the right version."

[LexManos]

We've made the error as clear as we can. If they dont understand 'this mod wants a different version of minecraft' then there is no hope for the user.

Just use the mechanics we have in place.

[Botjoe]

Closing the thread for now. Rethinking how to make it easier.