The following warnings occurred:
Warning [2] Use of undefined constant SAPI_NAME - assumed 'SAPI_NAME' (this will throw an Error in a future version of PHP) - Line: 3388 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3388 errorHandler->error
/showthread.php 116 build_archive_link
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/inc/functions.php 3324 build_forum_breadcrumb
/showthread.php 195 build_forum_breadcrumb
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb






Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
undefined packet sphere 56b and 56c exploding.
Author Message
Coruja
Sphere Developer
*****

Posts: 987
Likes Given: 5
Likes Received: 226 in 187 posts
Joined: Jul 2012
Reputation: 7

Dimension Shard

Post: #20
RE: undefined packet sphere 56b and 56c exploding.
56d is compatible with old scripts, of course to jump from an 8 year ago 56b to the latest 56d you can't just update your SphereSvr.exe, there's some root scripts that must be updated too (sphere.ini, sphere_defs.scp, sphere_msgs.scp, spheretables.scp, ...) but in general all triggers/functions/etc still the same

depending how deep is your server customization, this can be an simple copy/paste overwriting all scripts or even an manual work of many weeks, but this is only valid to root scripts. You doesn't have to rewrite all your custom systems, custom items, etc. Unfortunately custom changes made by users on root scripts are not our responsability, so although we always try to keep everything backward compatible, sometimes the user itself made so many custom changes on his code that this will turn into a headache when these scripts must be updated to match the latest official changes

it still worth update these scripts to keep using the latest updates (56d) rather than use an old sphere build (56b), but anyway, you can find some official 56b builds here: https://github.com/Sphereserver/Source/releases
the latest 56b build is from 2013, maybe it could be better than an 56b build from 2009
(This post was last modified: 05-17-2017 01:16 PM by Coruja.)
05-17-2017 01:11 PM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Messages In This Thread
RE: undefined packet sphere 56b and 56c exploding. - Coruja - 05-17-2017 01:11 PM

Forum Jump:


User(s) browsing this thread: 5 Guest(s)