[MUD-Dev] MUD Economy

Shawn Halpenny malachai at iname.com
Fri Jan 9 16:10:48 New Zealand Daylight Time 1998


On Thu, 8 Jan 1998, Adam Wiggins wrote:

> [Shawn Halpenny:]

[ ... ]

> > All vendors could start out quite stupid (i.e. not having any idea
> > whatsoever about what an object is worth):  e.g. trading 1 kg of
> > steel for 1 kg of flour.  Then, as the local demand for steel rises,
> > the vendor would learn that he was initially trading steel for _way_
> > too little and then raise his "price").  Now that price is what needs
> > to be determined.  It's easy to say "You can have that sword if you
> > give me three good milk cows", but where does the frame of reference
> > for the comparison come from?  What makes the sword worth three cows?
> 
> I tend to think it's important for the shopkeepers to have a clear view
> of what they are actually vending.  A few pawn shops/wandering merchants
> can spice things up, but we tended to orient our shopkeepers around
> actual crafts; they convert raw materials into sellable goods.  Thus,
> a shopkeeper knows he needs x lbs of steel in order to make a breastplate
> someone ordered.  If someone brings in steel in any form that he thinks
> he can use, he'll buy/trade for it.  By a similar token, if someone
> brings in a breastplate identical to one that they asked for and he feels
> that it is up to snuff as far as quality, he'll buy it, polish it up, and
> sell it to them, unless he has some sort of policy against selling
> things he didn't craft himself.

In a recent post I said that I'd decided to do the same sort of thing
in addition to the trade of existing items.  Look there for some
thoughts on obtaining that clear view of the item in question as well
(which is complicated when free user programming enters the picture).

> 
> > Perhaps vendors should keep track of what people have come in and
> > asked for but the vendor didn't have.  He doesn't even need to have
> 
> Well, for that matter, he should keep track of everything they ask
> for, regardless of whether he has it or not.

Of course.  I was distinguishing between the things he doesn't have in
stock but are in demand (which should prompt him to modify his trade
practices to procure some if the demand is persistent enough) and the
things he does (or can make, which amount to the same thing, since if he
made it, he is likely selling it in his shop--does not preclude him selling
it to another shopowner elsewhere, though) and can readily trade to other
characters.  I say characters here meaning players and NPCs since I fully
expect the more intelligent mobiles to take advantage of shops as well.

> > any idea that it exists, just that someone asked for it.  This
> > requires that characters be able to walk into a store and ask for an
> > item the shopkeeper doesn't have.  Then the shopkeeper can wait until
> > someone trades him that desired item, or find another method of
> > obtaining some (trade caravans come to mind, amongst other avenues of
> > obtaining goods).  
> 
> A method is needed, of course, to weed out things that they don't want
> to bother selling.  The blacksmith may say, 'Bah!  Why would I sell
> such a thing?' when someone asks for a beanie.

This makes perfect sense but I left it unstated.  I think this shopkeeper
would have to be aware of every item name in the world to know if characters
were requesting something that exists or not.

> This raises the question: could they change trades?  This is what you
> seem to be going for with your stuff, which is, I think, kind cool.

Certainly.  In that same recent post I gave a few simple rules that would
govern a shopkeeper's motivation and the conditions under which he would
perhaps change trades.  Additional rules could determine what sort of trade
he would try, where he would attempt it, etc.

> This depends a hell of a lot on how dynamic your world is.  If you create
> all the characters by hand (traditional builder style) then I would think
> probably not.  If you are going for a completely dynamic world (planting
> the seeds and pressing the GO button, as JC suggests) then I'd think that
> they would have to, in order for them to find their niche in the first
> place.  Maybe different merchants would have different levels of flexibilty
> with new lines of trade?  Ie you've got some that are ready to jump on any
> bandwagon they think will make them cash, others that love what they do
> and will never change, and everything inbetween, just like real life.

I anticipate the world being quite dynamic, but not so much that I just
drop the seeds, press GO and the whole machine chugs along.  I want to
design the very, very basic patterns so that things will run okay without
any tweaking and become more interesting the more extreme the conditions
(cf. the recent post's example of Bubba and the milk and cows).  So I guess
in a sense I'm seeding and then starting the whole thing.  I'm dreading,
though, doing all the stuff that will look behind-the-scenes to the casual
observer...

The thing is, vendors don't make any cash.  At the outset anyway, since I
haven't decided if money should be allowed to evolve (but with the trade of
user-programmed items, is there any way that money wouldn't evolve?).  So
in the case with no money, the shopkeeper has no incentive--he's just
following the rules set out by builders.  He neither cares if he does well
or not, nor even what he trades in.  This stuff could be mimicked, though,
for the benefit of observant players (e.g. Bubba's shop begins failing, his
wife leaves him and takes the kids, his dog dies, he contracts several
nasty diseases and jumps off a bridge).

As for vendor flexibility, it would devolve into writing the desired rules.
If a builder wants a shopkeeper who jumps at the smallest chance of doing
more business (perhaps that should be the metric of success if there is no
money?), he would simply write it that way.  As of yet, I'm not envisioning
a generic system for specifying these rules:  currently, everything would
still be done in the internal language (fine for me, but some builders
might like a more general way of specifying their shopkeeper's behavioral
patterns).

> > Given that, the above sword _could_ be worth three cows because ten
> > minutes before, someone came in and wanted some cows that the vendor
> > didn't have.  The question of what determines that the vendor _would_
> > trade like that still remains.  
> 
> Right.  Players could easily become merchants by making caravans between
> cities in order to buy something that is cheap in one location and sell
> it for a high price someplace it is sought after.  Entire games have
> been based on this - Tradewars was probably the first I played like
> this.

Precisely.

> > This entire economy would be trade-based.  User-created objects would
> > probably have to be untradeable to NPC vendors since the vendor would
> > have no way of gauging the object's utility (it would be too easy to
> > create a completely useless object that the vendor had never heard of
> > and thus get something for nothing).  Of course, if there was no
> 
> This depends how user-created objects work, exactly.  Are we talking
> about new classes of items (ie, different functionality) created by
> builders?  Or a more MOO-like environment where anyone can make anything
> they want?  Or are we talking about some sort of IC creation system
> whereby players can forge a sword with two hilts and six blades?

All objects have to be derived from another object.  Then the attributes
and methods can be changed as the user desires.  There is a cost associated
with this and the derived item will decay over time:  the more it differs
from its parent object, the faster it decays.  Currently, I'm oscillating
between decay forms:  the child object either gradually mutates back into
the same form as its parent (i.e. all attributes return to match those of
its parent and all new and overriden methods gradually disappear), and a
simple timer-based destruction--at time t+dt the thing vanishes.  Each has
its plusses, but I'm particularly attracted to the former because I think
it yields more observational fun:  Bubba with his very own carefully
crafted key to the bank vault, but as he walks to the bank he realizes that
it's turning back into the bag he created it from.

So, any of what you said above is possible.  The sword with two hilts and
six blades could be made and traded, but wouldn't last long once in use,
leading to a possible altercation between the vendor and the sod who
created it.

> It seems to me that all of these except for the completely open-ended
> MOO style thing (which probably wouldn't work anyhow in a system like
> this) would be fine.  If someone makes a new sword, the blacksmith takes
> a look at it and determines its worth based on how well crafted it is,
> what materials its made of, how well taken care of it is, etc.

The methodology behind that is what I'm wrestling with.  Without
user-programming, it's a matter of comparing attributes like what you list
above.  With user-programming, the sword could be made of papier-mache
but does something magical whenever it hits someone.  I can't conceive of a
way for a vendor to determine that without the builder/user who created it
saying so.

                                                                  Assuming
> you have a system this detailed (builders define quality, sharpness,
> method of grip, length, weighting, materials and so forth on new weapons
> they create) this should be no problem at all.  It works exactly the
> same way in a non-builder system such as Orion and I have been gravitating
> towards with our server; a weapon's value is defined by how it is used,
> how well it is made, how sharp it is, etc - regardless of whether these
> numbers were typed in by a builder or generated by the system when someone
> forged it.

Exactly.  Not a problem if those attributes are defined and available to
the vendor.  When people can create objects willy-nilly, one can't be sure
anymore even of the attributes.  That's partly why I think the vendors will
have to, on some level, rely on the fundamental object type:  "Look's like
this sword used to be a hotel bar fridge...what're you trying to pull
anyway?".  I'm not sure, though, that that alone will give sufficient
indication into what that sword is worth when compared to the three cows
Bubba wants to trade it for.

I don't want to have to force builders to determine anything directly
concerning the worth of an item.  That worth will be based on variables
specified, so a builder is indirectly specifying the worth, but I
absolutely abhor the thought of "I'll make this 2d6 sword worth
20000 gold...that should be good."

> > demand for that bogus object, the shopkeeper would have no reason to
> > trade for it.  However, a user could then determine what objects the
> > shopkeeper would trade for (i.e. someone had previously come in and
> > tried to trade for something the vendor didn't have) and then go
> > create an empty shell of that object and trade it in, again getting
> > something for nothing.  Another argument can be made, though, that
> 
> I see this as no different from RL.  You *could* try to trade a hollow
> sword, but as soon as the shopkeeper tested its weight he'd know it was
> a fake.  Obviously this gets tougher in a higher-tech world, but I
> still don't see any real problems.  Someone makes something which is supposed
> to be a computer but is actually an empty metal box.  As soon as the
> shopkeeper tries to boot it up, it does nothing, and he won't want to
> buy it from you.  Long story short is that shopkeepers need to test
> out objects given to them just as a player would.  Now, they can still
> be dupped - a player could learn the methods by which they test, and come
> up with something that would pass all the tests but still be a fake,
> resulting in profit for the player.  I have no problem with this.

I've come to agree...see the aforementioned recent post.  And given that
there is an expense in creating an object from another, the entire
definition of profit is not very clear--particularly if it's not money that
it costs to create.

[ more about junk items snipped ]

[ shopkeepers as distributors, vendors, and originators of items ]

> > Given that, is there a requirement for a planned initial distribution
> > of objects to vendors to seed the economy somewhat?  Each vendor
> > would have to at least start with one item, or he'd have nothing to
> > trade (and there's no incentive for a player to trade anything to the
> > vendor if the vendor has nothing or just gives away his object for
> > free).  Is more than one item necessary for each vendor?  The paths
> > of future trade caravans can be started at this stage simply be
> > putting all the flour in one vendor's shop and all the milk and eggs
> > in another.  As long as the object given to the vendor is somewhat
> > desirable by at least one player, would things take off from there? 
> > Or could things just be dumped haphazardly on vendors and the result
> > (a semi-functioning economy) be the same?  Perhaps each would yield
> > something sustainable and interesting.
> 
> An economy cannot sustain based on people just trading things around
> endlessly.  (Or, at least, it would be a fairly stale one.)  At
> some point someone has to produce something, and someone else has to
> consume something.  I think that everything you outline is great as long
> as you already have a system for production and consumption set up;
> your economy just becomes a method of distribution.

Quite true.  And I do have systems in mind, simple, but hopefully workable.
It's building them that takes the time.

--
Shawn Halpenny




More information about the MUD-Dev mailing list