[MUD-Dev] Introduction System

razor drbwana at tin.it
Fri Jul 14 09:44:04 New Zealand Standard Time 2000


From: Eli Stevens <wickedgrey at wickedgrey.com>
> Of course, if you can devise a system to do this without using a
true name,
> then this would not be a problem, but...  I don't really see any way
to do
> so (anyone care to enlighten?).  To me it seems elementary:
identifying
> something positively is impossible unless you have a unique
identifier.
> Unless you could devise a system that identified each player
uniquely both
> with respect to the identified player AND the identifying player (my
key for
> Buffy and Boffo's key for Buffy are different)...  Or would that put
you
> back where this question started: storing the info on the server...

I'm using a similar metod in my mud for gate-spell: befor opening the
gate they have to know the "magic tune number" for the destination
room (via "magic tune spell" cast in target room). This "magic number"
is calculated from the IDnumber of the room and the IDnumber of the PC
(the first is known by builders adn immortals for "goto", the second
is secret and known only by the 4 Big Guys) and a fake-random factor,
so "trading numbers" and reverse engineering isn't so easy if you use
bit operations, fake-random and a bit of the All-Mighty Black Magic
called "lies about guild-password generation algoritms" =).
This metod is used also for guild. Instead of having each subscription
saved in a different file for each guild, each pc has a different
password for each guild (the guild vnumber is known only to builders
and guildmaster, the pc ID is secret).

> <//> Silence golden           RUIN, v.  To destroy.            <\\>
>  ||  Eli                         Specifically, to destroy a maid's
||
>  ||  wickedgrey at wickedgrey.com   belief in the virtue of maids.
||
> <\\> www.wickedgrey.com            -- Ambrose Bierce
<//>

Very nice quote =)
PS: excuse me for my English, but I'm from Italy.
--
Razor [Chief of Darkmud: Breed of Darkness @ darkmud.gamersrevolt.com
4000]
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
http://www.kanga.nu/lists/listinfo/mud-dev



More information about the MUD-Dev mailing list