TKF Wrote:Also the shield system does also require a lot too and produce lagg equilant to 20 projectile being moved constantly through the entire game. The shield system itself reduce performance on my computer with 15-20%. And that is without missile detection.

1. Max HP of barriers;
   
2. Regeneration rate;
   
3. Refresh timer(when it is destroyed);
   
4. Take damage from <source> (I dunno if this is handled in any special way but I think it shouldn't - any explosion from a rocket must deal damage to all barrier instances in a defined radius by a built-in mechanisms of a game and cause no additional lag in result);
   
5. Remove Shield trigger (condition of this trigger I must study a bit to understand it more precisely);

1. This is determined by a number of Boosters(forget exact name) and Graded Boosters of each player in team. I also dunno exact formula for calculating this but this formula is not important. We can store this formula's result in a separate variable, which will be updated only when number of boosters is changed. And Max barrier HP will be calculated from this variable(or even make a variable that holds final number of Barrier Max HP and take that value from var directly without calculations). This will make all triggers that use barrier Max HP vale not to calculate each time all the formula. Calculation will happen only when number of boosters is changed in team what happens not that often.
   
2. This is the same as described above but with one small correction. The total factor that influences regeneration rate and max hp is the same and it depends on a number of boosters. So we can store two additional variables with numbers of Boosters and Graded Boosters(in case if we cannot use one var for storing "upgrade level" that could be used for both hp and regen - in case if graded booster gives different bonuses to hp and regen increase). And then calculate or store final vars that will represent final amount of hp and final regen rate(or regen multiplier).
   The idea here is that we wont make redundant calculations of the same formula for two different values.
   
3. This trigger is pinned to an event when hp of one of the barrier instances goes 0 or below. I don't see a problem here.
   
4. Also no triggers required.
   
5. See p.3.

1. Event handling works as delegate calls, not as constant State checks(this I must research a bit to make sure). If we need to make constant checks - this really sucks and I don't generally know how could be this refactored.
   
2. Shield does not have self-linearizing feature. By this feature I mean self-equalization, when if one piece of barrier is damaged and other pieces are full hp, their hp will quickly flows to a damaged one so all the pieces in a shield will have equivalent hp amount. This process of equalization will take some time of course and it will be particularly constant, so it may cause significant lagging.

TKF Wrote:I Asked Exilus5 permissiom at azeroth for the open source of the map. He did only have 1 condition: credits as the original mapper.

Maybe he designed the triggers when he wasn't so skilled in the editor. Who knows, but the current shield system is more advanced than it needs to be. But I'm to noob to simplify triggers. Btw he have made soldiers map too, which is very awesome!


0.51
I added zoom function, and a defense against motherships; Gravity Vortex which works kinda like a black hole.

TKF Wrote:Made a 1.24b compatible version.