Melee while casting?

[Greatguardian]

Guess I caught your arguments out of context because you were being irritated at the people you were replying to. That's a legitimate assumption (still, I just really think it's more guesswork than a given). Tossing a like for wrongly calling you out (my bad) and moving along now...

Don't worry about it, no harm done. I really should have been more clear in general, it can just be extremely frustrating to feel like you're talking to a wall over and over.

Edit: To continue with the idea you presented, the biggest issue I'd see is really the situation wherein your melee round overlaps the end of the spell. Even if you simply cast the spell after the round went off (this is assuming that the Devs make sure to code for negative numbers in remaining cast time. Shouldn't be too hard, but important), you'd still have the 2.0338~ second post-action delay after the spell goes off, which would pause your attack rounds - resulting in a low net gain.

This is also assuming that the magic commands are sent in real-time rather than simply "When Time = Start Time + Adjusted Cast time, check for StartPosition==EndPosition and SpellInterrupted=False" or some variation therein. It would be more efficient for them to have the server calculate magic casting time at the beginning of the cast rather than having the client send both start and end packets. This would mean inserting a check for attack delay and delay status into the original "magic start" routine and adjusting the completion of the spell to be "When Time = Start Time + Adjusted Cast time + Attack round time", and would still miss taking into account whether or not the player is actually able to swing at something.

Christ, the more I think about it the less I want to be "that guy" on the Dev team that gets asked to look into something like this, lol.

[Selzak]

There would definitely be conflict sometimes, but I don't see why it would be terribly difficult to deal with. A particularly easy solution would just be to consume that swing and give the cast priority. Like I said, I was more introducing the idea that it may be possible to effectively allow meleeing while casting instead of trying to make it possible to perform two actions at once. How they actually handle the act of "casting", I have no earthly idea. I do have a hunch that this is possible though, for a couple of reasons:

Casting (as in, waiting for a spell to occur) is sent a lot quicker than it seems because the animation tends to lag behind. If you ever get interrupted you'll notice that your casting animation goes on (sometimes for a really long time...) but you are not actually casting anymore- the log says you were interrupted and you are allowed to swing. *This produces the illusion that you are swinging while casting, actually. If you just watch the log as you're selecting/casting a spell you'll notice that the information is being sent a lot faster than it looks like it is graphically. Keep in mind, there's also a meter that calculates your % location in the spell's cast time. I doubt it would be possible to make it so that your attacks are simply not affected by casting (sometimes the stars are going to align the wrong way), but making it so that you do tend to get your attack rounds in while not affecting the cast sounds possible to me, and I think that'd definitely be good enough for what people want.

In PvP, you'll sometimes notice players (on melee + mage jobs) turning their backs while casting a spell in order to "queue up" a melee attack when they're done casting. This leads me to believe that attack rounds are, in fact, happening while you are casting and that they are simply not produced. I don't know if this is common knowledge or not, but eh.

But we're just having fun here, neither of us (or at least I know I sure as hell don't) know very much about what's going on underneath this game.


Are the mechanics beneath this flexible enough to allow them to do something like I mentioned? I have no idea, but I don't think it's unrealistic to think about. Again, the point was just that there may be any number of ways to "make it happen" so to speak. Or maybe it's too complicated and no one could come up with a working solution...I don't know. I think we both agree on the idea that they probably won't be able to do this, but I think it's more of an issue of the size and nature of the development team + whether or not they can be assed to try it. Our disagreement on this seems to be that I think (out of my ass) that's it's probably 65/35 in terms of there being an impractical/practical solution and I think you're more like 95/5.

The real kicker here is that, even if they could do it (even easily), they probably won't lol. I'd love to keep talking about possible solutions though; programming is a lot more fun than discussing melee RDM!

( I kid, as a DRK main I understand the pain of a broken job concept ;; )




*More casting weirdness: That remaining time meter is terribly inaccurate. On long spells, I'll notice myself beginning to cast about 60% into the meter sometimes. I read this as:

1) They are keeping track of casting time in a continuous fashion
2) These calculations are talking to your actual "actions" a lot faster then they are talking to you.

I think that's a good sign for the above idea.