Will adding damage dealt per wave create lag?

[Reciever80]

On a mediocre computer, one that can run halo CE, unreal, and other, smaller games at medium settings, Will this make the computer lag?

I'm creating a tower defense, and was thinking about creating post-wave tallies. For instance, who had the most kills, who dealt the most damage. I already have the kill count set up properly, however if there's multiple towers (anywhere between 8 and 50?) towers all dealing damage at a rate considered "Very High" by WC3, would all those calculations per second add up on the computer's processing ability? Or are all of these calculations minute in the scheme of things?

Also, will this trigger work?

• WaveDamageCounts3
  • Events
    • Unit - A unit Is attacked
  • Conditions
  • Actions
    • Set DamageTemp = (Damage taken)
    • Set PlayerWaveDamage[(Player number of (Owner of (Attacking unit)))] = (PlayerWaveDamage[(Player number of (Owner of (Attacking unit)))] + 1)

Thanks,

~Brent

 

[Spartipilo]

Hehehe.... you can't imagine how many numbers common computers can handle don't worry. Just pervent creating tons of creeps at the same time, and prevent toons of heavy special effects.

You can have 1000 towers attacking every 0.1 seg a unit and display floating text for each one of them with the damage dealt, and save the number of hits and total damage dealt by each tower in a hashtable, and it won't lag even if you run WC on a CASIO Watch clock.

Again, what most lags is the Unit creation and special effect (includes Towers missile effect). You can keep them simple with arrows or light bolts, forget about shooting Shockwaves and else.

 

[Magtheridon96]

That won't work.
Also, it's very exploitable.

You shouldn't use the event "A unit is attacked", you should implement a Damage Detection system like Bribe's DamageEngine for this.

Also, this won't cause lag, like at all.

 

[Arhowk]

Warcraft 3 runs thousands and thousands of threads a second, that would be no problem

also note that the unit is attacked function only occurs when the unit actually goes to attack, not when the unit is damaged. You will want to implement a damage engine, like mag described

btw spartipilo, that wont lag but that will glitch because you can only have 99 floating text at once. (or was that text tags...)

 

[Magtheridon96]

Warcraft 3 runs thousands and thousands of threads a second, that would be no problem

Actually, just one ._.

 

[Arhowk]

Is thread a bad word for it? lol

 

[Magtheridon96]

Yeah
I think processes is closer to the correct term.

 

[Meticulous]

Very few things will create lag unless they leak.

 

[Magtheridon96]

I found it, triggers is the perfect term for this.
When you do something like reference a variable with no value (not even null, 0, "", or false or w/e), you would create a run-time error and crash the trigger, not the entire game :>

 

[gorillabull]

why dont you just test it first and see what happens' this will not lag if you use arrow projectiles and set the decay time for bones to and flesh to 0 also depending on what other programs you are running it is hard to make a computer lag if there are no graphics to process.