Post: #11

ic, so why even have roomdefs then?

Post: #12

(06-26-2013 09:38 PM)Mordaunt Wrote:  It's really simple I don't know why people have so much trouble with this.
Just change the Roomdef to Areadef and add your event....
You're still going to affect the same region, you're just changing it's type.

Trouble?
When you are in a ROOM, when you say .where it says You are in "Room Name" in "City Name".
When you are in an AREA, it says "Area Name"

When you make an area, you need to set the same FLAGS of the city area.
So you make area inside another area with the same flags, just to put events...

So, yes, roomdef should have events properties of course.

Okay if you don't to make it, its just my opinion and I think it without events is useless.

Post: #13

Well.. making it is nothing to do with me, I'm not a dev, I'm just here to clean up the forums e.t.c...
Though I believe that Ben has expressed the opinion previously that rooms don't need to have events.
As for why have roomdefs... I don't know that either, though I imagine suddenly removing them would cause a few complaints from people.

You can't please all the people all the time unfortunately

Post: #14

extreme, basically what mordaunt is saying, is that roomdefs are kinda pointless, as they can be defined as areadefs all the same, and areadefs can have events where-as room defs cannot, for reasons only Ben can tell us atm

so see if you need an event for a roomdef, u can easily just change that roomdef to an areadef and then place your events as needed.

although like extreme has stated room defs give you different information than aredefs do when you use .where, so thats the only convenience i can assign to a roomdef atm.

maybe Ben will come clear this up for us

Post: #15

You can write a really simple script to fix the .where command (I know it's a workaround and people don't like it but still)

<region.region.name> will give the name of the region which contains the region you are standing in.

Post: #16

I don't have an answer other then the different info given by the .where function.
I never even realised that roomdefs gave out different info.
To me, they are useless.

Post: #17

roger that

Post: #18

The main problem IS NOT what .where shows.

The problem is:
- as AREA you need to set FLAGS, so you need set it in every AREA you create even it is INSIDE a city.
- so, if you change the city flags, you need to change all 'small areas' inside the city.
- rooms are just 'areas' that assign the flags of the main area.

Example:
City 1 - Flags: guarded
[ROOM] Tailor Shop - Flags: City 1 flags = guarded

Then you change the city flags to: unguarded, then tailor shop will be automatically unguarded.

But
City 1 - Flags: guarded
[AREA] Tailor Shop - Flags: guarded (you NEED set it)

Then you change the city flags to: unguarded, the tailor shop still guarded.

Then think about change ALL shops in the city if you change the flags of the city.

Did you understand my point?
I think its the most clear that I can explain.

So here is my request:
ROOM accepts events, just that, so it can follow the flags of area and receive events =D

Post: #19

ahh ok, I was unaware that rooms inherit their parent region's flags... interesting, and not something i ever gave much thought to

Post: #20

need to add something to this

mordaunt you said <region.region.name> will show the parent regions name, however it does not, nor can tags set on parent regions be accessed in this way. is there another way?