|
teion Wanderer
Joined: 03 May 2005 Posts: 72
|
Posted: Mon Feb 02, 2015 9:17 pm
creating room and zone scripts from command line |
I have observed that when I attempt to create a room or zone script from command line that another instance is made of the room or zone class that is separate from the map. The only way I have been able to create a room or a zone trigger is
1) right click the room or zone and edit zone script. This creates a new class under the map.
2) write the triggers on command line and save to a temporary class.
3) go to the temporary class and find the triggers and move to the class that was made by the mapper
I am not sure why somethig like #trigger {^You can't go that way} {#nomap;#nodir} Room3465
creates a new class that is not part of the map. |
|
|
|
shalimar GURU
Joined: 04 Aug 2002 Posts: 4691 Location: Pensacola, FL, USA
|
Posted: Tue Feb 03, 2015 5:37 pm |
Because you are putting Room3465 where the class value goes
I'm not sure if there is a way to make a room/zone setting via script.
I am thinking this is because maps themselves were not designed to be shared in the package library, but settings in general are..
Have you considered using the onRoomEnter or onZoneEnter #EVENTs to toggle classes in your package?
I think that would be the ideal method, since I think roomscripts and the like was a feature they were trying to phase out. |
|
_________________ Discord: Shalimarwildcat |
|
|
|
|
|