[MUD-Dev] Real Life Consequences

Kerem HADIMLI waster at iname.com
Mon Feb 19 22:02:09 CET 2001


the_logos at www.achaea.com wrote:
> 
> On Sun, 18 Feb 2001, Corey Crawford wrote:
> 
> > My question is, has anyone ever thought of - instead of banning,
> > deleting, shrubing, whatever'ing - fining a player for grievances
> > against the game?
> 
> > I'm talking charging real life money (via credit card, most likely)
> > because of rules broken.
> 
> If you're going to do it by credit card, then there is no need to do
> it at all. You just ban the troublemaker and ban his credit card. He
> might use another one, but most troublemakers are not the sorts to
> have multiple credit cards at their beck and call I find.

What about having a central player database (such as a
security-network for MUDs), and in order to play on MUDs that're
joined to this network, the user will have to sign-up with this
central database, enterin his credit card, etc, and if a MUD admin
decides someone needs global ban (ban from all muds in the network),
then he'll fill some form from web, explaining ban reason, etc, and if
the 'council' (for example 10 MUD admins, re-elected montly) accepts
the reason for ban, then the player (so the credit card) be banned
from the central player database, and so from all MUDs that're joined
to this security-network.

Geetting banned from one MUD (that uses credit card control) is no
problem if you have 10 credit cards, as you won't even play there 10
times if you want to abuse there, but getting banned from 150 MUDs
will be a problem when you have only 10 credit cards.

I think we should establish something like that, but the problem is:
1) will there be enough MUDs, so the p layers will trust to give their
credit card number, and 2) Will enough MUDs join at the beginning,
risking their player-database (such as, as there will be few MUDs at
the beginning, there will be less players that will want to give their
credit card info, and so that the MUDs will have less players).

Regards,
Kerem HADIMLI
--
If it happens once, it's a bug.
If it happens twice, it's a feature.
If it happens more than twice, it's a design philosophy.

_______________________________________________
MUD-Dev mailing list
MUD-Dev at kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev



More information about the mud-dev-archive mailing list