Diablo 4 screenshots9/20/2023 ![]() ![]() My issue with this is that sometimes I attack monster A and the shot hits monster B (and no, monster B is not crossing the projectile path, nor is too close to monster A).Īlso if I have an imp or a scavenger running straight toward me and I attack them an istant before they stop to attack me, my attack is shot BEHIND my character. Maybe this is latency related so it will be fine when I'll play on EU servers.īut it will not encourage me to play with my US friends (maybe softcore, no HC) and our Aussie/New Zeland/SE-Asia friends have all my sympathies.Ībout move button: I use it, also you can just click on a clear spot anywhere on the screen and, still holding down mouse button, move the cursor around, your char will navigate without attacking. If anybody else is willing to try it with lower/higher latencies and share some screenie it would be good. If we're lucky, they can just make the guessing less aggressive by changing a variable or something.Ībout lag: my average latency is 225ms ,so quite high. With the game being so close to release, I'm not sure they'll overhaul their netcode to fix the issue. ![]() Unfortunately this means having a key bound to force move seems to be the only real solution at present. When you want to move to a small free space and the system is "guessing" monster movement then the targeting boxes could overlap and cause you to attack instead of move. I have rarely been over 100ms in the beta, so that might be why I've never seen the issue, but I can understand why it would be a problem. I'm guessing it's a feature to help you if you click on a monster and he had moved from when you clicked, due to lag, you would still hit him because the server would guess what your target should have been at that given point in time. If you have a large latency, your data is coming in with a higher variance, the system needs to compensate for that. ![]() I think it's a valid point that this issue may also be affected by lag. I have seen spells miss a monster by inches, if the boxes were as large as suggested here, I'd never see that. To me the "hitbox" is the box that represents the monster in the game world and determines if a skill will "hit" the monster. Is it the "hitbox" that's the problem or the "targeting box". I think there needs to be some distinction here. The good news is that you can bind another mouse button to move so if you have a multi-button mouse you can still use left click to attack and move with another button. Maybe the best solution is just to have Left Click be for moving only and bind everything else to keys / mouse buttons. ![]() click to move is an awkward system sometimes, but I don't think we can say the D2 system was better. I understand the dilemma that Blizzard faces though. With the default bindings being 1-4, you're not encouraged to hold Shift in order to attack or Ctrl to move (if it actually works like that. I guess they want you to be able to move towards an enemy with left click when using melee abilities? Using Left Click for moving and attacking is problematic for range classes. the controls for this game seem like they'll be awkward at times. Having huge hitboxes is better than having tiny ones while still using left click I suppose. I understand why the hitboxes are that big so that you don't accidently move right next to an enemy when you're trying to fire from range but this looks messy. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |