Recent content by hunterrravyn

It will work, but not as intended.

This is probably a basic version of what your after includes --Show --Update and a basic varible setups

Looking at your stuff, You may look at splashing blue, it does have some nice creature defence and counters (i.e. Counters, Bounces, Cheap Defence), the blue would also add a more contoling aspect to the deck. Have a look at. This Card can make for some intresting and quick games with a burn...

The rectangular things that you make in the editor are called Rects point < rect < cells < regions < = Made Up Of actual regions are point that can make a shape of any kind, oh and as far as I know there is o gui support for them.

Umm the Crossbow shot had an error on upload. The rifle (should have been more specific, forgot to mention lever action) Lever Action Rifle Kinda like that The Crossbow Crossbow Well it doesnt give you the actual bolt placement, but basically its a light sound of wood on wood.

Pistol Shot.(9mm?) -Shoot -Reload(Cartidge) Revolver(louder and sharper than pistol shot) -Shoot -Reload(6 Shots) Assult Rifle. -Shoot Shotgun(Pump Action). -Shoot + Pump -Reload Combat Shotgun -Shoot Crossbow. -Shoot + Reload Silenced Pistol. -Shoot Have fun :)

That's no problem, if your know programing and intrested in a new one for warcraft III, then Jass is it. There is plenty of tutorials around the web on the the helper and the hive.

Advanced unit sharing in Scenario -> Forces (might show it, if it does they probably could use it) But it cant be changed in game.

No you didnt miss anything, i just was doing it "freehand" unless your talking about Loop for integer But if you storeing them in an array you can use set unit[For Loop Integer A] = Value

Depending on your situations Trigger Actions Loop for whatever Loop Actions: set unit[For Loop Whatever] = Bla

I dont see any problems with it but what if the hero has two swords? it would get rid of both. i.e. In the Or conditions

Trigger Events Unit - A unit enters region Conditions Actions Custom Script: local location uloc = GetUnitLoc(GetTriggerUnit()) Custom Script: local real uface = GetUnitFacing(GetTriggerUnit()) Custom Script: call SetUnitPositionLoc( null, PolarProjectionBJ(uloc, 200.00, ( uface +...

Actions Custom Script: set udg_HireUnit[1] = null This doesn't really matter much depending on how often a unit is hired. If left once, it will cause a single leak, really not much to worry about. Of course this is doe after you declare everything with it.

I believe that there is a Terrain Deformatation Command in GUI, cant open WE atm so i dont know exactly were it is.

uhhh, setting to; call TriggerSleepAction(0.5) and exitwhen(x == (y*2)) will make the tree killing more often but lasts for the same time