Chatlog readings for damage sources outside 30'

[Kristal]

Hello~

Thank you for the suggestion! We can certainly understand the functionality of this request but this is where we currently stand:

System wise, we can extend the range that chat logs receive information. The issue is that if we do widen that range, it will cause an increase in lag. We wouldn't want an unexpected decrease in frame rate especially during intense battles. We hope for your understanding.

I have a hard time seeing how it could increase lag. How would showing 18 people getting hit at 20' be any different from 18 people getting hit at 40'? I'm not asking to see OTHER people's damage numbers, I only want to be notified when my own character is hit by any type of damage or effect, regardless of distance to it's source.

If chatlog can't be used, show at the very least some graphical effect, like damage numbers or spell effects.

[Puck]

Why do the devs bother responding to anything anymore?

Here's how it goes:
Player: "Here's a reasonable request to make our gameplay experience better."
Devs: "Thanks, but we can't do it because of blahblah system balance monkeypicklebanana etc."

[Demon6324236]

Why do the devs bother responding to anything anymore?

Here's how it goes:
Player: "Here's a reasonable request to make our gameplay experience better."
Devs: "Thanks, but we can't do it because of blahblah system balance monkeypicklebanana etc."

I see it as better than before. We got a reason, not just the word balance or "we can not do it due to technical problems it would cause." I am guessing it is probably that by increasing the range the game would have to register all things at that range which can create alot more work for the game to do. Also if it constantly monitors that range for activity to give information for in the chatlog then it would slow it even more thanks to it constantly trying to see what might be going on. Not sure if that makes any sense but really this isn't bad, the are getting better at listening and telling us the problems I think.

[Kristal]

I see it as better than before. We got a reason, not just the word balance or "we can not do it due to technical problems it would cause." I am guessing it is probably that by increasing the range the game would have to register all things at that range which can create alot more work for the game to do. Also if it constantly monitors that range for activity to give information for in the chatlog then it would slow it even more thanks to it constantly trying to see what might be going on. Not sure if that makes any sense but really this isn't bad, the are getting better at listening and telling us the problems I think.

But it has to register all things anyway, since we're still getting hit with Meteor without seeing it. I think the problem lies with aoe that hit anyone in a 40' range, not just those that have claim. In that case, the lag would go up. You'd also be dead, since you never saw it coming.

[Demon6324236]

Well the damage I think would be done server side, as you take damage so your receiving data that your HP is lower than it was. However client side no info about the attack, it hitting you, or you taking damage, was done, only information was received to tell you your HP went down. Thats what I think might be the case though.

[Dragoy]

Teegrins!

The issue is that if we do widen that range, it will cause an increase in lag. We wouldn't want an unexpected decrease in frame rate especially during intense battles. We hope for your understanding.

This part I am having a bit of a hard time digesting.

If you are participating in an intense battle, you would want to see the information regardless, I would imagine. I really don't see abilities reaching that far bringing any more fun challenge to the battle in the first place though.

As for an increase in lag? Lag for what, exactly? Is it affecting the rate that which the frames are being displayed just another way of saying “PS2-limitations”?

<cough>

In any case, if it's that bad, I truly feel sorry for the people who have to work with the code... and for us, too.


Blubb.