Search results

I get a message in game that says: "Error message missing" when a hero dies. I have editted the hero death text in Game Interface to a space. Normally this is no big deal in my other small tests maps. But in my main map I get this message and I can't fix it. I use the NewGen World Editor but...

What global constant or trigger action should I use to make sure that heroes can't level multiple levels in 1 go? So for example. Hero is level 1 and picks up a book that gives 500exp, the hero levels to level 3. This should be level 2,9.

My map gets insta desyncs since 1.25 My map gets insta desyncs since 1.25. Is there any word out there yet how to deal with this? It's just the same deal we had when 1.24 came out. It destroyed alot of maps too.

Is it me or doesn't the "Data - Damage Dealt (%)" do anything? Because when a ranged attack is reflected to the enemy unit. It always does full damage.

I got some questions about certain choises you can make in world editor which could have a relationship with desyncs. -Wait and Wait (game-time) Wait (game-time) is a polled wait so players wait for eachother until everyone is done with waiting. When is using wait in a multiplayer game...

I got a building with hero select ability. This building has an ability that players can click on. Is it possible to find out who clicks on the ability?

1: Is it possible to bind an art model to this ability? A buff such as brilliance aura. 2: Is there an auto-cast spell that can touch units with spell immunity? Non-auto-cast spells are ensnare & finger of pain||death. Thanks!

Appearently my map (Terrania) isn't mac compatible. Same for TBR, COT RPG and Castle Fight. At least that is what I got reported. The game crashes for mac users when they select something like a hero. There are no selection events, conditions or actions in my map so I have no idea what's...

Does this leak? Set Point1 = (Center of region1 <gen>) *goes in loop* Item - Move (Picked item) to Point1 *an then like 20 times this move action* Custom script: call RemoveLocation (udg_Point1) If this doesn't leak then I don't really see the point in removing the location. Because...