The following warnings occurred:
Warning [2] Trying to access array offset on null - Line: 198 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 198 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined property: DB_MySQLi::$google_seo_query_limit - Line: 232 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 232 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Decrement on type null has no effect, this will change in the next major version of PHP - Line: 232 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 232 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined array key 1 - Line: 287 - File: inc/plugins/google_seo/redirect.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo/redirect.php 287 errorHandler->error_callback
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined array key 1 - Line: 288 - File: inc/plugins/google_seo/redirect.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo/redirect.php 288 errorHandler->error_callback
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined array key "" - Line: 301 - File: inc/plugins/google_seo/redirect.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo/redirect.php 301 errorHandler->error_callback
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined array key "" - Line: 308 - File: inc/plugins/google_seo/redirect.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo/redirect.php 308 errorHandler->error_callback
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined variable $change - Line: 345 - File: inc/plugins/google_seo/redirect.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo/redirect.php 345 errorHandler->error_callback
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once




XP Level Limit?
#1
It seems that the server screams at me whenever I reach an xp level above 117. It says "Attempted to update invalid using an invalid value: -32512" or something like that. Is that a server limitation because vanilla servers can go up to 250 and upwards. Going above 117 would be useful for my MCSmash plugin because I use that for the damage indicator.
Reply
Thanks given by:
#2
I look into it.

EDIT:
the server is using a short int for experience. (xp not level)

Why? I have no idea.
Reply
Thanks given by:
#3
Ok, I'm kinda using a bit of a cheesy method to get around that, but its nowhere near as desirable. It seems somewhat of an arbitrary limit.
Reply
Thanks given by:
#4
It looks like the restriction was put in place in Nov 2013 in PR 353. As for why it was put in place their is no mention, but we probably want to bump it to a 32 bit value to match minecraft.

I think I've found the reason. Prior to snapshot 14w04a the experience was sent to the client as a 16 bit value. So their was no need to be able to store larger values. However since the protocols prior to that snapshot have been removed we might as well increase the value to an int.
Reply
Thanks given by:
#5
Ok, that will be quite a bit more optimal, thanks. Smile
Reply
Thanks given by:




Users browsing this thread: 1 Guest(s)