-MPRHB- Development proceeds...

External Since: Jan 27, 2008 Posts: 31

On 30 Jan, 17:23, Jeff Lait <torespondisfut... DeleteThis @hotmail.com> wrote:
> 3) Confusing data with code.

In HASAD (my previous, discontinued RL) I used huge strings to
represent map elements such as rooms, houses and continents (on the
world map). In addition to this I had lists of coordinates to add
towns, people, treasure, etc. I don't recommend this approach.

OTOH, in TSL (the successor) I still use hard-coded monsters, items
and encounter tables; I haven't seen any reason to move it to data
files. In fact, I see several reasons to keep it this way.

I'm considering changing the way items are generated, though; I now
have a huge switch statement (for item number), that sets item
parameters. Would it be better to create a large array that kept a
copy of each item? Then I could just duplicate them and run some
"custom code" on certain item types (wands would need random charges,
for example).

I see several advantages, the most attractive that I could call an
item by name (wands of wishing here we come!) as well as item number.

-the ru

External Since: Nov 29, 2007 Posts: 75

On Jan 31, 7:27 pm, Jeff Lait <torespondisfut... RemoveThis @hotmail.com> wrote:
> I think there is a lot of good to be said of having your secondary
> "languages" compile into your primary language. It certainly makes
> the whole question of setting up bindings rather trivial :>

Certainly.
Did you write the lexer/parser for your configuration/data language
yourself or used some tools like flex and bison/bison++?