Highlighted Section of Rules of Conduct?

In the Guild Wars Rules of Conduct why is #9 highlighted in orange?

It says:

Is this just a coding issue or are they trying to tell us something? If so, what?

Rules of conduct are a joke they ban you while you done nothing and then support hides behind the words you broke rules of conduct

If you were banned, it was for a reason.


@OP, what it's aiming to do is highlight to people that you AREN'T allowed to modify the client with dll injections and such, which is the main reason they did the 3700 bans.

seems pretty straight forward to me, no reason to read between the lines......just.......read THE lines

That they do not like people using xss attacks on their sites, attempting to hack servers and of course, modifying client. They really do not enjoy that at all.

Basically just "bad people, stay away from our game, mmkay?".

tl;dr version: Don't hax our any of our services, pl0x lol thx bai.

Highlighted parts are either parts added or modified later that differ from the original compilation of the rules. They're highlighted for you to better notice the updates in the RoC.

I see. That makes sense.

Not that I'm using it, but does TexMod count?

Gill nailed it, it shows a modification or change which may or may not be recent. 23 has the word "bot" highlighted the same way.

The page also has "Updated 8 October 2009" not too sure how accurate that date is...

Textmod does not count however be careful where you get it from some versions may be tainted.

Lololobai

According to the rules, it does. According to Gaile/Regina it doesn't. Hey, ambigiousness is how they role. Keep your rules as vague as possible, and pick out random exceptions, and you can ban anyone for anything.

Honestly I can't be the only one who tired of this from you. They have been clear from the start, yes it is against the EULA, but they will not do anything about it as long as its only replacing textures and not doing other things (dll injecting, botting, doing your homework).

Because that makes sense. Anything that is ambiguous in the EULA is not that way because they like banning people (that makes absolutely no sense). It's that no one can write a perfect document stating what you can and can't do.

No it doesn't. It doesn't modify the client or servers in any way; it simply modifies the the interpretation of the data on the client side.

Soooo... no.

Gill is right about this. We highlight the text each time the Rules are updated to draw attention to the stuff that's been changed. It's easier for people than trying to compare the versions

The injection doesn't modify the client either. It solely reads packets (In no way different than we "read" the screen, and replies certain packets with interrupts.

They clearly hint at any form of modification of your "Guild Wars experience". Anything that didn't came with the original package falls under this category.

And the fact that they (Gaile or Regina, forgot who) did specifically had to mention Texmod was OK, clearly shows it would've fallen under the not-allowed category.

He asked what the highlighted parts were, I replied with the honest anwser that they were modifications to the old EULA which solely make it more ambigious, or atleast not more clear in the least bit.

In regards to TexMod and other such things...

If you have to ask, don't. Is it seriously worth getting banned over? In my opinion... No it doesn't. So, why risk it?

And, yeah. Highlighted parts are there either to signify importance or to signify changes.

That should be move to #1, or maybe #2.

And this is why it's bannable:

Seems clear enough to me. This also explains why apparently harmless stuff like PaketFakor triggered the detector. Even if PaketFakor is no cheat program, it's still a hack.

Also, it is bannable for this:

Read both the EULA and the RoC better, as the vague parts are indeed really minimal, unless you want to play the fool.

What else do you need?

I found the following statement from Arena Net customer service: http://www.guildwarsguru.com/forum/e...t10439627.html