SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001637SphereServerexecutable - genericpublic19-07-09 19:3802-08-09 03:39
ReporterCoruja 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Nightly Version09-09-2008
Experimental FlagsNone
Option FlagsNone
Internal Build Number
Summary0001637: t_campfire and dispel
DescriptionType t_campfire can be dispelled with dispel/mass dispell
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
19-07-09 19:38CorujaNew Issue
19-07-09 19:38CorujaNightly Version => 09-09-2008
19-07-09 19:38CorujaExperimental Flags => None
19-07-09 19:38CorujaOption Flags => None
22-07-09 23:49babidiNote Added: 0000254
02-08-09 03:39MrSugarCubeStatusnew => closed
02-08-09 03:39MrSugarCubeNote Added: 0000258
02-08-09 03:39MrSugarCubeResolutionopen => no change required

Notes
(0000254)
babidi   
22-07-09 23:49   
i can confirm that.
dispel should not affect the t_campfire by default because of the absence of "SPELLFLAG_TARG_ITEM"

mass dispell affects.

you can fix it by script however

[TYPEDEF t_campfire]
ON=@Spelleffect
if ((<argn1>==41)|| <argn1>==54)) //41 dispel, 54 mass_dispel
    return 1
endif
(0000258)
MrSugarCube   
02-08-09 03:39   
This behaviour appears to be intentional. You should use the @Effect/@SpellEffect trigger (as above) if you want to override this.