- Refinement of the IP/Name logger would be a start (it is capable of having a bit more functionality, specifically involving a cross check between logged IP's and logged names - I can elaborate more if you need me to). This would be the most effective way in reducing the number of smurfs, and you can also limit the abilities that a certain player has if their IP/Name has never been logged or registered in the server before. I could keep going.
- You can make any vote on a player still work after they have dropped, and also after they have dropped and then reconnected to the server. If they drop, and change their IP, you will have to rely on a more ambiguous statistical approach to handling them. I have explained at the bottom of this post.
- Duplicate IP's are already being checked in every Annihilation server (have you ever seen a "send in the clones!!" message? that means that there is a duplicate IP connecting to the server). Anyway, you can run through all of the player IP's in the server once a new connection is attempted, and if any of those IP's that you ran through are the same as the one that is trying to connect, you can disallow that new connection from being made. This will in turn will disallow duplicate IP's on your server.
My Statistical Approach to Manipulating Server Trends
- You can log 99% of the things that occur in your server. The more data that you log, the more data that you have for recognizing server trends. Trolling, spamming, vote abusing, admin abusing, bking, pitchforking teammates; all of these trends have specific data associated with them that can be logged from the server. Once you start seeing the trends in your data, you can begin telling your server to recognize those same trends and how it should act accordingly. This is the same method that I suggested to use in selecting the missions for your server's map rotation; collect the data, find the maps that have a trend of players voting for them, or not, and then use that data as the guideline for how you will set up your map rotation. This method can be applied to just about any problem in the game. If your problem is more ambiguous, like some player with an unknown IP connecting to the server for the first time, you would still be referencing data from that pool of logged data; the pool of data about players who connected with an unknown IP and also the pool of data related to their activities. It is a process of gathering data, finding the trend, and then telling your server how to handle it in the future.
Vote Droppers Beware! (CROW)
Re: Vote Droppers Beware! (CROW)
One thing that sucked about that IP check in Annihilation is the you get one vote per IP rather than per player. My bro used to come over a lot and play and we were only able to cast a single vote.
[NHOP]Virus
Re: Vote Droppers Beware! (CROW)
good lol^
<--Click here to subscribe to S_hift's youtube
Click here for full access to all my tribes downloads
Click here for full access to all my tribes downloads
Re: Vote Droppers Beware! (CROW)
anthrax and virus are good guys tho
Re: Vote Droppers Beware! (CROW)
Thanks r.justR wrote:anthrax and virus are good guys tho
[NHOP]Virus
Re: Vote Droppers Beware! (CROW)
I'll probably add it.DaJ4ck3L wrote:Ghost wrote:Crow why u ignore disI'll think about it.virus wrote:This needs a poll. This could work against a lot of people if a prick voted on you for no reason.
Be careful.
Been working on other stuff really, and I have a few things going on behind the scenes that about to come to light. No need to be in such a rush.
- {SW}SkyWalker
- Posts: 664
- Joined: Wed Feb 05, 2014 2:46 pm
Re: Vote Droppers Beware! (CROW)
Good i hope u add this because idiots shouldn't avoid justice. Like not showing up to court.
No matter how long I stay away from this game I will never forget the stuff this game and community forged onto my heart!