+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d)
+--- Forum: General Help (/Forum-General-Help)
+--- Thread: undefined packet sphere 56b and 56c exploding. (/Thread-undefined-packet-sphere-56b-and-56c-exploding)
RE: undefined packet sphere 56b and 56c exploding. - aserehe - 02-10-2017 04:32 AM
The player does not die when this setting is 0. There's nothing to do with these mistakes
RE: undefined packet sphere 56b and 56c exploding. - xwerswoodx - 02-10-2017 05:32 AM
(02-10-2017 04:32 AM)aserehe Wrote: The player does not die when this setting is 0. There's nothing to do with these mistakes
It is 0 for me and everyone can die in my sphere
PacketDeathAnimation setting is only an animation for death. Maybe you need to check your @Death triggers.
RE: undefined packet sphere 56b and 56c exploding. - aserehe - 02-10-2017 07:18 AM
It's 0 for die chars but screen is not black.
RE: undefined packet sphere 56b and 56c exploding. - Criminal - 02-15-2017 04:29 AM
I remember some crashes in 56b(while PacketDeathAnimation was not in ini) with randoms packets recived, I think is same problem
RE: undefined packet sphere 56b and 56c exploding. - aserehe - 03-10-2017 05:53 PM
Yes, same problem.
RE: undefined packet sphere 56b and 56c exploding. - Coruja - 03-11-2017 12:53 PM
as we already said some time ago, the best and only way to fix this is using sphere 56d instead any other old version
RE: undefined packet sphere 56b and 56c exploding. - Aimed - 05-12-2017 10:00 AM
I want to fix this issue for the latest 56b release.
How do I build this https://github.com/Sphereserver/Source2/releases/tag/56b-20130616
I didn't find CMakeLists.txt anywhere. I'm Using Cmake 3.5.0
What tools do I need to build this? Provide me with a readme if u can, please.
RE: undefined packet sphere 56b and 56c exploding. - Aimed - 05-12-2017 08:31 PM
Hey guys, we might've found a 56b release which doesn't crash on this packet.
We've tested it by sending 0xff packets and it didn't crash. I'm not sure if that was a right test case, maybe packet size and content also does matter. Would need a dump from Spheres which have been crashed this way.
Anyway, here's the windows build
And for Linux just build this release
If you don't trust this windows build link, you can build it yourself on windows of course
RE: undefined packet sphere 56b and 56c exploding. - Aimed - 05-13-2017 01:22 AM
(03-11-2017 12:53 PM)Coruja Wrote: as we already said some time ago, the best and only way to fix this is using sphere 56d instead any other old version
Maybe you should do something with compatibility? Seems like even on different releases of 56b some scripts don't work properly.
How do you expect people will upgrade, if they might have spent hundreds or thousands of hours writing scripts and they are going to get broken by an upgrade? : /
RE: undefined packet sphere 56b and 56c exploding. - Coruja - 05-17-2017 01:11 PM
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