For the record, the first question was asked in post #3.
If you run DotA hotkey changer program and open up the customkeys.txt file, every entry is all lowercase. However, if you convert the data into numbers(I'm not sure what these numbers are), you get to see this.
Is this going to be based on those Icons from earlier?
Critical Strike abilities. Combo Points increase the chance and/or damage.
Corruption Orb. Combo Points increase the armor reduction.
Splash Attack Orb(Fire Orb). Combo Points increase the splash damage radius.*
Toss Enemy Unit...
scope FUPresence initializer FUInit
private integer f = 'A000'
private integer u = 'A001'
private integer fd = 'A003'
private integer ud = 'A002'
If you have any variables with the same names then you get errors. Use private...
In that case, don't forget to use the correct constant.
constant unitevent EVENT_UNIT_HERO_SKILL=ConvertUnitEvent(79)
constant playerunitevent EVENT_PLAYER_HERO_SKILL=ConvertPlayerUnitEvent(42)
constant unitevent EVENT_UNIT_SPELL_EFFECT=ConvertUnitEvent(291)
Would it be acceptable to treat this as a terrain problem? You could include more unbuildable terrain in order to restrict where the town halls can be built at. At any rate, without seeing your terrain/map, it is hard to understand your dilemma completely.
Ok, I see your point. You read the part where I said takes triggerunit. I edited that to say takes t. I could not remember your local variable name. You basically delete your local variable. It isn't needed.
EDIT: Yes, I see what you did with that local unit. That isn't needed. I don't...
Sorry, I was confused. I edited my post while you were posting. I mentioned you should use takes. That will pass the unit. That's all you didn't do yet. But the other poster maybe tried to mention your Ability ID plan is odd. I don't think it would bug. So you can maybe ignore it for now.
He doesn't appear to be using a globals block. You are correct about GetTriggerUnit() needs to be somewhere that it can work at. I don't remember using GetTriggerUnit() wrongly in a way that resulted in anything but a failure of code to fire in-game.
Ok it took me a while but I think I get...
A learner might look for something that deals with "time of day". He might look at one system(one says time, one says day), find something completely different from what he wanted, and feel sad he did not find what he was looking for. Solution? You ask him to keep looking. This learner has...