Full Version : Talking Trash Barrel
xmlspawner >>Troubleshooting >>Talking Trash Barrel
<< Prev | Next >>
Haazen- 05-25-2006
We are very new with XMLSpawner so are starting out easy.
We placed a trash barrel in the vendor mall.
Used XMLEdit and set the following parameters.
EntryNumber =10
Text = Welcome to Vendor mall, {GETONTRIGMOB,name}!
DependsOn =-1
The greating works well. The problem is after a player recieves the greeting, and then open the journal in the client, the client crashes. After relog on, there is no greeting entry in the journal.
What have I not set, or what other parameter must I set to gt this to work? This worries me because I can see most XMLSpawner projects having thse same parameters set. So if I am not setting correctly, I am going to have continuous client crashes.
ArteGordon- 05-25-2006

QUOTE (Haazen @ May 25, 2006 01:49 pm)
We are very new with XMLSpawner so are starting out easy. We placed a trash barrel in the vendor mall. Used XMLEdit and set the following parameters. EntryNumber =10 Text = Welcome to Vendor mall, {GETONTRIGMOB,name}!
DependsOn =-1
The greating works well. The problem is after a player recieves the greeting, and then open the journal in the client, the client crashes. After relog on, there is no greeting entry in the journal.
What have I not set, or what other parameter must I set to gt this to work? This worries me because I can see most XMLSpawner projects having thse same parameters set. So if I am not setting correctly, I am going to have continuous client crashes.

This happens with all players?
There is nothing specifically about the text generated by xmldialogs that would cause client crashes (they are just standard public overhead messages).
Generally those journal crashes are a result of certain problem strings sent to the client, such as long player names.
My guess is that it has something to do with their names or possibly the name of the item you are attaching it to.
(edit)
other things to check are the client versions. What are they using and what version is the server patched to?
(edit)
you might also check the Hue value. An invalid hue (like a really large value) could cause a client crash. If you left it at the default of -1 then it would just use the standard default text hue.
But this would happen immediately upon generating the text, and not just when opening the journal, so it is probably not related to your problem.
Haazen- 05-25-2006

QUOTE (ArteGordon @ May 25, 2006 06:57 pm)

QUOTE (Haazen @ May 25, 2006 01:49 pm)
We are very new with XMLSpawner so are starting out easy. We placed a trash barrel in the vendor mall. Used XMLEdit and set the following parameters. EntryNumber =10 Text = Welcome to Vendor mall, {GETONTRIGMOB,name}!
DependsOn =-1
The greating works well. The problem is after a player recieves the greeting, and then open the journal in the client, the client crashes. After relog on, there is no greeting entry in the journal.
What have I not set, or what other parameter must I set to gt this to work? This worries me because I can see most XMLSpawner projects having thse same parameters set. So if I am not setting correctly, I am going to have continuous client crashes.

This happens with all players?
There is nothing specifically about the text generated by xmldialogs that would cause client crashes (they are just standard public overhead messages).
Generally those journal crashes are a result of certain problem strings sent to the client, such as long player names.
My guess is that it has something to do with their names or possibly the name of the item you are attaching it to.
(edit)
other things to check are the client versions. What are they using and what version is the server patched to?
(edit)
you might also check the Hue value. An invalid hue (like a really large value) could cause a client crash. If you left it at the default of -1 then it would just use the standard default text hue.
It was happening to everyone. I am patched to 5.0.2b and so is my GM. It did not happen to me to start with because I was in admin mode. I switched to Plaer mode and it happened as soon as I recieved the message and then clicked Journal.
We deleted the TrashBarrel so no crashed today.
Thx for your quick response Arte. You are one of the few people I will believe without question for support. Off subject: Everytime I post on RunUO, I hope it is you that answers. :}
I will do more tests on this issue and see if I can find a link.
ArteGordon- 05-25-2006
I would check the name of the barrel and see if that is the problem.
I just tested the exact text that you used, and there was no problem, and I am also using 5.0.2b
Haazen- 05-25-2006

QUOTE (ArteGordon @ May 25, 2006 07:50 pm)
I would check the name of the barrel and see if that is the problem. I just tested the exact text that you used, and there was no problem, and I am also using 5.0.2b

Yes the name was the problem. The name was changed to
Put your unwanted stuff here!
Thanks for your help.
ArteGordon- 05-25-2006

QUOTE (Haazen @ May 25, 2006 03:16 pm)

QUOTE (ArteGordon @ May 25, 2006 07:50 pm)
I would check the name of the barrel and see if that is the problem. I just tested the exact text that you used, and there was no problem, and I am also using 5.0.2b

Yes the name was the problem. The name was changed to
Put your unwanted stuff here!
Thanks for your help.
so what was the problem name? It was probably just too long. The client seems to have trouble with displaying long names in the journal.
Haazen- 05-25-2006
Name = "Put your unwanted stuff here!"
That was the name exactly.
FWI We also had Text Hue set to 217. Not sure if the hue in this case added to the problem. The text hue did not cause crash before we changed the name.
ArteGordon- 05-26-2006

QUOTE (Haazen @ May 25, 2006 03:44 pm)
Name = "Put your unwanted stuff here!" That was the name exactly. FWI We also had Text Hue set to 217. Not sure if the hue in this case added to the problem. The text hue did not cause crash before we changed the name.

an invalid hue would be something above 37K or so. I can try to find out the exact value and put in a check to prevent setting it that high.