Using new invisibiliy types to simulate other senses

I have been working on a modmod of Orbis, the modmod of FfH but will post the question here as I feel it will develop into a nice little discussion thread. If the moderators think it should be moved, then please move it.

What I would like to do is use invisibility types to simulate sense such as smell, hearing and perhaps others such as psychic abilities for fantasy mods or radar, electric impulses, etc. for sci-fi mods. Using the wonderful editor developed by Kael and expanded upon by Ahwaric in his Orbis modmod, I was hoping to add abilities to "see" units other than by increasing their visibility range. I was also hoping to have varying degrees to which a unit will "hear", "smell", or sense another unit.

That's what I want and here's a simple example what I figure is possible right now and what I hope we can implement:

The Idea


I hope that makes sense. There are some problems I have with how this would work:

The Problem



Here are the ideas I propose for solving the problem.

Theories for Improvement



I am not sure what sounds best and what is possible so I am asking for everyone's input and ideas. Hopefully I have explained the desired effect well enough, but if I haven't then please ask. Thanks.

If you modify the DLL as well, this is pretty simple. Since you reference the editor Kael made and Ahwaric expanded on, that seems to imply the XML editor, and thus being uncomfortable with even XML modification though.


The way that invis works now (note for other readers, this is specific to Fall Further and those who imported my work) is that you can list multiple invisibility types per unit, and any unit can see them only if they can see through EVERY invisibility type on that unit.

For your purposes, you need that to be exactly reversed.

What you would do, is grant all units who have hidden their scent INVISIBLE_SCENT, units who don't reflect light would be INVISIBLE_SIGHT, units who make no noise INVISIBLE_SOUND, units who leave no tracks INVISIBLE_TRACKS and so on.

Then you would need to modify the DLL (pretty simple modification actually) to reverse the logic and only require that you see through ONE of a unit's invisible types to actually detect them. The more complicated issue though would be making sure that if the unit LACKS any specific invisibility type that other units are still able to detect them.

Another complication would be that promotions can add as many invisibility or see invisibility types as you desire, but they cannot REMOVE either of them (except by being lost of course).



What would be a bit easier probably would be to add a completely new element to visibility which works opposite of invisibility, making units more sensitive to certain "sense types" and allowing units to better mask various sense types. Then you can set up unique vision ranges for each sense type (longer/shorter than sight range) and make it so that unless a unit is masking in a given sense type, it is revealed when within range of someone who possesses said enhanced sense.

This approach would do exactly what you say you desire, but not actually link to invisibility at all, and require semi-hefty DLL work.

It's interesting that you say the one with the heavy DLL work would be easier.

I am very comfortable with XML editing; I was just saying the editor is wonderful because of the time it saves. In fact, I edit the VB so I can add my own items to the print out.

If one could direct me to the files needed for flipping the Boolean invisibility logic, then it might be worth a try.