SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002190SphereServernew feature requestpublic13-08-13 17:3030-04-14 11:45
ReporterXuN 
Assigned ToXuN 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version16-06-2013, 0.56b Prerelease 
Target VersionFixed in Version0.56c Nightly 
Nightly VersionAutomated (specify build number)
Experimental FlagsNone
Option FlagsNone
Internal Build Number1599
Summary0002190: Attacker. functionality
DescriptionIt would be nice if we have more control about attacker system, like making actual methods also writable instead of read only and adding a way to add/remove chars by script, if I want to remove just one player from the attacker list I just can't do it like either add them.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
13-08-13 17:30XuNNew Issue
14-04-14 11:34AvatarNote Added: 0002045
14-04-14 11:35AvatarNote Edited: 0002045bug_revision_view_page.php?bugnote_id=0002045#r605
14-04-14 11:36AvatarNote Edited: 0002045bug_revision_view_page.php?bugnote_id=0002045#r606
14-04-14 12:48AvatarNote Edited: 0002045bug_revision_view_page.php?bugnote_id=0002045#r607
14-04-14 17:25XuNNote Added: 0002049
15-04-14 08:07AvatarNote Added: 0002052
15-04-14 08:08AvatarAssigned To => XuN
15-04-14 08:08AvatarStatusnew => assigned
30-04-14 11:45XuNNote Added: 0002134
30-04-14 11:45XuNStatusassigned => resolved
30-04-14 11:45XuNFixed in Version => 0.56c Nightly
30-04-14 11:45XuNResolutionopen => fixed

Notes
(0002045)
Avatar   
14-04-14 11:34   
(edited on: 14-04-14 12:48)
Why dont you prevent attacking one from attacker list ?

For instance ,

for n 0 <eval <attacker> -1 > then list all attackers if you want with serv.list.attackers.add <attacker.<dlocal.n>.uid> then it becomes writable :)

So how can you prevent , put return 1 under on=@gethit to corresponding attacker.

or referance the attacker then stop his action.
(0002049)
XuN   
14-04-14 17:25   
Huh, old one request :P.

I took a look some time ago and was unable to do it, will have another look asap.

However, if you want to know ... the issue is not how to solve this ... I made exactly another system for attackers... but the default one should be flexible enough to do that simple things so no one needs to have 2 systems working (default and custom one).
(0002052)
Avatar   
15-04-14 08:07   
You are right. If it is okay with default one, no need to function it customly. It wont be efficient. So lets assign this to you then :D
(0002134)
XuN   
30-04-14 11:45   
Added it:
 -Added attacker.add uid / attacker.delete uid. Self explanatory
 -Changed: attacker.elapsed/dam are now writable