Search results

@Sygvur: AFAIK GetUnitGoldCost only works for the standard/default units ... however i dont recall if it crashed wc3 when used for custom-units, or if it just returned the value of the base-unit.

Grundy's way might work if you order the last order again... (maybe using some library like LastOrder) btw Grundy, did you try issue that autocast-trigger order with an immediate order or not ? If not you could try if an immediate order interrupts the current order aswell or not .. And i still...

does cjass directly compile to jass or to vjass ? Or should i ask... can you even use cjass without JassHelper (vJass) ?

you are a mapbaned noob .. rofl

TrollBrain is right, switch to Hashtables, they are a lot faster ... and safer.

u could use UnitAlive from common.ai aswell ;)

you could try this: http://www.wc3c.net/showpost.php?p=1052338&postcount=3

you CAN check if a unit was stunned by checking if the target unit has the stunbuff...

you have to ask this @ WC3C

check this http://www.wc3c.net/showthread.php?t=106558

things which doesnt work with 1.23b yet: war3err (not sure about this one) japi RtC

damage detection is really tricky, and can cause many errors if not coded >very< well. So i would advides you to use a established system for your map, like: Light Leakless Damage Detect (LLDD), ADamage or IDDS If you just started your map, i would use IDDS, if not i would recommend LLDD...

sad thing is, thats a LOT of work to recycle units ...except for dummies, which should always be recycled.

strange, when i tested this (abuse) yesterday it didnt work for me... EDIT: i get syntax error now, "cant convert handle h to integer" ... well i use Zoxc's Parser, which enforces strict type safety ...to laze to switch to pjass for testing this again right now.

Nice ;) Sorry cant give you Rep (spread) xD

benchmark are coming soon, as Mindworks finishes the new StopWatch Natives (i am hoping he will ..some day)

How to find auto complete with ressource hacker: "RC Data" > "TFORMTESH_MAIN" > "SciAutoComplete" > "AStrings.Strings" There you go

any numbers prefixed with "0x" are Hexadecimal numbers ... not binary numbers. With the new natives this shouldnt be needed anymore anyway, since hashtables arent limited as arrays...

No, there was a workaround using return bugs ...but that doesnt work anymore for multiplayer... and wont work for whole warcraft with patch 1.24

StartThread is NOT an normal Native ..its an AI-Native...