Would Set Name of unit cause a desync?

[georgo]

I'm curious. Two players playing same map with different languages of warcraft. Would this function cause a desync?

• Unit - Set Name of (Triggering unit) to ((Name of (Triggering unit)) + (|nLevel + ((String((Level of (Triggering unit)))) + |r)))

Since it refers to the unit directly, and both player clients would return different value of (Name of (Triggering unit)). Sadly i can't test it myself.

 

[Pyrogasm]

Visual differences in strings like this don't desync afaik, like locally changing floating text for different players.

 

[georgo]

If so, how unit will be named with this function? For example, if i'm gonna rename peon with this. And there will be 2 players, one with eng client, one with russian. Will it be "Peon" or "Раб" in russian? Or will peon have own name for each player?

 

[Pyrogasm]

SetUnitName() is a new native I haven't played with. My best guess is it would be whatever the name of peons is in-game for Russian WC3.

Apparently you can also set heroes' proper names in-game too: Patch 1.29 new natives: a testing place

 

[PurgeandFire]

If so, how unit will be named with this function? For example, if i'm gonna rename peon with this. And there will be 2 players, one with eng client, one with russian. Will it be "Peon" or "Раб" in russian? Or will peon have own name for each player?

It won't translate it unless you tell it to. You can get the translated version of a string using the native GetLocalizedString.

For example:

call SetUnitName(someUnit, "Peon")

Would rename someUnit's name to "Peon", even on a Russian client. However, this:

call SetUnitName(someUnit, GetLocalizedString("Peon"))

Will set it to the localized version of "Peon". So for a Russian client, it would show "Раб". On an English client, it would show "Peon".

 

[georgo]

It won't translate it unless you tell it to. You can get the translated version of a string using the native GetLocalizedString.

For example:

call SetUnitName(someUnit, "Peon")

Would rename someUnit's name to "Peon", even on a Russian client. However, this:

call SetUnitName(someUnit, GetLocalizedString("Peon"))

Will set it to the localized version of "Peon". So for a Russian client, it would show "Раб". On an English client, it would show "Peon".

Interesting information, i didn't know that you can use translated/original strings in code. Thanks.

 

[PurgeandFire]

oops, I forgot to include a GUI example. Here is what it would look like if you wanted to take advantage of it in GUI, just make a variable "TempString", use this custom script, and it will overwrite TempString with the localized version:

• Set TempString = (Name of (Triggering unit))
• Custom script: set udg_TempString = GetLocalizedString(udg_TempString)
• -------- You can use "TempString" below this and it will be the localized (translated) version based on the person's client --------