Forum

Login to ZARP

View BBCode Back »

EdenB wrote:

RedPowder wrote:

What? Caps and Large font are to different things and I didn't think that was hard to understand. Caps locks just means all the letters are uppercase the rule states it needs to be a large font. So this would be wrong and this would be right.

Caps locks and Large font the same thing......

I thought large font meant the size to be 100.
the rule confused me , and thats why i thought "BUilDINg" does not count as building sign, yet admins can understand my confusionElla wrote:

RedPowder wrote:

Umm what?

If it says "Building" on the sign it's a building sign if it says any thing else it's not. I'm not to sure how hard it is for you to define between the two but it seems simple enough for an average person. We currently have to literally spell out every aspect of how to raid because you guys can't differ what's wrong or right.

Ok this was brought up because of what happened with the guy on server 2. In my opinion the rules just needs to be stated better. What happened was that this guy spelt his sign "Building" and said he could print because the rule says "Building signs need to be in LARGE font and need to be spelt "BUILDING" , Which classifies as the sign needing to be like this "BUILDING" in all caps or in "large" print as stated in the rules. He is saying that because he didn't put it in all caps or large print he can print because the rules say it must be in LARGE print. So i totally agree with him,but he was warned for printing with a building sign, which is technically a false warn and should be removed. In my opinion the rules is fine just needs to be worded better so this doesn't become a big problem.

well. even if your english isnt the best, you will still get warned because some things are not obvious as they think they are

Again... LARGE not capitalized even if he wrote building in all lower case letters but was large enough to see it still works out.

BBCode

[quote="EdenB" post=213541][quote="RedPowder" post=213530]What? Caps and Large font are to different things and I didn't think that was hard to understand. Caps locks just means all the letters are uppercase the rule states it needs to be a large font.  So [size=1]this[/size] would be wrong and [size=4]this[/size] would be right.

Caps locks and Large font the same thing......[/quote]
I thought large font meant the size to be 100.
the rule confused me , and thats why i thought "BUilDINg" does not count as  building sign, yet admins can understand my confusion
[quote="Ella" post=213529][quote="RedPowder" post=213525]Umm what?

If it says "Building" on the sign it's a building sign if it says any thing else it's not. I'm not to sure how hard it is for you to define between the two but it seems simple enough for an average person. We currently have to literally spell out every aspect of how to raid because you guys can't differ what's wrong or right.[/quote]

Ok this was brought up because of what happened with the guy  on server 2. In my opinion the rules just needs to be stated better. What happened was that this guy spelt his sign "Building" and said he could print because the rule says "Building signs need to be in [b]LARGE[/b] font and need to be spelt "BUILDING" , Which classifies as the sign needing to be like this "BUILDING" in all caps or in "large" print as stated in the rules. He is saying that because he didn't put it in all caps or large print he can print because the rules say it must be in LARGE print. So i totally agree with him,but he was warned for printing with a building sign, which is technically a false warn and should be removed. In my opinion the rules is fine just needs to be worded better  so this doesn't become a big problem.[/quote]
well. even if your english isnt the best, you will still get warned because some things are not obvious as they think they are[/quote]

Again... LARGE not capitalized even if he wrote building in all lower case letters but was large enough to see it still works out.

Forum

[SSRP Suggestion] "BUILDING" sign rules

Time to create page: 0.068 seconds