Gypsy Paz Posted July 18, 2014 Share Posted July 18, 2014 0: XP_ERROR_NONE1: XP_ERROR_THROTTLED2: XP_ERROR_EXPERIENCES_DISABLED3: XP_ERROR_INVALID_PARAMETERS4: XP_ERROR_NOT_PERMITTED5: XP_ERROR_NO_EXPERIENCE6: XP_ERROR_NOT_FOUND7: XP_ERROR_INVALID_EXPERIENCE8: XP_ERROR_EXPERIENCE_DISABLED9: XP_ERROR_EXPERIENCE_SUSPENDED11: XP_ERROR_QUOTA_EXCEEDED12: XP_ERROR_STORE_DISABLED13: XP_ERROR_STORAGE_EXCEPTION14: XP_ERROR_KEY_NOT_FOUND15: XP_ERROR_RETRY_UPDATE10: XP_ERROR_UNKNOWN_ERROR16: XP_ERROR_MATURITY_EXCEEDED Here are the correct error codes. They appear to be listed wrong on the two wiki pages. Link to comment Share on other sites More sharing options...
Qie Niangao Posted July 19, 2014 Share Posted July 19, 2014 EDIT: As penance, I went ahead and modified these constants in https://wiki.secondlife.com/wiki/Template:LSL_Constants/Experience_Tools_Errors so they should now correspond to Gypsy's sequence. (Gypsy, sorry, I keep adding tangents onto your threads. :matte-motes-bashful-cute:) Speaking of error codes, llGetExperienceDetails() has been reporting a state of 4 and corresponding state_message of "operation not permitted" ever since somebody said no to it once (or something) despite many intervening successes. Is anything supposed to clear that status back to 0? Link to comment Share on other sites More sharing options...
Lindens Dolphin Linden Posted July 20, 2014 Lindens Share Posted July 20, 2014 llGetExperienceDetails doesn't care about agent permissions, it just checks the estate and parcel settings. If it is allowed and not blocked on either the parcel or the estate then you should not be getting that code. Link to comment Share on other sites More sharing options...
Qie Niangao Posted July 20, 2014 Share Posted July 20, 2014 Okay, it's certainly the case that I've tried to use my Experience on parcels before I remembered to enable it for the parcel, so I have no doubt that's how llGetExperienceDetails came to return that code. But that problem has been resolved long ago and everything seems to be working fine, yet I still get that same status code in the details list. Is it supposed to reflect the status of the last Experience-related operation (and thus clear to 0 after success) or is it always the code for the most recent error regardless of when that may have happened? It seems to be behaving a bit like errno but with no way to clear the status. Link to comment Share on other sites More sharing options...
Lindens Dolphin Linden Posted July 20, 2014 Lindens Share Posted July 20, 2014 It does a live check every time the function is called so it certainly shouldn't be retaining anything. Send me a slurl and the name of the object in question and I can take a look. Link to comment Share on other sites More sharing options...
Recommended Posts
Please take a moment to consider if this thread is worth bumping.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now