SC2Mapster

This new "This field may be upgraded" thing confuses me, because my unit's weapon has another value ingame than what it has in the editor. However, the weapons fire rate does not seem to be affected by this, but it's still annoying. Does anyone know why these fields have been upgraded?

P.S. I changed my dependencies from "Swarm" to "Void" when the new expansion came out. Does that have something to do with it?

Could it be that period is how long it takes between shots to be fired and weapon speed is how often per second it fires?

Quote:

Does anyone know why these fields have been upgraded?

You seem to be misunderstanding what they mean. They mean the field can be upgraded. Only fields that can be upgraded can be modified by upgrades and catalog natives. Not all fields can be modified by upgrades and catalog natives, hence why they inform you which ones can.

Quote:

P.S. I changed my dependencies from "Swarm" to "Void" when the new expansion came out. Does that have something to do with it?

Any data based on other data, via inheritance or modification, might have changed. This would explain why your weapon is suddenly different. Go back to it and make sure it is set correctly.

Quote:

Could it be that period is how long it takes between shots to be fired and weapon speed is how often per second it fires?

That is not the default behaviour, neither do the values he show make sense if that was the case.

@OutsiderXE: Go

No, that would be 0.56 shots per second if you did the math. And it's not only on Period for weapons, but also in the Speed for units and stuff. I just generally see the ^This field may be upgraded on so many different values and wondered why that was.

@ImperialGood: Go

This is what my dependencies look like.

That difference is probably the result of real time being used in game now, it changes all the speed and time values, since different game speeds result in different real time durations, build times, and so on.

@Alevice: Gothe value itself isn't altered, but the displayed value in game is. Try different game speeds and see what values you get in game.

@SoulFilcher: Go

That has to be something new Blizzard has done, because that never happened in my previous maps. :P

Edit: You were right. After testing with Normal game speed the value changed to those I typed in the editor.

The value being displayed is being changed to reflect real-time, As Soul said. 2.25 = 3.15. The difference is a multiple of 1.4. That seems to get accurate enough though that isn't always going to be right. 2.25 * 1.4 = 3.15. Similarly 0.86, the Marine's attack speed, is 0.86 / 1.4 = 0.61 (Which is what it displays in game.)

This modifier remains the same no matter what gamespeed you're on. So it will always be 0.86 / 1.4 = 0.61, even if you're on Slow game speed.

This change only happens when you add the Void.SC2Mod dependency. So it might have to do with a file in there, or it could be hard-coded but I don't know that for sure. I'm not sure what file it would be though. Perhaps someone could ask on the Modding / Mapping section on the SC2 Forums to see if a Blizz Rep will reply with an explanation on why the displayed speed values only change on Void.SC2Mod.

The actual number of ticks between attacks should be the same even with this working. It is only normalizing the time displayed into real time units as opposed to game time units.

Game speed alters ticks per second. Slow runs less ticks per second than normal. Fast runs more ticks per second than normal. I think normal is defined at 16 ticks per second.

Quote from TheLazzoro: Go

That has to be something new Blizzard has done, because that never happened in my previous maps. :P

It was added during LotV beta because esport viewers found it weird that displayed values weren't "accurate". So yeah, map makers didn't stop to read that ;-)