Guard (with no s) should NOT bring guards
Forum rules
Posts in this forum are expected to be constructive, realistic and civil. Inflamatory or off topic posts will be removed.
Posts in this forum are expected to be constructive, realistic and civil. Inflamatory or off topic posts will be removed.
Guard (with no s) should NOT bring guards
Also, hi buy should work (at least in early t2a). It works in the demo.
Re: Guard (with no s) should NOT bring guards
What do you mean guards should not bring guards?
Re: Guard (with no s) should NOT bring guards
He's saying if you say:
"Guard me" after being attacked in town, no guards will come to your aid.
You must say "guards" to bring guards. I.E. the S is important.
"Guard me" after being attacked in town, no guards will come to your aid.
You must say "guards" to bring guards. I.E. the S is important.
Re: Guard (with no s) should NOT bring guards
So guards will come if you literally just say the word "guard"?
Re: Guard (with no s) should NOT bring guards
I think fwerp is referring to this:
Saying "guard" is not enough, it must be "guards".
Code: Select all
on speech<"*guards*">(object speaker, string arg)
{
if(speaker == this)
{
return(0x01);
}
if(!isMurderer(this))
{
return(0x01);
}
if(!inJusticeRegion(getLocation(this)))
{
return(0x01);
}
callGuards(this, speaker, 0x03E8);
return(0x00);
}
+ORC: If you give a man a crack he'll be hungry again tomorrow, but if you teach him how to crack, he'll never be hungry again.
chumbucket: I don't collect pixels.
Never trust the client. It's in the hands of the enemy : UO Demo internals @ JoinUO
chumbucket: I don't collect pixels.
Never trust the client. It's in the hands of the enemy : UO Demo internals @ JoinUO
Re: Guard (with no s) should NOT bring guards
Aye, just tested, this is in error in comparison to the demo code.
However, the client keywords whenever introduced, sets 0x0007 to be *guard* and *guards*
At some point, *guard* was also allowed. Not sure when.
However, the client keywords whenever introduced, sets 0x0007 to be *guard* and *guards*
At some point, *guard* was also allowed. Not sure when.
Re: Guard (with no s) should NOT bring guards
Never thought to try just "guard". I was always under the assumption that only "guards" would work. 

Re: Guard (with no s) should NOT bring guards
Derrick, if the file you are referring to is "speech.mul", the patchlog file indicates this file was added with "Win32_UO_Gold Publish 60".However, the client keywords whenever introduced, sets 0x0007 to be *guard* and *guards*
That's UO:R, client 2.0.7 (gold_win32_2-0-7).
+ORC: If you give a man a crack he'll be hungry again tomorrow, but if you teach him how to crack, he'll never be hungry again.
chumbucket: I don't collect pixels.
Never trust the client. It's in the hands of the enemy : UO Demo internals @ JoinUO
chumbucket: I don't collect pixels.
Never trust the client. It's in the hands of the enemy : UO Demo internals @ JoinUO
Re: Guard (with no s) should NOT bring guards
Thanks. So the keyword localization was introduced during UO:R. It's probably safe to assume that *guard* and *guards* were equivalent at that time.
It's still unclear if they were equivalent before that time.
It's still unclear if they were equivalent before that time.