Diablo style gameplay

[Phalanx]

I was thinking that the heros are on a constant stop so he will not move or attack back. Both right or left clicks are the attack command. Once the attack command is give he will ether move there or attack target ONCE. After that the command buttons are no longer required so there is space for more spells.

All units and heros are blind so there is a chance to miss. Agility will lower the miss chance and will not increase attack speed or movement speed.

All heros primary attack is melee (unless the hero is using a bow) and the primary attribute is strength.

Maybe allow choosing stats?

 

[syltman]

Or maybe something like this game? http://www.hiveworkshop.com/forums/resource.php?t=93569&prev=search=Unholy%20invasion&d=list&r=20

 

[Phalanx]

Or maybe something like this game? http://www.hiveworkshop.com/forums/resource.php?t=93569&prev=search=Unholy%20invasion&d=list&r=20

Not really. That game is a little to hard to control and there is no primary attack.

 

[CloudWolf]

It's a nice idea, however, I want Warcraft 3 players to be able to easily understand the map Theres nothing I hate more than starting a new map, and having to learn a brand new system :S

I really like the idea of agility acting as a hit/miss percentage though In the current build, agility only gives an armour bonus. We removed the attack speed increase to stop players from becoming too imba, so it would make a rather neat change

 

[dansaDisco]

I really like the idea of agility acting as a hit/miss percentage though In the current build, agility only gives an armour bonus. We removed the attack speed increase to stop players from becoming too imba, so it would make a rather neat change

How about a trigger that's something like this:

Trigger

• Miss chance
• Untitled Trigger 001
  • Events
    • Unit - A unit Is attacked
  • Conditions
    • ((Attacking unit) is A Hero) Equal to True
  • Actions
    • Set PlayerNumber = (Player number of (Owner of (Attacking unit)))
    • Set Target[PlayerNumber] = (Attacked unit)
    • Set Attacker[PlayerNumber] = (Attacking unit)
    • Set Agility = (Agility of Attacker[PlayerNumber] (Include bonuses))
    • Set MissPercent = ((Random real number between 0.00 and 100.00) + (Real(Agility)))
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • MissPercent Less than 50.00
      • Then - Actions
        • Unit - Order Attacker[PlayerNumber] to Stop
        • Countdown Timer - Start Timer as a Repeating timer that will expire in 0.01 seconds
      • Else - Actions

Trigger

• Miss loop
  • Events
    • Time - Timer expires
  • Conditions
  • Actions
    • Set DummyPoint = (Position of Attacker[PlayerNumber])
    • Unit - Create 1 Misscasting Dummy for Player 12 (Brown) at DummyPoint facing Default building facing degrees
    • Unit - Order (Last created unit) to Undead Banshee - Curse Attacker[PlayerNumber]
    • Unit - Add a 2.00 second Generic expiration timer to (Last created unit)
    • Unit - Order Attacker[PlayerNumber] to Attack Target[PlayerNumber]
    • Custom script: call RemoveLocation(udg_DummyPoint)
    • Countdown Timer - Pause Timer

(I've tested it and it works fine, should be MUI aswell ^^)
the curse is a spell that gives unit 100% chance to miss over 0.5 sec

 

[Phalanx]

How about when a hero stops it goes to hold position instead. This will stop the hero from running off to an enemy.

 

[Kwah]

Trackables. Use 'em.

 

[CloudMax]

Trackables. Use 'em.

This:

It's a nice idea, however, I want Warcraft 3 players to be able to easily understand the map Theres nothing I hate more than starting a new map, and having to learn a brand new system :S

Also, if you cant handle trackables and use them wrong, it end up with a whole lot of shit and i think you know that And i dont think anyone of us knows how to handle trackables, but i think RedMarine would like to learn that though xP

 

[redmarine]

This:



Also, if you cant handle trackables and use them wrong, it end up with a whole lot of shit and i think you know that And i dont think anyone of us knows how to handle trackables, but i think RedMarine would like to learn that though xP

I sure do! But for now lets stick with Wc3's default command system.

 

[Phalanx]

Will there be weapons that have attribute requirements?

 

[Thyrael]

You can catch left and right clicks on a target unit. But only if you default selection is your hero. First is simple player selects unit, second if unit gets order rightclick. Selectionevent always works. For right click you have to select your hero and the rightclick the targetunit.

 

[redmarine]

Will there be weapons that have attribute requirements?

Probably not as for now because we're just trying to make the map as much fun as can be first. All the boring stuff can wait.

 

[redmarine]

You can catch left and right clicks on a target unit. But only if you default selection is your hero. First is simple player selects unit, second if unit gets order rightclick. Selectionevent always works. For right click you have to select your hero and the rightclick the targetunit.

There is a delay in selection events so no.

Thanks for your input though.

 

[Thyrael]

When using JASS there is no delay, I use it for my actionbar. The buttons are units, leftclick => selection, rightclick => order rightclick and automatically reselection of the previous target.

function InterfaceClickL_Timer takes nothing returns nothing
    if BUTTON.ClickPeriodicSelect(GamePlayer, true) then
        if (GetLocalPlayer() == GamePlayer) then
            call ClearSelection()
            call SelectUnit(GameUnit, true)
        endif
    endif
endfunction

function InterfaceClickR takes nothing returns nothing
    if BUTTON.Click(GetOrderTargetUnit(), false) then
        call PauseUnit(GetTriggerUnit(), true)
        call IssueImmediateOrder(GetTriggerUnit(), "stop")
        call PauseUnit(GetTriggerUnit(), false)
    endif
endfunction

You can adjust the delay by setting the interval of the triggering timer.

 

[redmarine]

When using JASS there is no delay, I use it for my actionbar. The buttons are units, leftclick => selection, rightclick => order rightclick and automatically reselection of the previous target.

function InterfaceClickL_Timer takes nothing returns nothing
    if BUTTON.ClickPeriodicSelect(GamePlayer, true) then
        if (GetLocalPlayer() == GamePlayer) then
            call ClearSelection()
            call SelectUnit(GameUnit, true)
        endif
    endif
endfunction

function InterfaceClickR takes nothing returns nothing
    if BUTTON.Click(GetOrderTargetUnit(), false) then
        call PauseUnit(GetTriggerUnit(), true)
        call IssueImmediateOrder(GetTriggerUnit(), "stop")
        call PauseUnit(GetTriggerUnit(), false)
    endif
endfunction

You can adjust the delay by setting the interval of the triggering timer.

Does that also imply for multiplayer? Even if this is plausible I doubt we'll actually use it anyway. Restricting players' ability to select other heroes and check upon their status is silly which WarCraft III players expect to be plausible.

 

[dansaDisco]

Restricting players' ability to select other heroes and check upon their status is silly

It may be silly, but that's the way it is in diablo 2

Not sure where my point on this is though.

 

[redmarine]

It may be silly, but that's the way it is in diablo 2

Not sure where my point on this is though.

This is WarCraft III after all. The UI is simply not designed for such drastic changes. This will also dramatically hamper most players from supporting each other. Without the proper informations e.g. level, health, mana, stats, etc. players are a bit lost.

 

[Thyrael]

This is WarCraft III after all. The UI is simply not designed for such drastic changes. This will also dramatically hamper most players from supporting each other. Without the proper informations e.g. level, health, mana, stats, etc. players are a bit lost.

simple add conditions to the trigger to filter out WHAT typ of unit the player selects/rightclicks. If it is an allied hero, you won't attack him.

 

[CloudMax]

simple add conditions to the trigger to filter out WHAT typ of unit the player selects/rightclicks. If it is an allied hero, you won't attack him.

I dont think that he means it that way.
If you have diablo 2 style, you instantly attack a unit when clicking on it without getting any information about it or something, all you get is a health bar over it. And you cant select it becouse you would just attack it.
Its not the ally that is our problem, it is that we still want to keep some Warcraft elements and not make it to much diablo. Otherwise it would confuse newbies.

 

[Phalanx]

Is there a way that ranged attacks go in a line instead of guided?

 

[redmarine]

Is there a way that ranged attacks go in a line instead of guided?

Yeah, if you code it. I doubt we'll do that though. The standard WarCraft III system works just fine.