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




Arguments in favor of the name change.
#4
  • The name it is extremely generic - expanding to “MineCraft Server”, which leads to confusion from people who hear about “MCServer” and think it’s just some new minecraft server or something. A more unique name would also increase the discoverability of the project, by increasing search rankings on branded queries and reducing the confusion of people using “MCServer” in general speech.

  • Since the name expands to “MineCraft Server”, it is could be construed to violate Notch Development AB’s trademarks and it therefore leaves the project vulnerable to legal action by Notch Development AB to protect their IP. This is a VERY IMPORTANT issue, it could completely ruin the project and should make a name change the top priority.

  • The current name of MCServer is also fairly hard to pronounce - “M C Server” rather than a simpler name like “Bukkit” or “Cube-right”.
    At the current time, there is no consistent brand for MCServer. By rebranding the online assets of MCServer at the same time as changing the name we could reduce overall effort and create a more consistent identity for the project. Rebranding and homogenisation of online presence would also be also easier after a name change, because “Cuberite” usernames are free in many places, whereas “MCServer” usernames and domain names are mostly taken and hard to come by.

  • Now would also be a good time to change the name of the project, as it has relatively few people who know about it, in comparison with mature Minecraft server projects like Bukkit or Spigot. It would be better to change the name of the project now rather than wait until later, when it would be much harder, if not impossible to change the name.
Reply
Thanks given by:


Messages In This Thread
RE: Arguments in favor of the name change. - by bearbin - 05-25-2015, 02:44 AM



Users browsing this thread: 1 Guest(s)