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




Lighting-related block variables
#11
Yes, that's what I meant by desync - the lighting was written too long ago and the newer blocks don't have their values set yet, because no-one updated those. That's what's causing the black ladders in the server, among other things.
Reply
Thanks given by:
#12
Well i'm currently working on the list, i think it will be finish this evening Smile

btw wouldn't it be easier if we move the "can't push" list out of the BlockPiston.h into in the BlockInfo.cpp?
Reply
Thanks given by:
#13
Probably should, on the contrary, move 'can break' into the piston handler since no one uses it. But maybe not.
Reply
Thanks given by:
#14
The question is, when a new block is added, will you remember to update the piston code to reflect whether the block is breakable / pushable? Or are you more likely to update it if it's in the BlockInfo together with all the other blocks?
Reply
Thanks given by:
#15
Maybe have a point in Guidelines for Contributing making a note of bring both locations up to date?
Reply
Thanks given by:




Users browsing this thread: 2 Guest(s)