Same, but I can do it when neededI'm going to end up writing a script for it. I just need the mod side done first, which will be partly my job and mostly Striking's. I honestly prefer not to deal with the Minecraft end too much.
Same, but I can do it when neededI'm going to end up writing a script for it. I just need the mod side done first, which will be partly my job and mostly Striking's. I honestly prefer not to deal with the Minecraft end too much.
But i will have to work with GUI things, which I'm terrible atSame, but I can do it when needed
What happens if there are two mods with after:* in the game?@Mod(dependencies = "after:*"), or use FMLLoadingCompleteEvent.
I'll use FMLLoadingCompleteEvent. Didn't know that existed, and that will allow me to do it for this more generically (like doing my mod along with all others)@Mod(dependencies = "after:*"), or use FMLLoadingCompleteEvent.
It looks fine. Striking's parsing may need to be redone depending on how he did it, though.A small question though, wouldn't it be better to check for each mod as soon as it gets registered, and spreading it out, instead of checking 200 mods at the end?
Oh, and I can see some room for improvement in IUpdateable. It's somewhat overcomplicated at the moment. I'll take a closer look at it tomorrow, and open a PR with some minor changes if I find it fitting.
YAML would combine both YAML and JSON. As YAML 1.2 (and 1.1 practically) is a super-set of JSONOkay, people, so would everyone be okay with YAML and not JSON, or is a choice between the two a must?
I happen to dislike the indentation requirement, but I'm asking the community so we have an accurate representation over which is preferred.YAML would combine both YAML and JSON. As YAML 1.2 (and 1.1 practically) is a super-set of JSON
...YAML can interpret JSON...that is what I'm saying...if you use a YAML interpreter people can use either YAML or JSONI happen to dislike the indentation requirement, but I'm asking the community so we have an accurate representation over which is preferred.
I'm sorry, I blame misinterpreting context....YAML can interpret JSON...that is what I'm saying...if you use a YAML interpreter people can use either YAML or JSON
Title screen and ideally somewhat like the ingame mod list.Well, I need to know what you want it to look like, where it should be located, etc.
How yours does for regular updates on the main menu for all updates. For severe updates do what yours does for the stopping of loading at a dirt screen. For critical updates in-game like Reika's. I'll add auto-download and all that from then on.Well, I need to know what you want it to look like, where it should be located, etc.
You could place it in a different position. And also just surround your code with optionals. If UpToDate is loaded then use it to check your updates, if it isn't then you use your version checkersWouldn't that conflict with my mods?
And for every mod that has a version checker and/or wants one, I would recommend doing this rather than requiring UpToDate as a dependency.You could place it in a different position. And also just surround your code with optionals. If UpToDate is loaded then use it to check your updates, if it isn't then you use your version checkers
Yep, because hard deps are usually not niceAnd for every mod that has a version checker and/or wants one, I would recommend doing this rather than requiring UpToDate as a dependency.
Well, sometimes they're needed, like with libraries.Yep, because hard deps are usually not nice