Feedback talk:User/Raine Valen/Skill suggestions/Warrior/Swordsmanship
From Guild Wars Wiki
< Feedback talk:User | Raine Valen | Skill suggestions | Warrior
Jump to navigationJump to search
Your sever buff is overcompressing stuff.Galrath's function doesn't make sense imo.Rest is fine afaik (although I don't like unblockable skills) Lilondra 13:17, 19 February 2010 (UTC)
- I think Sever needs a shorter Bleeding duration.
- Galrath's function is, ofc, a second Bull's. Swords aren't scary like axes or hammers; they can't just frenzy on you and eat your red bar, they can't knock you down and kill you. Giving a sword war a second copy of the most-threatening war skill ever should make them a bit less laughable.
- I think the only unblockable skill is Seeking, which, iirc, was pretty weak. is for Raine, etc. 16:08, 20 February 2010 (UTC)
- Its more the cast time that is worrying me.Remove cast and it is fine or barely OP (hard to tell with just theory).Also I don't know I liked the idea of daze if DW on galrath (its not mine AFAIK).And AFAIK if someone is moving and you slash with sword that has to be one hell of a (blunt) sword to knock the target down tbh.It seems that if the sword is strong enough you'd cut the guy in 2.Also déjà vu's are twice as scary if they involve fucking computer screens.Lilondra 16:25, 20 February 2010 (UTC)
- Severgash is still using two skillslots to be worse at spiking than axes. :>
- Galrath slash is more of a "trip with sword" deal. Galrath was a dishonorable Bad Guy, so swords get a dishonorable skill to match! Also, swords can Bull's just fine, which makes equally as little sense. is for Raine, etc. 16:30, 20 February 2010 (UTC)
- hey the doesn't make sense part is a detail as long as the function works :p.Also You are forgetting its not just that its also bigger pressure,more spread.Its just OP imo.Anyway You only cover DW with daze for X seconds (the daze should be 5 sec max) so its not like its lolOP Lilondra 08:33, 21 February 2010 (UTC)
- Its more the cast time that is worrying me.Remove cast and it is fine or barely OP (hard to tell with just theory).Also I don't know I liked the idea of daze if DW on galrath (its not mine AFAIK).And AFAIK if someone is moving and you slash with sword that has to be one hell of a (blunt) sword to knock the target down tbh.It seems that if the sword is strong enough you'd cut the guy in 2.Also déjà vu's are twice as scary if they involve fucking computer screens.Lilondra 16:25, 20 February 2010 (UTC)
With Final thrust, would you have the Deep Wound occur before the extra damage, or afterwards? I don't like your HB, because it has the potential to spike and pressure at the same time. King Neoterikos 03:39, 27 June 2010 (UTC)
- After; you'd have to follow up with a fast attack (like prot strike), apply degen beforehand, be under 33% ias, or have a team spike assist in order to take advantage of the deep wound.
- I think HB needs its functionality moved to axe mastery. As I think you might've noticed, I'm moving lots of damage out of swordsmanship; that's what axes are for. Swords are supposed to... cripple stuff, or something. is for Raine, etc. 04:01, 27 June 2010 (UTC)
Quivering blade[edit]
Looks like that even if you don't interrupt yourself, you gain 30+ bonus damage and daze for 5 energy, which is very very powerful. --Boro 15:37, 8 November 2010 (UTC)
- I am against +10...34...40 damage attack skills in the first place; this is partially why. -- Armond Warblade{{Bacon}} 17:13, 8 November 2010 (UTC)
Silverwing Slash[edit]
I don't think any melee has nearby range attacks. It should be adjacent.--Life Infusion «T» 03:55, 15 November 2010 (UTC)
- No other melee attack has nearby range, yes. The question we've got to ask from a design standpoint, though, is: "Does that mean that it shouldn't?"
- Adjacent range and nearby range mean two totally different things. Adjacent range punishes balling; Nearby range hits several people in normal play. I don't want Silverwing Slash to punish bad players; I want it to have the power that Cry has for mass disruption. That is why it's nearby and not adjacent, from a design standpoint. — Raine Valen 1:01, 16 Nov 2010 (UTC)