Delceri thoughts on warrior


My Oculus cable is broken, and with spare time + class balancing coming up a few times recently I’ve decided to re-visit a class that I’ve always wanted to like. Here is my personal idea of what an ideal warrior update might look like, give or take some. You probably will have to “open image in a new tab”, etc because the forums super-shrunk the image.

I have a whole thing for spear warrior(which actually is where thrust makes more sense, do sword-wielders turn their wrist during a thrust? Or do they just reel-back and stab?). Turning the blade for bleed still makes sense. That said, I’ve limited the amount of ideas presented at once lol. My real love would be an insane, axe wielding warrior who can swap to a bow like a ranger.


Old video for reference regarding the hit-detect system ( I am aware some changes/fixes have been made since - so this is not 100% the same currently ). (detects upswing as right swing, hard locking you out of your combo)


Lot of interesting stuff, imo. My only issue is that the finite tracking like the twists may not be reliable.


I can understand some skepticism, but I am pretty certain that if you position your arm correctly from the start of the stab, to the end of the twist, that is plenty of digits to work with to collect that the player rotated the wrist, imo.

I’ll preface below with that, redesigning the hit-detection system (aside to include wrist turning, etc) is probably not necessary to implement a lot of new features. It would just be an improvement.

That said, part of this change suggests designing a more intelligent warrior system capable of “guessing” (within a narrow window) what the player is doing, rather than locking them out of combos for a bad-swing register. An ideal system won’t pull the trigger immediately, it will wait an unnoticeable amount of time (to human perception) until it’s determined the valid/intended swing. So as to not confuse for example the thrust/bleed combo, a large stabbing motion will be looked for and then it will start looking for large wrist turning, triggering the bleed attack. Whereas if the player thrusts/turns the wrist, and then hesitates(but the wrist does not rotate inward) or begins swinging again, then it will know the move was a thrust and a bleed is not going to follow up. As just one example. Another option is to look-back at the previous swing for possible results, in this instance. If a thrust is recorded, then your next swing-state should look back at it to see how much wrist-motion was present during that thrust. If the number is low, then it probably was not a thrust+turn. Thus, this current swing-state would be expecting a higher amount of wrist-motion to invoke bleed. Otherwise, if the last swing only registered as a black dot/thrust, but had 50% of the wrist motion required, and then this swing-state also contained ~50% of the required wrist motion, which began near the end of the last state, then we are most definitely performing a blackdot/wrist rotate and this swing-state is actually no different from the last, it was just a mis-fire. Something along the lines of that… This isn’t really my 100% right here lol, if I sat down and fleshed it out I could but they can figure out those details themselves.

Similar-ish to the runemage system, where a calculation is done at the end of a drawing, except this would be on the fly within small time-windows, triggered by swings “starting”(as they are done now). Once the system is like 90% sure a swing is an upswing, and not a right swing for example, it will exit the window and begin looking for the next swing. Otherwise, if the window closes, it will take the highest valid swing. Again, these time windows are so tiny that they would not affect your swings negatively.

They could even have an invisible “ghost blade” follow your strikes at some delayed elliptical speed(so that it never strays too far from your actual sword), and take the difference of motion(quaternions, for example) between your “two swords” to try and guess what you were really doing. Or store your motion information at some critical point during a swing. I have no idea what their system actually does.

Wikipedia is a garbage fire of overly complicated information, but quaternions could be useful here if they aren’t already using them.

1 Like

This is kind of a random last addition, but, as something else that could be used in combos: movement. That is, in game movement (small steps via joystick/or IRL walking) and body rotation(head/goggles, not just the sword), to include swing-arc-distance (so you really have to turn your body, not just your head) to really emphasize certain swings. Example: Swing left and rotate your body(head/goggles) left, arcing your sword wide. This would be cool for like giant maces or just “huge” feeling attacks in general. Like giant cleaves. Just keep small children and objects away from you lol.

This is my last, super duper random derailing thought. But man… ranger/warrior, pally/shaman, would just be absolutely sick classes. Musky/scoundrel(with additional rework…) too. Every class beside mages feels like 50% of something really good to me :(. This is probably not helpful because I think there’s a low chance of negotiation to merge entire classes & synergizing their best features. I do think it’s possible to still expand on each class as-is, it just feels more challenging to do that for some classes (like musketeer).