Quest for standard

[lxndr]

1. Knowing which mod requires which extension quickly becomes a true nightmare when you have say hundreds of mods.

2. From an engine/software point of view, there's no easy/clean way to determine this.

So, here my request for a new standard:

<basedir> / <gamedir> / ext.cfg

This file would list all required extensions so that engines could automatically load them before loading maps, or inform the user when they are missing. Example:

quoth

[Baker]

Really that topic is far better suited for Inside3d.com, where that kind of thing gets discussed and even sometimes acted upon.

It's true that some of those things are very problematic. Some mods even only run on specific non-current versions of a single engine.

[lxndr]

Really that topic is far better suited for Inside3d.com, where that kind of thing gets discussed and even sometimes acted upon.

It's true that some of those things are very problematic. Some mods even only run on specific non-current versions of a single engine.

noticed, please forgive me for my other related thread.

[MH]

Yup, there's a lot of standards discussion going on at I3D and I think this is a really good idea; it's about time that there was a way for a mod to advertise it's requirements.

[R00k]

Over 90% of the mods are geared to the original built-ins, otherwise mod authors could have a readme in the installation that states which engine it was intended for and or the list of protocol extentions that it uses. Otherwise you might just get a protocol error stating builtin # 332 not found crash!
Trying to make a mod to run on all engines may be limiting, at the same time trying to make and engine to run all mods might be overkill.