[MUD-Dev] data structure design in a new mud

[Kwon Ekstrom]

The choice between using a global list or not I guess would be a
matter of opinion.  A fair amount of my administration commands rely
on the global list, and I'm a big fan of centralized administration,
although I make good use of encapsulation and oop in my code, but
that's a whole different topic.

----- Original Message -----
From: <pauli.saksa at ztango.com>
>   possible attributes of a sword:
>
>   1. - name
>      - size
>      - building instructions
>      - battle attributes (damage etc.)
>
>   2. - quality     (calculated from used material
>                     and the skill of blacksmith, etc.)
>      - condition
>
> That first set of attributes is stored once in the memory and all
> items of that particular type use the same shared memory.  The second
> set of attributes is unique for all item instances and stored
> separately for each item.  So if I have several similar swords, they
> are all built from the same parts and named equally but their
> qualities and conditions may differ.  I see no cpu loss here.

I guess our systems are different enough for this confusion,
apparently your system has a certain static attributes that don't get
modified, and some that do, ie your quality and condition.

I'm still developing my system so I don't have all the details in yet,
but I'm aiming at a component based system where each item is made up
of smaller components that players can build or modify.  This allows
any statistic on the item to change over time, and definitely makes it
more difficult to track what's original and what's been changed.
Naturally I'll setup a general store of item components and a system
to generate items for in-game distribution.

-- Kwon Ekstrom

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