+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d)
+--- Forum: General Help (/Forum-General-Help)
+--- Thread: 56d Crash Bug (/Thread-56d-Crash-Bug)
56d Crash Bug - aserehe - 10-12-2018 08:40 AM
Hi,
Crash bug on staff commands. I'm using .111 command than sphere loop this errors.
Compiled: Sep 27 2018 (07:29:31) [build 698 / Git hash 9e95d075]
01:32:1:Account 'admin' logged on char 'Admin' ('xxx.xxx.xxx.xxx')
01:32:1:'Admin' Says UNICODE 'ENU' '1' mode=0
01:32:1:'admin' commands '111'=1
01:32:DEBUG:__ thread (4228) __ | # | _____________ function _____________ | __ ticks passed from previous function start __
01:32:DEBUG:>> 4228 | 0 | CWorld::OnTick | +0
01:32:DEBUG:>> 4228 | 1 | CSector::OnTick | +0
01:32:DEBUG:>> 4228 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
01:32:DEBUG:>> 4228 | 3 | CChar::NotoSave_CheckTimeout | +0
01:32:CRITICAL:"Access Violation" (0xfff27710), in CChar::Tick() #2 "NOTO timeout"
01:32:DEBUG:__ thread (4228) __ | # | _____________ function _____________ | __ ticks passed from previous function start __
01:32:DEBUG:>> 4228 | 0 | NetworkManager::processAllInput | +0
01:32:DEBUG:>> 4228 | 1 | NetworkManager::checkNewConnection | +0
01:32:CRITICAL:"Access Violation" (0xffee7119), in Sphere::Tick() #4 "network-in"
01:32:DEBUG:__ thread (4228) __ | # | _____________ function _____________ | __ ticks passed from previous function start __
01:32:DEBUG:>> 4228 | 0 | NetworkManager::processAllInput | +0
01:32:DEBUG:>> 4228 | 1 | NetworkManager::checkNewConnection | +0
RE: 56d Crash Bug - Coruja - 10-12-2018 10:51 AM
when you call functions only using numbers sphere will assume that the first value is an skill number and the second value is the skill value. So using ".12 50.0" as example, it will set cartography (skill 12) = 50.0 on the char
but the higher skill number is 57 (throwing), the skill 111 doesn't exist and sphere will just ignore it if you type ".111". So try check if your scripts have any kind of custom funcion named "111", probably this is creating a conflict with some internal sphere function
RE: 56d Crash Bug - aserehe - 10-12-2018 05:42 PM
No, i'm using default sphere script pack.
Latest SphereServer Script Pack
https://github.com/Sphereserver/Scripts/archive/master.zip
RE: 56d Crash Bug - aserehe - 10-14-2018 04:29 AM
Sphere crash are 108 109 110 111 and 112 commands.
Fix:
[f_oncommand]
for x 108 112
if (strmatch('<args>', '<local.x>'))
src.sysmessage Not a valid command
endif
endfor
RE: 56d Crash Bug - Coruja - 10-16-2018 05:29 AM
sounds weird, I'm also testing on latest build with latest script pack
Code:
16:23:1:'admin' commands '105'=1
16:23:1:'admin' commands '106'=1
16:23:1:'admin' commands '107'=1
16:23:1:'admin' commands '108'=1
16:23:1:'admin' commands '109'=1
16:23:1:'admin' commands '110'=1
16:23:1:'admin' commands '111'=1
16:23:1:'admin' commands '112'=1
16:23:1:'admin' commands '113'=1
16:23:1:'admin' commands '114'=1
16:23:1:'admin' commands '115'=1probably you should have something on your scripts conflicting with these internal functions, forcing sphere to create an infinite loop