View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001794SphereServernew feature requestpublic11-08-10 07:5809-10-10 16:28
Reporterxantier 
Assigned ToShiryuX 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionno change required 
PlatformOSOS Version
Product Version0.56c Nightly 
Target VersionFixed in Version0.56c Nightly 
Summary0001794: Permared or Nondecaykills or something like that.
DescriptionI have learnt this thing today, permared flag.

In OSI 1999 patch, on each you become red, there is a variable "pingpong" is increased by 1. When this variable reaches 5, you become permared. Pingpong is never decreased, never. So you will be red forever, even you have 0 kill count. "Nondecaykills" or "Pingpong" can be added like "kills" or tag.noto.permared can be added like permagrey so we can script it by ourselves..
TagsNo tags attached.
Nightly VersionNot Available
Experimental FlagsNone
Option FlagsNone
Internal Build Number
Attached Files

- Relationships

-  Notes
(0000550)
xantier (reporter)
11-08-10 08:01

About that patch in 1999 :

A new long-term counter will be added that tracks murder counts. // this is already implemented in sphereserver as "kills"
This counter will go up when you are reported for murder, like the current murder count.
This counter will decay at the rate of 1 every 40 hours (the current counter goes down 1 every 8 hours).
While this counter is five or more, you will highlight red, and will be vulnerable to attack.
Stat loss will still depend on the standard murder counter.
Another new counter we term "pingpong" will be added. // permared
This counter increases each time you go red.
If this counter reaches five, you will be permanently red (meaning, you will be attackable. You will not suffer stat loss unless your murder count is also high).
This counter does not decay.
(0000552)
ShiryuX (developer)
11-08-10 14:12

I won't add one TAG for every color in the game. A way to override the Notoriety Flag should be the correct solution.
(0000553)
xantier (reporter)
11-08-10 14:34
edited on: 11-08-10 18:24

You are right, it can be really good solution.

Maybe a tag.noto=NOTO_(type) or a sphere.ini option to override the system..

(0000696)
ShiryuX (developer)
09-10-10 15:55

I guess this should be marked as fixed indirectly because of last update.
Good luck.
(0000697)
xantier (reporter)
09-10-10 16:27

Last update what?
(0000698)
ShiryuX (developer)
09-10-10 16:28

Last update in source, wait for next nightly.
Don't open the ticket again unless needed :)

- Issue History
Date Modified Username Field Change
11-08-10 07:58 xantier New Issue
11-08-10 07:58 xantier Nightly Version => Not Available
11-08-10 07:58 xantier Experimental Flags => None
11-08-10 07:58 xantier Option Flags => None
11-08-10 08:01 xantier Note Added: 0000550
11-08-10 14:12 ShiryuX Note Added: 0000552
11-08-10 14:34 xantier Note Added: 0000553
11-08-10 18:24 xantier Note Edited: 0000553
09-10-10 15:55 ShiryuX Note Added: 0000696
09-10-10 15:55 ShiryuX Status new => resolved
09-10-10 15:55 ShiryuX Fixed in Version => 0.56c Nightly
09-10-10 15:55 ShiryuX Resolution open => fixed
09-10-10 15:55 ShiryuX Assigned To => ShiryuX
09-10-10 16:27 xantier Note Added: 0000697
09-10-10 16:27 xantier Status resolved => feedback
09-10-10 16:27 xantier Resolution fixed => reopened
09-10-10 16:28 ShiryuX Note Added: 0000698
09-10-10 16:28 ShiryuX Status feedback => resolved
09-10-10 16:28 ShiryuX Resolution reopened => no change required


Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker