This repository has been archived by the owner on Apr 29, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 550
Maat Broken Again #3633
Comments
https://github.com/DarkstarProject/darkstar/blob/master/sql/mob_family_system.sql#L403 Give the Maat family a detection method, otherwise it won't be able to engage because it doesn't have a way to track the target. |
Brierre
added a commit
to Brierre/darkstar
that referenced
this issue
Jan 9, 2017
Brierre
added a commit
to Brierre/darkstar
that referenced
this issue
Jan 9, 2017
The fatal error is unrelated to the detection: tons of mobs were missing detection, none of them generated a fatal error message. So multiple bugs one report basically. Probably related to that BCNM entry. Btw, Maat wouldn't have a prob engaging from that (he doesn't attack till you do anyway). He'd just be really easy to de-aggro. |
Also Kj fixed the nextrow thing, which I forgot about |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have:
Client Version (type
/ver
in game) :30161206_3
Server Version (type
@revision
in game) :62fa641
Source Branch (master/stable) :
Master
Additional Information (Steps to reproduce/Expected behavior) :
I dunno what this fatal error is but seems kinda serious
[08/Jan] [16:44:54][LUA Script] UPDATE csid 32000 option 255
[08/Jan] [16:44:54][Error] Mobutils::CalculateStats Mob (Maat, 17367077, 335) ha no detection methods!
[08/Jan] [16:44:54][Fatal Error] Sql_NextRow: SQL_ERROR
The text was updated successfully, but these errors were encountered: