Good idea, the only possible problem with that is that there might be resources in the Nova files that I would need (asteroid graphics, some STR# resources, interface graphics, etc...). I'll have to take a look at the Nova files to see what's where.
If Matt Burch reads this, perhaps you would be able to sneak into the next update a (new) resource with a single field (or use a smaller resource like the colr resource) which could be set to a non negative number (basically a boolean) if we wanted only the plugin's resources used. So when Nova loaded, if the field was set to a value not 0 (0 being default), then it would ignore the Nova resources if (only if) the resource type was present in the plugin (so if there's any ship resources, it would ignore Nova's. On the other hand, if there isn't the resource type in the plugin it would use Nova's). Of course the graphics would be exempted (so we could still use some of Nova's graphics, but not all), it would just obey the existing rules regarding plugins. The Nova data could still be loaded, just not used if it meet the requirements (of that resource type already existing in the plugin).
------------------
Phoenix
(url="http://"http://www.outpost.web1000.com/nemesis/")EVN Nemesis(/url)
(This message has been edited by Phoenix (edited 05-03-2003).)
(This message has been edited by Phoenix (edited 05-03-2003).)