I may be wrong and haven't tested it for a long time, but AFAIK the FCodes ARE case sensitive. Only the lower case version "mf?" should work.Samuelt86 wrote: You can set a Universal Minefield code by setting one of your planets with a FC of MFx where x is any charactor. The M & F are not case sensitive. So it can be MFx, mFx, mfx, etc.., All your minefields will then have that FC.
http://www.xs4all.nl/~donovan/help/mine ... iendlycode
The FCs are case-sensitive. Therefore "mft" will not work, while "MFT" will....majorm wrote:but where do I see which universal code actually "works"? I set one of my panets fc to mft and now, a turn later, the starcharts show the same different fcs for the minefields.
Somehow I missed this topic.majorm wrote:Maybe this is a newbie question but I didnt find it anywhere at Donovan's.
Many Minefields of mine have the FC ATT or NUK, I don't want to change them because the planets need them. Could an enemy get a hit if he sets his fc also to ATT or NUK?
I have written a host-addon that runs in both AUX1 and AUXBC. The first part changes all ATT/NUK commands to a random 3 character selection. The second changes them back to ATT/NUK.B A N E wrote:How to get around this problem...
PHost is solution #1.
In THost games, the only alternative to protect NUK & ATT codes
from easy transit is to employ minefields with centers not on the
planet you're wanting to use NUK on.
Planet A has NUK
Planet B has ???.
Minefield centered on planet B, overlaying Planet A has the ??? fcode.
Users browsing this forum: No registered users and 1 guest