I think it's a plugin to store tech information that can be used for the next map. For example, if you unlock a tank in one map, the plugin will store that data so that the tank is buildable in all maps from then on.

Not exactly, though that is one use. ...Basically, it would let you write stuff to a text file and then read it back later. So, you could have the above scenario, where getting access to tanks in one mission lets you use them in future missions; however, you could also use it in other ways, such as giving the player some extra (non-plot-critical) heroes who can be lost, but don't show up in future missions if they are, etc.

IskatuMesk wrote:
Code information for Firegraft. Think Thundergraft, Limit Expander, other stuff of that level. Ultimately it equates to reverse engineering the game.

Sounds powerful. I just googled Limit Expander, is it still unstable or has it been improved? Seems like you used it for AO, did it work fine?

AO has an unsolvable crash I accounted to the limit expander but, to be honest, I don't really know. The limit expander is kind of like the dark age of technology and DoA wasn't even sure how it worked at all when I came to him with that issue so many years ago. I can't guarantee you it'd be stable, or if it was even the reason why AO was crashing.

Remembering, you're not just dealing with your own code in this stuff, but the horrific trainwreck that is Blizzard's code as well. Something as hackish as the limit expander no doubt can upset the equilibrium of lard that is intern soup.

/e

As for the contest I was considering joining but I think I'll save myself the embarrassment.