kalabasa Posted March 12, 2022 Posted March 12, 2022 i already set to hide_woe_damage: 1 is this the default behavior? all server's out there are no visible damage at all. Quote
0 mrfizi Posted March 14, 2022 Posted March 14, 2022 // When set to yes, the damage field in packets sent from woe maps will be set // to -1, making it impossible for GMs, Bots and Hexed clients to know the // actual damage caused by attacks. (Note 1) hide_woe_damage: no Read Note 1: //-------------------------------------------------------------- // Note 1: Value is a config switch (on/off, yes/no or 1/0) // Note 2: Value is in percents (100 means 100%) // Note 3: Value is a bit field. If no description is given, // assume unit types (1: Pc, 2: Mob, 4: Pet, 8: Homun, 16: Mercenary) //-------------------------------------------------------------- Almost all server that I've played hide woe damage. Quote
0 kalabasa Posted March 15, 2022 Author Posted March 15, 2022 still the "1" damage popping out above's character's head. maybe this is covered by grf side? Quote
0 mrfizi Posted March 16, 2022 Posted March 16, 2022 hide_woe_damage: yes I've prefer to write yes I'm sure if you still got this issue after changing it, the problem is your client. You can refer this discussion for more info: Quote
0 kalabasa Posted March 18, 2022 Author Posted March 18, 2022 i check my saved nemo profile. i don't have Enable GvG damage display toggle on either. and yeah i already set to "yes". On 3/16/2022 at 11:23 PM, mrfizi said: hide_woe_damage: yes I've prefer to write yes I'm sure if you still got this issue after changing it, the problem is your client. You can refer this discussion for more info: Quote
Question
kalabasa
i already set to
hide_woe_damage: 1
is this the default behavior?
all server's out there are no visible damage at all.
4 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.