DvDmanDT wrote:aubergine: I see. I suppose I'll just hard-code or something for now then since it seems dumb to create maps that won't be playable by the majority of players for another year or so. I mostly agree with what you have on that wiki page, but I'm not sure there's enough info.. On the other hand, I like the simplicity. What I mean is that some AA locations may only make sense for a specific player.
I've not actually done any map making myself, so it would be very useful if anyone making maps could help provide better info (even if info is posted here or sent to me in PM I can copy to wiki, or just edit wiki directly). I currently have to do "educated guesswork" to document stuff relating to map making, so there will be some missing information but I figured that is better than no information
From what I understand, the labels/gateways stuff can still be put in to maps and it can be coded in to AI scripts (so long as they degrade gracefully when used on earlier versions of the JS API) and the maps/AIs will still work in current releases. At a later date when 3.2 is released, the extra JS API functions become available and scripts can then start taking advantage of the labels and so on.
What I was thinking is that it's probably worth thinking up some standard label naming conventions sooner rather than later, so that more map makers can start putting labels in to their new maps as they make them, rather than having to go back and retrofit at a later date.
"Dedicated to discovering Warzone artefacts, and sharing them freely for the benefit of the community."
-- https://warzone.atlassian.net/wiki/display/GO