Rename the map from "Pevolution" to "Revolution" (alpha2)

subj

Anyone named the bug in the new chaos race yet?

Elements Tier 1 tower (Proton) is not upgradeable. There's an ability "Deploy Proton" (costs 40 gold), and it does absolutely nothing.

When you have a LOT of units (almost filling your lane), forward ranks will meet the creeps and will engage them, while back ranks will not do anything, because they are outside of aggro range. This is not a problem when fighting against powerful waves, which mow down your first ranks, and eventually get to the second ones, but in some rounds, when your units have the upper hand, the back ranks will never see the action, and thus they won't move, and won't go into the teleport, reducing the number of units protecting the king lane.

I can provide a replay where this bug (feature?) becomes apparent.

OK, some pretty minor stuff:

Here's a correct map loading screen text for you:
Hi! This is a new LegionX3 Revolution map, it is based upon Lisk's 1.60b and eGze's 2.7. It is an alpha version. Why? In short, not all features are implemented, but the map is in VERY good shape, better than most of the "finished" BNet maps.

What's new:
- probably a LOT LESS lag on late levels
- 2 NEW RACES
- a lot of X3-only balance improvements
- double- and triple-builder modes (-db and -tb), try them!
- mode -gg is back. Mode -cb is not, but will be sometime later

An alpha version LegionTD Pro (X1) is also released



OK, now, other things:
1) Can you add some message that would be printed when the map starts? A message that would tell people to not to freak out, that a big lag at the beginning is normal?
2) Some maps require you to press any key after they've been loaded to start the game. LTD just writes "LegionTD unofficial expansion" in the progress bar when it's finished. It's unclear whether or not one should press anything. According to my tests (creating a LAN game vs a computer opponent) you DO need to press something to start.

von_Oberstain wrote:hmmm, i know of this but have not real solution yet. if aggro range is increased, middle builds start to become useless (creeps tend to act weird even now). i did creep aggro increase in work-in-progress version, but i guess it's not enough.

i think there is a way to 'alarm' units via triggers, will have to investigate its possibilities - some kind of "chain reaction", like every unit engaged alarms neighboring units or something like that.

anyway, i'll see into it, in the meanwhile (my own solution which i use in Pro), is NOT to build at foremost sides, until battlefield gets overcrowded (and even then, preffer king's side to opposing, there is pathing blocker near middle which causes creeps to turn to king)

[EDIT] yes, i think it is possible to solve this WITHOUT breaking existing engagement rules (on a glance, at least)... now i really have to sleep...

If you still use old pathing (eg, fighter start with 0 movement speed, then change to default speed when creep within range)

then you can solve these problem by:
1, set up 8 boolean variable: fight_start[1-8] with default value = false,
2, set up 8 unit group variable: fighter_group[1-8], it will store fighter for every player
3, find out which code change movement speed from 0 to default, and add these new code :
-- if fight_start[player's id] is false, set fight_start[id] = true, and change all fighter_group[id]'s movement speed to default speed.

so after these change, if any ONE of RED's fighter start attack, all RED's fighters will move forward to attack.