Full Version : Moving Indiana Jones boulder
xmlspawner >>Q&A >>Moving Indiana Jones boulder
<< Prev | Next >>
Xerrox- 09-20-2006
Dont use the screenshot for the complete entries since they can be truncated. Use the posted XML. The complete entry that tests for collision is

QUOTE
OBJ=IF/GETONTRIGMOB,x=GETONSPAWN,1,x &amp; GETONTRIGMOB,y=GETONSPAWN,1,y/33:MX=1:SB=2:RT=0:TO=0:KL=0:RK=0:CA=1:DN=-1:DX=-1:SP=1:PR=-1

which in plain text is
IF/GETONTRIGMOB,x=GETONSPAWN,1,x & GETONTRIGMOB,y=GETONSPAWN,1,y/33
Allmight- 09-20-2006
Hmmm, seems like the following is missing two colons...

CODE
static,4952:MX=1:SB=1:RT=1:0:TO=0:KL=0RK=0:DN=-1:OX=-1SP=1:PR=-1

You are missing a colon before the RK=0, and SP=1. Think it should be...

CODE
static,4952:MX=1:SB=1:RT=1:0:TO=0:KL=0:RK=0:DN=-1:OX=-1:SP=1:PR=-1

That might explain why you get the ": property not found" error
Allmight- 09-20-2006
Compare that line to the line Arte posted above

CODE
static,4952:MX=1:SB=1:RT=0:TO=0:KL=0:RK=0:CA=0:DN=-1:DX=-1:SP=1:PR=-1:

Then i notice an etxra :0: in the middle of the line.
So either you have a cut and past glitch, or if you typed it manually, you have missed a few characters.
ArteGordon- 09-20-2006
the complaint about basepriority is because you dont have the latest version of xmlspawner that added support for that new property.
It will still work, but the animation is going to be very slow (1 tile per second).
also, if you are getting this message
Xmlspawner:invalid type specification: static,4952:MX=1:SB=1:RT=1:0:TO=0:KL=0RK=0:DN=-1:OX=-1SP=1:PR=-1
then you must have entered this entire string into the entry
"static,4952:MX=1:SB=1:RT=1:0:TO=0:KL=0RK=0:DN=-1:OX=-1SP=1:PR=-1"
instead of just
"static,4952"
and this
"IF/GETONSPAWN,1,>2362/22"
should be this
"IF/GETONSPAWN,1,x>2362/22"
you are just testing the value of x on the spawned boulder (static,4952), and seeing if it is greater than 2362, which is just an x value that I chose to be the end of the boulder's path.
Xerrox- 09-20-2006
THANK YOU THANK YOU THANK YOU
Ohh my god it works.
though i am using DAMAGE,200,100,0,0,0,0 instead of KILL the KILL dosent work. Guess the server as you also said with the basepriority, havent been updated properly.
Now to wait for a sever update and see what will happen with the update
But thanks once more for all the help
ArteGordon- 09-20-2006
yeah, must be running an older version. KILL was added in v3.15, basepriority in 3.16