SphereServer BugTracker - SphereServer
View Issue Details
0002357SphereServerexecutable - windows buildpublic31-05-14 20:1507-06-14 09:12
TigerBlitz 
XuN 
normalmajoralways
resolvedfixed 
 
0.56c Nightly 
Automated (specify build number)
None
None
0002357: When i attack get this error on Sphere Console..
Hi im using latest 56c nightly. And i was testing some items on my local shard and when i attack with this item getting some critical error on S-Console

[ITEMDEF i_flamesword]
NAME=Greater Flamestrike Sword
ID=I_SWORD_VIKING
TYPE=T_WEAPON_SWORD
DAM=50,50
REQSTR=100
WEIGHT=0.5
VALUE=500
SKILL=Swordsmanship

CATEGORY=Weapons
SUBSECTION=Greater Flamestrike Sword
DESCRIPTION=Sword

ON=@Create
HITPOINTS=50000
COLOR=025

ON=@DAMAGE
SRC.SOUND=SND_SPELL_FLAMESTRIKE
SRC.EFFECT=3,i_fire_column,6,15,1
SRC.HITS=(<SRC.HITS>+-100)
IF (<CONT.HITS><<CONT.STR>)
    CONT.HITS <CONT.HITS>+50
ENDIF



20:59:DEBUG:__ thread (4324) __ | # | _____ function _____________ | ticks passed from previous function start ______
20:59:DEBUG:>> 4324 | 0 | CWorld::OnTick | +0
20:59:DEBUG:>> 4324 | 1 | CSector::OnTick | +0
20:59:DEBUG:>> 4324 | 2 | CChar::OnTick | +0 <-- exception catch point (below is guessed and could be incorrect!)
20:59:DEBUG:>> 4324 | 3 | CChar::OnTickEquip | +0
20:59:DEBUG:>> 4324 | 4 | CChar::Memory_OnTick | +0
20:59:DEBUG:>> 4324 | 5 | CChar::Memory_Fight_OnTick | +0
20:59:DEBUG:>> 4324 | 6 | CChar::Attacker_GetID(CChar) | +0
20:59:CRITICAL:"Access Violation" (0x2804d), in SUB: CChar::Char::Ticking items()
No tags attached.
Issue History
31-05-14 20:15TigerBlitzNew Issue
31-05-14 23:28CorujaNote Added: 0002261
02-06-14 12:34XuNNote Added: 0002262
02-06-14 21:45FeehNote Added: 0002264
07-06-14 09:12XuNStatusnew => resolved
07-06-14 09:12XuNFixed in Version => 0.56c Nightly
07-06-14 09:12XuNResolutionopen => fixed
07-06-14 09:12XuNAssigned To => XuN

Notes
(0002261)
Coruja   
31-05-14 23:28   
It's only occour on this weapon?
I dont use this script and I'm having the same problem here, many exceptions about attacks. It seems to be related to latest builds, I tested may 29 build here and in just 1 day I got 200mb logs files with tons of this 'attacker' errors (on my server, an log file size without problems is about ~800kb)

but let's wait for june 1 build and try again, maybe this problem got fixed with some updates
(0002262)
XuN   
02-06-14 12:34   
Still happening there? I had no errors.
(0002264)
Feeh   
02-06-14 21:45   
Also no errors here