Maybe it would be more interesting if this "mutator" will be integrated in a patch plugin for NavAdder. Plugin is loaded, plugin is looking for mutator if exist in system whatever U files path, if mutator is found will operate minimal tweaks if something else is needed for that map and will do a Package-Mapping automated. If mutator is not found, will do paths tweaking inside doing what mutator does - except doors attack, these won't have direct references just testing presence and using if it's available. If it's used only as permanent CTF mutator will have no use outside of CTF-Niven map. And btw... map has a light deleted but lightning was not rebuild, map having reference to deleted Light118, lol:
Code: Select all
Warning: trying to archive deleted object: Light118
As a technical question aimed at experts: Is this possible to be brought back in stage somehow ? Where is this stored and in which format ?
This map do seems another experiment named in similar way with words "Experimental Lab", AvgAItime value stored in LevelInfo is -0.000000 - this is evidence that drinking and mapping in the same time was never good... or this was exactly the experiment in cause... UT_FlakCannon has no ammo in here out of DMMutator...
Edit: My Bad, there are more deleted objects and map not rebuild:
Code: Select all
PathNode58
..
Light128
..
Light43
..
Ahem, I was able to recover Light118 but... I don't think I can bring it back in run-time...
Edit2: And missing PathNode58 has a path[0]=359 referenced and it is referenced in PathNode59 as RouteCache, which exist in map. Now I'm curious to find what does that means reachSpec 359... Why I'm not surprised about dumb Bots at random ?
Edit3: Phew !
ReachSpec 359 means:
MrGarbage wrote:
=359 Start=PathNode56 End=PathNode51 RFlags=Walk =1 Dist=287
This deleted node actually has only crap inside as "awesome" as it is "archived ?", map being saved without rebuilding changes. I think it needs patched and Paths[X] from PathNode56 has to be loaded with reachSpec 359 as upstreamPath[x] from PathNode51 needs this reachSpec too...
Edit4: I got it, Number 359 is a pruned one located in PathNode56 - referenced by a deleted PathNode located nearby the other Base...
Anyway... I found how to hunt ALL reachspecs from a map, because some maps have more reachspecs than referenced in navigation network, the real number... For now, I can keep for me what I found - I don't want to awake a storm...