Area instances

ID:169033
 
Aug 2 2005, 11:08 pm
Can only one instance of a /area exist at one time?

For instance, if I have a /area/testarea with var "bob" set to "Hello!" can I have another /area/testarea with var "bob" set to "o_O"?

If you don't understand that, which I don't expect anyone but me to, then maybe this:

Can two areas of the same type (such as /area/testarea) have a common variable be a differant value? (Such as one have its "Numvar" variable set to 1, and another one have its "Numvar" variable set to 2; thus there would be two differant /area/testareas on the map)

I had just noticed that if I use GM_Edit on a certain /area whose layer var is set to 3 for something I was testing, all of the areas of the same time get edited at the same time. If this is supposed to happen, then it'll just take some extra coding to work around it, but I can live with it maybe. Not tonight though, as its 4 AM :( oh well.
Aug 2 2005, 11:25 pm
Correct, only one instance of any area is ever created.
Aug 3 2005, 12:40 am
Open the map editor and right click the area you need to edit. Then choose edit from the list. From the list of variables that show up, edit the variable to "Bob" or whatever you need it to be and then that particular instance will have been changed.
Aug 3 2005, 4:02 am
You most certanly can make multiple objects derived from type /area that all have the exact same subtype.
proc/new_areas()
    var/area
        A1; A2
    A1 = new; A2 = new
    var/turf/T = locate(1,1,1)
    A1.contents+=T
    T = locate(2,1,1)
    A2.contents+=T

You then have two objects of the exact same type of area on the map. At least, you can do it like this at runtime.

Doing it in the map editor, however, I'm not sure. You might be able to do that with the instance editor part of it. I don't get into that, so I can't help you there.
Aug 3 2005, 4:03 am
In response to YMIHere
YMIHere wrote:
Correct, only one instance of any area is ever created.

Only one instance if each area is created by default at startup. But you can certainly make more at runtime, so you should have avoided the word ever.