Or just reset all kills to 0 once t-mode starts. Or restrict out-of-t same-ip t-mode to very late time period like 5 to 7am or something. Zach On 4/14/06, James Cameron <quozl at us.netrek.org> wrote: > The following patch is for discussion. It changes the t-mode scumming > check by preventing t-mode from beginning at all if there are players > present from the same IP address. Once the duplication is resolved > t-mode begins. > > It is implemented as a state machine. The state variable is: > > static enum ts { > TS_PICKUP, > TS_SCUMMERS, > TS_BEGIN, > TS_TOURNAMENT, > TS_END > } ts = TS_PICKUP; > > Alternate ideas I've been playing with ... > > - exclude the duplicate IP players from the total per team, such that > with four clients on Federation from the same IP, they'd need another > three ships before Federation would be considered to have quorum, > > - make CHECKSCUM a maximum number of duplicates allowed, so that > legitimate players from the same IP are permitted, > > - if every slot is guest, don't care, allow t-mode. > > (The intention is to hinder the social "problem" of players feeding > their character kills while waiting for other players to arrive. > Distortion of t-mode statistics. It's not that I care about the > statistics, it's that people perceive the problem.) > > -- > James Cameron mailto:quozl at us.netrek.org http://quozl.netrek.org/ > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQFEP5uubmRwv64kZsARAtFjAJ44fB7c376f5GmlTS6SBbS98t6T0wCdFcAO > pq+LAyPNq39x4hkuUuK2l9o= > =AVQL > -----END PGP SIGNATURE----- > > > _______________________________________________ > netrek-dev mailing list > netrek-dev at us.netrek.org > http://mailman.us.netrek.org/listinfo/netrek-dev > > > >