View Full Version : Chatlog readings for damage sources outside 30'
Kristal
09-11-2012, 06:39 PM
Some enemies use attacks that extend beyond the visiblity range of 30'. These attacks never show up in the log, but any damage or status effect does affect the player still.
Please make it possible to at least see those effects on the player itself. If I'm being hit by a 40' AoE Ochre Blast at 35', my only indication is a sudden loss of HP. At the very least any damage done to me should show up in my chat log, even if I cannot see party members in range being hit as well.
SMD111
09-11-2012, 08:35 PM
this is a realy good request
Mirage
09-11-2012, 10:04 PM
Yes, indeed.
Perhaps it would be best to add chat-log-range settings to the config, so that each player could set it to what they like the best.
Okipuit
09-13-2012, 07:39 AM
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.
Zubis
09-13-2012, 07:55 AM
The most obvious question then is why continue to add NM attacks that can hit for 40+ yalms?
Demon6324236
09-13-2012, 07:57 AM
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.
Can a change in range for enemy attacks be made so that this problem is avoided? Or can you add a function to adjust the range so that if players wish to see farther it is an option and they choose said option at their own risk?
Kaisha
09-13-2012, 08:12 AM
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.
Just adjust stuff on the server-end to extend the range on select abilities that hit folks at absurd ranges, rather than for everything.
Mirage
09-13-2012, 08:22 AM
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.
And that's why the range should be adjustable client-side. Then people who have framerate issues could leave it at a setting where they can play normally.
-edit-
Furthermore, I believe you are misunderstanding what it is we are asking for. We do not ask for the game to display battle animations past 30 yards away, only for our chatlog to display what is happening. I seriously doubt the extra lines of combat log from 30 yards away would affect the framerate of the game. If that was true, our framerate would drop if we were in a very active linkshell where people talked extremely much.
But in the case I am wrong about that, as I said, let players change it manually if they know they have a computer that can handle it. There really is nothing in your reply that makes it sound like increasing the range would cause an actual problem.
Septimus
09-13-2012, 09:36 AM
The most obvious question then is why continue to add NM attacks that can hit for 40+ yalms?
Not allowing mobs to hit from 40+ yalms away would also increase lag. Somehow.
Insaniac
09-13-2012, 10:44 AM
Any AoE range beyond 30 is kinda superfluous anyway. You already can't participate in the fight anymore unless of course you are there to heal mages and ranged attackers which is not exactly a prevalent strategy. Just make 30 the max range on any AoE for an easy peasy fix.
Kristal
09-13-2012, 05:53 PM
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.
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
09-13-2012, 09:04 PM
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
09-13-2012, 10:52 PM
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
09-13-2012, 11:14 PM
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
09-20-2012, 10:59 PM
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.