The REASON it came to mind tonight is because I have found that I MUST copy the Huaramarca system in my adventures or risk an eventual error in the debug or the system simply not being created at all. ( i used a god mode to list the systems created and it was not in the list.......which made me upset because i had to get into it !!!!!

===================================================
Taking the prospect of compelling .xml makers to go full monty into adventures http://www.neurohack.com/transcendence/ ... 144#p41144
instead of a "weapon here and a shield over there "
I like this part because in an Adventure you can virtually do anything

However, file sizes are an issue. IF the .xml must copy out everything they want included : I think it would be easier if the database had an order to call on to EXCLUDE rather then have to include everything: like CorporateOnDestroy.....you can set your adventure with a Global to ( on Global System Created )to call or block parts like : initDomina ( includes Domina powres / stations); InitSisters ( excludes Domina powers / stations ).
This would be simpler and cost less in file size while giving George less "bug" issues and the person making the .xml more freedom to include or not exactly what they want from different modules.
And I think the orders should be in the database : and the game version would have to call them up as well : which would give the person editing .xml the ability to simply copy the virtual station and erase the parts for modules they do not want in their adventure.
then the Wiki makers would have fun keeping up with THAT

thoughts? can it actually be done? if it were a global virtual station I think it would save everybody work and file sizes
(( ******* note, no fancy long code required : I hate long code versions they bug the game, Iam sure your far superior minds can make on and off switches for various modules in the database )