ZDoom

Had a couple ideas.

[b]LoadMessage[/b] - (FileName, MessageNotFound, Color NotFound, MessageFound, Color Found)
Gives the ability to print a message based on if the file is found or not along with a color to highlight them in.

In addition this could also be useful for LoadRequired so I can use it to instruct people for D4D that the D4DResources.pk3 needs to be in the same directory as the data package.

Very well then. I'll forget the rest and just say, a REQUIRED version of Load would be appreciated then.

At least people will then recognize they forgot to download something else.

pre-loading a required base mod is perfectly acceptable, but this really makes no sense at all.

[quote="Gez"]No, that doesn't sound like a good idea. I really don't like the idea of enabling a mass loading of everything that fits such a flimsy criteria.

Make a batch file if you want that kind of things.[/quote]
While I wouldn't put it quite like this myself, I'm inclined to agree. I don't think it should be a mod's business to be autoloading other mods. A batch file or detailed instructions should work just fine. Plus, doing it this way would confuse people who actually know what they're doing when they decide "I want D4D with D4D_Addon_splurbyfoofoo and nothing else", load just those two with ZDL, and wind up having all the addons in the folder loading anyway.

No, that doesn't sound like a good idea. I really don't like the idea of enabling a mass loading of everything that fits such a flimsy criteria.

Make a batch file if you want that kind of things.

Nah, just optional stuff so people don't have to screw with things. Like for instance, it'd be pretty neat if it could take "D4D_Addon_*.pk3" where the * can be whatever is after it. Of course that's for optional loading.

Then it's the role of the add-on to LOAD the already-existing stuff; not the role of the main mod to force loading of every add on that might be present on the disk.

D4D has addons developed by other people. What better of a way to offer easier support than perhaps a naming convention of sorts? I mean, yes, I could just throw in another .pk3 with LOAD involved after D4D.pk3 but that's even more micromanagement people have to deal with regardless.

For the first, I'd call it just REQUIRE instead of LOADREQUIRED.

For the other two, what's the point of loading after? Give some reasonable use-case, because the more I think about it, the less likely it seems to be actually useful.

LoadRequired: An alternative to Load, which will abort the game launch if the file isn't found.

LoadAfter: Loads the files after instead of before.

LoadRequiredAfter: Combo of the two above.