[HLM]

these numbers? it also requires division multiplication and subtraction, just the basic functions

[fysiks]

Sounds like it's time to rethink your point system.

[Emp`]

Originally Posted by Seta00 It's not that simple... Floats aren't an option

Why not?

[HLM]

Originally Posted by fysiks Sounds like it's time to rethink your point system.

rethink it? why? its not one of those "keep adding to the top" systems, its a bit more unbalanced than that, basically (if I plan on removing it from the current plugin its embedded in) it has two real functions, it will need to add +1 and divide the number by 2, all users start out with 50 points, when that user kills another user, he recieve (amt/2)+1 of the victims points, I add the +1 for in the event that the victims points is 0, I have also set it so that the points cant fall below 0, rather it will stay at 0 until he gets more points. if I do plan on further developing this, I will probably make some sort of algorithm so that you are capped on how many points you can recieve from killing someone (so some random new person cant come in and kill steal and get X billion points), probably basing it off of current points or something.. but I think its pretty simple, and I tried enforcing a max points, but people dont like that, and I do understand that the problem is coming from the +1 problem, it is creating more points in the system, and I could also probably help decrease these large numbers by lowering these starting points from 50 to probably 10, also, bots are not saved in the system, rather when the points are loaded for the map start, they are assigned a random amount of points (30 to 70 I think) which probably causes more points to be taken, I could probably just remove those, but for people that are stuck playing with several bots and end up having only 12 health after encountering a bot and get a one hit kill from a human player, thus it would seem unfair. I think those are things I COULD change, but I dont know yet.

TL/DR: I know of a few things, but im not going to "reinvent" the system

[Seta00]

Originally Posted by Emp` Why not?

My bad, I thought AMXx implemented fixed-point rational numbers support...
Well, here's your answer then, HLM. (Unless you need to store numbers bigger than 10^308 )

[fysiks]

Originally Posted by Seta00 My bad, I thought AMXx implemented fixed-point rational numbers support... Well, here's your answer then, HLM. (Unless you need to store numbers bigger than 10^308 )

I believe that is for 64-bit floats. For 32-bit floats is's about 10³⁸

Originally Posted by HLM rethink it? why?

Without rethinking the points system you will run into the same issue again and again.

Originally Posted by HLM its not one of those "keep adding to the top" systems

Basically, yes it is. Otherwise you wouldn't have this issue.

Originally Posted by HLM and I do understand that the problem is coming from the +1 problem, it is creating more points in the system

The +1 has very little to do with your problem. One point is insignificant when you give 25± points (50/2) for a kill. From what I understand, a person that kills a player with 1,000,000 points will himself get 500,000. This is why points are "blowing up". It's almost exponential!

Originally Posted by HLM (so some random new person cant come in and kill steal and get X billion points)

This is essentially what your plugin is designed to do!

One thing that you could do to prevent the "blowing up" is reset everybody's points on a regular basis.

[Bugsy]

I think you should add some type of cap on kill-points and\or let a user obtain (amt/10) points instead of (amt/2); or you can make the divide number variable based on his rank or w\e. You definitely need to be a bit more conservative on issuing points because you will continue to run out of storage-space (like the problem you have now), especially if you are never resetting stats.

[HLM]

yeah, I am planning on doing something based on rank (which will be given after reaching X points) and hopefully that way, there is less "blowing up" and maybe I'll make it so that when you do go up a rank, it resets your points, therefore, you can have several different brackets of top (top dominator, top over-achiever, top #rank3 etc.)

thanks for the input, I guess im going to develop this further

EDIT: if you guys can think of anything else I should do with this, im open to suggestions.

[Bugsy]

Originally Posted by HLM yeah, I am planning on doing something based on rank (which will be given after reaching X points) and hopefully that way, there is less "blowing up" and maybe I'll make it so that when you do go up a rank, it resets your points, therefore, you can have several different brackets of top (top dominator, top over-achiever, top #rank3 etc.) thanks for the input, I guess im going to develop this further EDIT: if you guys can think of anything else I should do with this, im open to suggestions.

I would both reduce point distribution as well as use your idea where you reset a players points with each new rank.

Example:

Player reaches 100,000 points
- move him to next rank
- set points to 0

Player again reaches 100,000 points
- move to next rank
- set points to 0

repeat.

[HLM]

bugsy, I have a question for you, if I convert iMin and iMax and adjust the public function accordingly, is your short script set up for float usage?