Adjust the behavior of out of range aggro removal

This is a bit more accurate
This commit is contained in:
Michael Cook (mackal)
2018-01-18 19:59:04 -05:00
parent a7310cba17
commit a440269c6b
3 changed files with 17 additions and 3 deletions
+1
View File
@@ -31,6 +31,7 @@ struct struct_HateList
int32 hatelist_damage;
uint32 stored_hate_amount;
bool is_entity_frenzy;
int8 oor_count; // count on how long we've been out of range
uint32 last_modified; // we need to remove this if it gets higher than 10 mins
};