Yeah, I'm still slowly working on it. It's going to be released as 3.40 because of the number of new changes and features.
I've only got 3 major things left to do:
- Sort out the new Nuke mechanics. It makes all enemy units on the field JYD, but for some reason in my map most flying units only JYD for 3-4 seconds and then they try to fly back to their original spawn positions. This didn't happen in another test map I did so I think it's something peculiar to my map. Need to investigate further, and this could end up being tricky.
- Change the CPU players to be allied with all the human players, so they don't destroy their bases. This means I have to review all uses of 'Allies' and 'Enemies' by the CPU players, and there are quite a lot. There are also a few systems I'll be able to improve (particularly the new nuke mechanic) because previously "enemies" meant opposite human players + enemy CPU, but now it will just mean enemy CPU so I'll be able to handle some effects much better.
- Finish up the early spawn mechanism. This is probably 80% complete and need to do extra testing.
I've also been looking into EUDs for detecting when players have researched certain upgrades. At the moment the upgrade sharing between team members is really very wasteful - if it detects you have spawned a unit that can have an upgrade, such as a dragoon, then every single time your units spawn it will create 3 of them in a holding area and give them to your CPU player and back (incase dark archon stole the upgrade from enemy team) and to your allies. For efficiency, this only needs to be done one, but because there's currently no way in the triggers to detect when the upgrade has been researched and therefore only do it once, it is done every time.
With EUD upgrade detection, I'll be able to change it so the upgrade sharing is done on an as-needed basis and not continually, which will be better. If you look in the map making theories section you'll see that I've been working on the EUDs for mac - if I go ahead with it then I don't want to lock out any of the player base.
Another thing that upgrade EUDs will let me do is make the spell system much more flexible. This is most notable with the Dark Archon. At the moment the DA will use maelstrom continually until you research mind control, and after that it will only occasionally use maelstrom. This is to do with the essential switch-based system the game uses for casting spells - if it has enough energy to cast MC it will do so, and only if MC fails will it attempt to cast maelstrom. At the moment all DA's are initially spawned with certain amounts of energy, but with upgrade detection I will be able to spawn them with different amounts of energy depending on what upgrades have been researched. I'll make maelstrom researchable again (as the current state is quite strong vs zerg), so when the DA has no spells it will spawn with 200 energy and therefore be able to use feedback once. When it has only maelstrom researched it'll spawn with 25 energy, enough for 1 maelstrom. When it has maelstrom + energy upgrade it will spawn with 50 energy, enough for 2 maelstroms. When it has maelstrom + MC researched, it will spawn with 95 energy, enough for 1 MC and 1 maelstrom. When it has MC + maelstrom + energy, it will spawn with 177, enough for 2 MCs and 1.5 maelstroms. With MC only it'll have 70 energy, enough for 1 MC, and with MC + energy it'll have 125 energy, just short of enough for 2 MCs. Numbers aren't final but this gives you an idea of the purpose of this. Without EUDs, such wildly different spawning energy values aren't practical. This concept can be applied to other casters that use multiple spells, such as the science vessal which hardly ever seems to use irradiate, and the zerg queen will be able to use ensnare and broodling more often.
These EUD changes of course will require SC 1.16.1, and so if Blizzard releases an update it'd break the map. So I will release 3.40 first which has all the major changes in it, and then once I've done the EUD stuff (probably 1-2 weeks) I'll release 3.41 then. That way if a new patch does come out and I never make a new version, people can go back to using 3.40.
None.