Guard (with no s) should NOT bring guards
Posted: Wed Jul 15, 2009 3:57 pm
Also, hi buy should work (at least in early t2a). It works in the demo.
UO Second Age
A forum for discussion of Second Age UO Shard
http://forums.uosecondage.com/
Guard (with no s) should NOT bring guards
Page 1 of 1
Re: Guard (with no s) should NOT bring guards
Posted: Wed Jul 15, 2009 4:02 pm
What do you mean guards should not bring guards?
Re: Guard (with no s) should NOT bring guards
Posted: Wed Jul 15, 2009 4:03 pm
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
Posted: Wed Jul 15, 2009 4:05 pm
So guards will come if you literally just say the word "guard"?
Re: Guard (with no s) should NOT bring guards
Posted: Wed Jul 15, 2009 5:36 pm
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);
}Re: Guard (with no s) should NOT bring guards
Posted: Wed Jul 15, 2009 10:29 pm
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
Posted: Wed Jul 15, 2009 10:48 pm
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
Posted: Thu Jul 16, 2009 2:16 pm
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).
Re: Guard (with no s) should NOT bring guards
Posted: Thu Jul 16, 2009 2:44 pm
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.