+- SphereCommunity (https://forum.spherecommunity.net)
+-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d)
+--- Forum: General Help (/Forum-General-Help)
+--- Thread: Attacking bug threads O.o (/Thread-Attacking-bug-threads-O-o)
Pages: 1 2
Attacking bug threads O.o - Lazarus - 05-06-2014 12:49 PM
I get some errors when I attack with to another char and I move away from battle:
what can be?
I tried:
-With the normal scripts folder
-With another sphere.ini
-Without Player Events
I don't know what is it!
Last build of script pack and sphere (56c)
Code:
15:26:DEBUG:__ thread (712) __ | # | _____ function _____________ | ticks passed from previous function start ______
15:26:DEBUG:>> 712 | 0 | CWorld::OnTick | +0
15:26:DEBUG:>> 712 | 1 | CSector::OnTick | +0
15:26:DEBUG:>> 712 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
15:26:DEBUG:>> 712 | 3 | CChar::Skill_Done | +0
15:26:DEBUG:>> 712 | 4 | CChar::Skill_Stage | +0
15:26:DEBUG:>> 712 | 5 | CChar::Skill_Fighting | +0
15:26:DEBUG:>> 712 | 6 | CChar::Fight_HitTry | +0
15:26:DEBUG:>> 712 | 7 | CChar::Fight_AttackNext | +0
15:26:DEBUG:>> 712 | 8 | CChar::Fight_Attack | +0
15:26:DEBUG:>> 712 | 9 | CChar::Fight_Clear | +0
15:26:DEBUG:__ thread (712) __ | # | _____ function _____________ | ticks passed from previous function start ______
15:26:DEBUG:>> 712 | 0 | CWorld::OnTick | +0
15:26:DEBUG:>> 712 | 1 | CSector::OnTick | +0
15:26:DEBUG:>> 712 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
15:26:DEBUG:>> 712 | 3 | CChar::Skill_Done | +0
15:26:DEBUG:>> 712 | 4 | CChar::Skill_Stage | +0
15:26:DEBUG:>> 712 | 5 | CChar::Skill_Fighting | +0
15:26:DEBUG:>> 712 | 6 | CChar::Fight_HitTry | +0
15:26:DEBUG:>> 712 | 7 | CChar::Fight_AttackNext | +0
15:26:DEBUG:>> 712 | 8 | CChar::Fight_Attack | +0
15:26:DEBUG:>> 712 | 9 | CChar::Fight_Clear | +0
15:26:DEBUG:__ thread (712) __ | # | _____ function _____________ | ticks passed from previous function start ______
15:26:DEBUG:>> 712 | 0 | CWorld::OnTick | +0
15:26:DEBUG:>> 712 | 1 | CSector::OnTick | +0
15:26:DEBUG:>> 712 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
15:26:DEBUG:>> 712 | 3 | CChar::Skill_Done | +0
15:26:DEBUG:>> 712 | 4 | CChar::Skill_Stage | +0
15:26:DEBUG:>> 712 | 5 | CChar::Skill_Fighting | +0
15:26:DEBUG:>> 712 | 6 | CChar::Fight_HitTry | +0
15:26:DEBUG:>> 712 | 7 | CChar::Fight_AttackNext | +0
15:26:DEBUG:>> 712 | 8 | CChar::Fight_Attack | +0
15:26:DEBUG:>> 712 | 9 | CChar::Fight_Clear | +0
15:26:DEBUG:__ thread (712) __ | # | _____ function _____________ | ticks passed from previous function start ______
15:26:DEBUG:>> 712 | 0 | CWorld::OnTick | +0
15:26:DEBUG:>> 712 | 1 | CSector::OnTick | +0
15:26:DEBUG:>> 712 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
15:26:DEBUG:>> 712 | 3 | CChar::Skill_Done | +0
15:26:DEBUG:>> 712 | 4 | CChar::Skill_Stage | +0
15:26:DEBUG:>> 712 | 5 | CChar::Skill_Fighting | +0
15:26:DEBUG:>> 712 | 6 | CChar::Fight_HitTry | +0
15:26:DEBUG:>> 712 | 7 | CChar::Fight_AttackNext | +0
15:26:DEBUG:>> 712 | 8 | CChar::Fight_Attack | +0
15:26:DEBUG:>> 712 | 9 | CChar::Fight_Clear | +0
15:26:DEBUG:__ thread (712) __ | # | _____ function _____________ | ticks passed from previous function start ______
15:26:DEBUG:>> 712 | 0 | CWorld::OnTick | +0
15:26:DEBUG:>> 712 | 1 | CSector::OnTick | +0
15:26:DEBUG:>> 712 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
15:26:DEBUG:>> 712 | 3 | CChar::Skill_Done | +0
15:26:DEBUG:>> 712 | 4 | CChar::Skill_Stage | +0
15:26:DEBUG:>> 712 | 5 | CChar::Skill_Fighting | +0
15:26:DEBUG:>> 712 | 6 | CChar::Fight_HitTry | +0
15:26:DEBUG:>> 712 | 7 | CChar::Fight_AttackNext | +0
15:26:DEBUG:>> 712 | 8 | CChar::Fight_Attack | +0
15:26:DEBUG:>> 712 | 9 | CChar::Fight_Clear | +0
15:26:CRITICAL:"Access Violation" (0x26f3b), in CChar::Tick() #6 "timer expired"
15:26:DEBUG:__ thread (712) __ | # | _____ function _____________ | ticks passed from previous function start ______
15:26:DEBUG:>> 712 | 0 | CWorld::OnTick | +0
15:26:DEBUG:>> 712 | 1 | CSector::OnTick | +0
15:26:DEBUG:>> 712 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
15:26:DEBUG:>> 712 | 3 | CChar::Skill_Done | +0
15:26:DEBUG:>> 712 | 4 | CChar::Skill_Stage | +0
15:26:DEBUG:>> 712 | 5 | CChar::Skill_Fighting | +0
15:26:DEBUG:>> 712 | 6 | CChar::Fight_HitTry | +0
15:26:DEBUG:>> 712 | 7 | CChar::Fight_AttackNext | +0
15:26:DEBUG:>> 712 | 8 | CChar::Fight_Attack | +0
15:26:DEBUG:>> 712 | 9 | CChar::Fight_Clear | +0
15:26:DEBUG:__ thread (712) __ | # | _____ function _____________ | ticks passed from previous function start ______RE: Attacking bug threads O.o - Coruja - 05-06-2014 01:01 PM
probably it's related to last ATTACKER.x changes, I'm getting exactly this same problem at each ~4sec, even on my test server with no players online
I tried to debug this thing but I have no idea what it could be. If some dev need I can make some tests to find something
Code:
23:56:CRITICAL:"Access Violation" (0x22dbb), in CChar::Tick() #6 "timer expired"
23:56:DEBUG:__ thread (12748) __ | # | _____ function _____________ | ticks passed from previous function start ______
23:56:DEBUG:>> 12748 | 0 | CWorld::OnTick | +0
23:56:DEBUG:>> 12748 | 1 | CSector::OnTick | +15
23:56:DEBUG:>> 12748 | 2 | CChar::OnTick | +16 <-- exception catch point (below is guessed and could be incorrect!)
23:56:DEBUG:>> 12748 | 3 | CChar::Skill_Done | +0
23:56:DEBUG:>> 12748 | 4 | CChar::Skill_Stage | +0
23:56:DEBUG:>> 12748 | 5 | CChar::Skill_Fighting | +0
23:56:DEBUG:>> 12748 | 6 | CChar::Fight_HitTry | +0
23:56:DEBUG:>> 12748 | 7 | CChar::Fight_AttackNext | +0
23:56:DEBUG:>> 12748 | 8 | CChar::Fight_Attack | +0
23:56:DEBUG:>> 12748 | 9 | CChar::Fight_Clear | +0RE: Attacking bug threads O.o - Lazarus - 05-06-2014 01:55 PM
(05-06-2014 01:01 PM)Coruja Wrote: probably it's related to last ATTACKER.x changes, I'm getting exactly this same problem at each ~4sec, even on my test server with no players online
I tried to debug this thing but I have no idea what it could be. If some dev need I can make some tests to find something
So, we should wait for the next release and hope some dev's saw this :'(
RE: Attacking bug threads O.o - Coruja - 05-06-2014 02:12 PM
I think it was fixed on may 6 nightly build
RE: Attacking bug threads O.o - Lazarus - 05-06-2014 02:32 PM
(05-06-2014 02:12 PM)Coruja Wrote: I think it was fixed on may 6 nightly build
I love you?
How can I check my Rev Build of Scripts?
RE: Attacking bug threads O.o - Coruja - 05-08-2014 01:27 AM
just use .show serv.build
or check the build date on nightly download page
it's working fine here using latest build
RE: Attacking bug threads O.o - Lazarus - 05-08-2014 02:55 AM
(05-08-2014 01:27 AM)Coruja Wrote: just use .show serv.build
or check the build date on nightly download page
it's working fine here using latest build
Windows 7 64 bits - Last serv.build 1913 with default sphere folder and scripts (all default) with my own sphere.ini still have the errors.
And the Scriptpack revisions viewer doesn't work http://scripts.spherecommunity.net/
How to replay the error:
-a GM hitting a player with 29129193 dex and 12931903901 hits
-when you're hitting the player, .invul 0 and .gm 0 (or before you start hitting, is the same)
-hit some damage and then go away
-sphereserver get's errors like hell.
![[Image: 8ca3a452b4f3c1f8480874570bd92ec3o.png]](http://fotos.subefotos.com/8ca3a452b4f3c1f8480874570bd92ec3o.png)
RE: Attacking bug threads O.o - kn4tseb - 05-12-2014 09:44 AM
having same error with may 11th release
20:55:DEBUG:__ thread (6740) __ | # | _____ function _____________ | ticks passed from previous function start ______
20:55:DEBUG:>> 6740 | 0 | NetworkManager::processAllInput | +0
20:55:DEBUG:>> 6740 | 1 | NetworkInput::processInput | +0
20:55:DEBUG:>> 6740 | 2 | NetworkInput::processData | +0
20:55:DEBUG:>> 6740 | 3 | NetworkInput::processData | +0
20:55:DEBUG:>> 6740 | 4 | NetworkInput::processGameClientData | +0
20:55:DEBUG:>> 6740 | 5 | PacketCreateHS::onReceive | +0
20:55:DEBUG:>> 6740 | 6 | PacketCreate::onReceive[1] | +0
20:55:DEBUG:>> 6740 | 7 | PacketCreate::doCreate | +0
20:55:DEBUG:>> 6740 | 8 | CClient::Setup_Start | +15
20:55:DEBUG:>> 6740 | 9 | CClient::addPlayerStart | +0
20:55:DEBUG:>> 6740 | 10 | CChar::Update | +0
20:55:DEBUG:>> 6740 | 11 | CClient::addReSync | +0
20:55:DEBUG:>> 6740 | 12 | CClient::addPlayerView | +0
20:55:DEBUG:>> 6740 | 13 | CClient::addPlayerSee | +0
20:55:DEBUG:>> 6740 | 14 | CClient::addChar | +0 <-- exception catch point (below is guessed and could be incorrect!)
20:55:DEBUG:>> 6740 | 15 | PacketCharacter::PacketCharacter | +0
20:55:DEBUG:>> 6740 | 16 | CChar::Noto_GetFlag | +0
20:55:DEBUG:>> 6740 | 17 | CChar::NotoSave_GetValue | +0
20:55:CRITICAL:Exception, in CClient::addChar()
20:55:DEBUG:m_dirFace (03)
20:55:DEBUG:__ thread (6740) __ | # | _____ function _____________ | ticks passed from previous function start ______
20:55:DEBUG:>> 6740 | 0 | NetworkManager::processAllInput | +0
20:55:DEBUG:>> 6740 | 1 | NetworkInput::processInput | +0
20:55:DEBUG:>> 6740 | 2 | NetworkInput::processData | +0
20:55:DEBUG:>> 6740 | 3 | NetworkInput::processData | +0
20:55:DEBUG:>> 6740 | 4 | NetworkInput::processGameClientData | +0
20:55:DEBUG:>> 6740 | 5 | PacketCreateHS::onReceive | +0
20:55:DEBUG:>> 6740 | 6 | PacketCreate::onReceive[1] | +0
20:55:DEBUG:>> 6740 | 7 | PacketCreate::doCreate | +0
20:55:DEBUG:>> 6740 | 8 | CClient::Setup_Start | +15
20:55:DEBUG:>> 6740 | 9 | CClient::addPlayerStart | +0
20:55:DEBUG:>> 6740 | 10 | CChar::Update | +0
20:55:DEBUG:>> 6740 | 11 | CClient::addChar | +125 <-- exception catch point (below is guessed and could be incorrect!)
20:55:DEBUG:>> 6740 | 12 | PacketCharacter::PacketCharacter | +0
20:55:DEBUG:>> 6740 | 13 | CChar::Noto_GetFlag | +0
20:55:DEBUG:>> 6740 | 14 | CChar::NotoSave_GetValue | +0
20:55:DEBUG:m_dirFace (03)
20:55:DEBUG:__ thread (6740) __ | # | _____ function _____________ | ticks passed from previous function start ______
20:55:DEBUG:>> 6740 | 0 | NetworkManager::processAllInput | +0
20:55:DEBUG:>> 6740 | 1 | NetworkInput::processInput | +0
20:55:DEBUG:>> 6740 | 2 | NetworkInput::processData | +0
20:55:DEBUG:>> 6740 | 3 | NetworkInput::processData | +0
20:55:DEBUG:>> 6740 | 4 | NetworkInput::processGameClientData | +0
20:55:DEBUG:>> 6740 | 5 | PacketCreateHS::onReceive | +0
20:55:DEBUG:>> 6740 | 6 | PacketCreate::onReceive[1] | +0
20:55:DEBUG:>> 6740 | 7 | PacketCreate::doCreate | +0
20:55:DEBUG:>> 6740 | 8 | CClient::Setup_Start | +15
20:55:DEBUG:>> 6740 | 9 | CChar::Update | +172
20:55:DEBUG:>> 6740 | 10 | CClient::addChar | +0 <-- exception catch point (below is guessed and could be incorrect!)
20:55:DEBUG:>> 6740 | 11 | PacketCharacter::PacketCharacter | +0
20:55:DEBUG:>> 6740 | 12 | CChar::Noto_GetFlag | +0
20:55:DEBUG:>> 6740 | 13 | CChar::NotoSave_GetValue | +0
20:55:DEBUG:m_dirFace (03)
20:55:DEBUG:__ thread (6740) __ | # | _____ function _____________ | ticks passed from previous function start ______
20:55:DEBUG:>> 6740 | 0 | NetworkManager::processAllInput | +0
20:55:DEBUG:>> 6740 | 1 | NetworkInput::processInput | +0
20:55:DEBUG:>> 6740 | 2 | NetworkInput::processData | +0
20:55:DEBUG:>> 6740 | 3 | NetworkInput::processData | +0
20:55:DEBUG:>> 6740 | 4 | NetworkInput::processGameClientData | +0 <-- exception catch point (below is guessed and could be incorrect!)
20:55:DEBUG:>> 6740 | 5 | PacketMovementReq::onReceive | +0
20:55:DEBUG:>> 6740 | 6 | PacketMovementReq::doMovement | +0
20:55:DEBUG:>> 6740 | 7 | CClient::Event_Walking | +0
20:55:DEBUG:>> 6740 | 8 | CChar::UpdateMode | +0
20:55:DEBUG:>> 6740 | 9 | CClient::addCharMove | +0
20:55:DEBUG:>> 6740 | 10 | CClient::addCharMove | +0
20:55:DEBUG:>> 6740 | 11 | PacketCharacterMove::PacketCharacterMove | +0
20:55:DEBUG:>> 6740 | 12 | CChar::Noto_GetFlag | +0
20:55:DEBUG:>> 6740 | 13 | CChar::NotoSave_GetValue | +0
20:55:CRITICAL:Exception, in SUB: NetworkInput::Message::ProcessMessage()
20:55:DEBUG:1:Parsing Packet len=7 id=0x02 [2014/05/11 20:55:31]
0 1 2 3 4 5 6 7 8 9 A B C D E F
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
0000 02 84 00 e5 95 8a e6 .......
RE: Attacking bug threads O.o - amonvangrell - 05-12-2014 02:02 PM
I'm concern.... O.o"
RE: Attacking bug threads O.o - kn4tseb - 05-12-2014 02:28 PM
Just tried it with may 2 compilation and no errors are shown, everything seems to work fine with that build