Difference between revisions of "MovingRoom"

From CoffeeMud Wiki
Jump to navigation Jump to search
(Created page with "{{BehaviorTemplate|Name=MovingRoom|Targets=Rooms|Usage=min=3 max=3 chance=100;"xmlsection";"ticks at stops";"ticks between stops"|Examples=min=3 max=3 chance=100;SUBWAY;3;10|D...")
 
Line 9: Line 9:
 
3.  You -cannot- have the moving room override an exit, ie. if room A links south to Room B you cannot have the mover link north to room A.
 
3.  You -cannot- have the moving room override an exit, ie. if room A links south to Room B you cannot have the mover link north to room A.
  
*******************
 
  
XML DOCUMENT NOTES:  
+
XML DOCUMENT NOTES:  
 
 
*******************
 
  
 
You can use the following strings in the XML document to be translated on the fly  
 
You can use the following strings in the XML document to be translated on the fly  
Line 69: Line 66:
 
===Notes===
 
===Notes===
 
.
 
.
 +
[[Category:ROOMS(BuilderInfo)]]

Revision as of 14:22, 29 October 2017

CoffeeMUD
Administrator                                                  Builder                                                              Player
=CoffeeMUD Builder Information=
Basics Praetor     Player Support     Commands     Zapper Masks Advanced Races     Classes     Abilities     Socials     Scripting    
Building Behaviors     Properties     Areas     Rooms     Exits     Items     Mobs Systems Achievements     Crafting     Help Info     Ships     Planes of Existence     Quests     Triumphs    
===MovingRoom===
Targets: Rooms
Parameters: min=3 max=3 chance=100;"xmlsection";"ticks at stops";"ticks between stops"
Examples: min=3 max=3 chance=100;SUBWAY;3;10
Description: The above example would set the room's parameters to the ones listed in the SUBWAY section of the file resources/moving.xml. There is a subway example already there.

NOTE! : The follow conditions -must- be met before setting the room to this behaviour.

1. The rooms that you want this room to open out to -must- already be defined before you make the XML section.

2. The XML document -must- be writen before you set this behaviour.

3. You -cannot- have the moving room override an exit, ie. if room A links south to Room B you cannot have the mover link north to room A.


XML DOCUMENT NOTES: 

You can use the following strings in the XML document to be translated on the fly

$disproom : if mover is at a stop this is the room it is opened to otherwise

. Example : this is the next room that this room will open too.

$inopendir : this is the direction the door on the inside (the mover) opens.

$outopendir: this is the direction the door on the outside (where the mover stoped) opens.

$traveldir : this is the current direction that the room is moving in.


(STOPS) here you would list the ROOMID of each room the mover will stop at example.

(STOP1)(first stop)(/STOP1)n

(NORMALDIRECTION) and (REVERSEDIRECTION)

-in these tags you define the parameters for the mover while is is going back and forth.

-normal is stop1 to stopwhatever and reverse is stopwhatever to stop1.

-TRAVELDIRECTION = the direction it is traveling from point a to point b.

-DOORSDIRECTION = the direction the doors open out of the mover.

--(INSIDE) and (OUTSIDE)

---in these tags you define what is echoed to the client in the mover and outside.

---ARRIVALINFO = what is echoed when the room gets to the stop

---DEPARTINFO = what is echoed when the room leaves the stop

(ROOMDESCRIPTIONS)

-here you define what is appended to the end of the room descriptions.

-(NORMALDIRECTION) and (REVERSEDIRECTION)

--(INSIDE) and (OUTSIDE)

---DOOROPENED = if the door is opened append this.

---DOORCLOSED = if the door is closed append this.

There are two examples in the XML document you can look at for further info.

Ideas for this would be, subways, busses, wagon trains (caravans) spaceships, stargates, everchanging paths in mazes, elevators, ect.

Notes

.