Maybe its time to release a little detail

The "first" people identified (you can probably guess who they are) as using "this kind of thing" went to the trouble of creating a cheating script and allowing it into the public domain, one of the reasons why this is so serious as you can hopefully appreciate is that it then tempts others into similar offending.

Everyone knows Syraid froze those players as they interfered with Ponds outlands mining, so that excuse is a little thin.

Now the real information is that Syraid knew that I had seen the cheats (although not used them) and that his silly freezings of my account over mod grudges (for pointing out all their mistakes) would lead to me making the scripts available to everyone.

So the scripts and cheats are in the public domain because of Syraid.  If he was not on such a power trip then nearly all the cheating players would not have them.

Syraid makes the wrong decision everytime, be it over my account, not punishing PvP and his friend Lestro for the OL cheating, allowing cheaters back in as some were popular figures, etc. The Syrnia modding system will always be a farce while he is in charge. Him throwing M2H's name about to try and add authority to his posts is just laughable and most see straight through it.

Deleted thread

.
The deleted thread they did not want you to see.  One comment was slyly deleted and not in the screenshot relating to me being correct about mods all along.  Mods cannot handle the truth.

Cheaters back and disinformation

.
So the cheaters are back, probably due to some of them having high profile friends.  Mods could not bring friends and popular people back without also bringing the others back.

This brings the message its ok to cheat but if the mods have a grudge against you, you will get frozen longer for just not agreeing with them.

[2] 13:05 (Mod)SYRAID[Pond]: cant see that The Guy.. as we can now identify such use.. a multi logged in last night using it (for the first time) and was immediately banned

This is simply disinformation to scare others from cheating. Players are currently logged in using cheats and they are not frozen.  They may be able to detect one kind of cheat which next to nobody uses, due to a little error in the cheat.  This is easily fixed and I may supply the source code and a modified version without the obvious flaw if I can be bothered.

They probably simply spotted a multi.

If they could detect most of the cheats, they would not have had to enter into communication with players to try and get them to admit how long they cheated for and then roll back their XP to that date.  They would have frozen them for a certain time and automatically rolled back their xp to when they detected them cheating.  But as they cannot detect the cheats they could not do this.

Word on the street is that they rolled back xp for those players to the xp they had in February, which shows they cannot detect the scripts or know how long players have cheated for.  So a player who has cheated for years only loses a few months xp.

A cheater who went to the mods and admitted cheating 6 months ago before mods were aware of any cheats was frozen for good.  Also a friend of his was frozen as they simply suspected him of cheating and remains frozen.  The difference is these players could interfere with the top clans mining in the outlands and had caused Syraids miners problems in the past.

So you have to ask, why these players were not unfrozen after 2 weeks yet the ones in high profile clans that also have mods in them were.  The other unanswered question is why some of Syraids clan mates were never frozen in the first place...

For the doubters

02-08-2009 Mod saying ALL scripts are not allowed

29-09-2009 Anasco island update released 2 months later

Screenshot of Ruboxjr using scripts after Anasco island update so months after the mods banned scripts. Its is obvious from the clan chat and players at the town who it is.  Ruboxjr has admitted it in the past too.  He was also a moderator when he broke the rule.

The punishment was so small that if he told anyone there would be major complaints.  What this has done is shown that its ok to use banned scripts and you can become/stay a mod.  Start cheating and get your mod status now!

Mods wonder why they have no credibility?  They will make up some kind of excuse as to why a fellow mod would not be frozen for breaking the same rule others have been frozen for....

P.S: MadameMasque, your attempts at discrediting me are making you look stupid ;)

Auto-eat safely

.

There is no code in Syrnia web pages that can detect greasemonkey and the auto eat scripts.  This has now been confirmed.  Any coder would be able to verify this by looking at the pages Syrnia sends to your browser.  As said before, even if the code was there it would still not be possible to know what the script done exactly. Needing mod tools to check players out also shows there is no such code to detect the scripts. If a tool has to be used it would only be to look at logs to try and find patterns, so its back to guessing and accusing and then hoping for a player to admit it.

If someone was caught using an auto-eat script, it was due to them making a mistake somewhere or players messaging cheat mods complaining about their xp gains and further investigation of the logs of that particular player.  Or they could have bragged about it/pasted something in whispers.  My own guess is that some players did not change the food ID to their own when they first installed it so a mod tool which searched for anyone trying to eat the food ID in the original script (every food ID is unique to every player) would be easy.  This makes the most sense as to how some were caught and not others.

This new version of the auto eat script is as basic as it gets.  It uses the exact same code in Syrnia pages and nothing else.  The eating the script does is identical to if you had had clicked the food yourself.  Removed the popup box and the help chat posting. It is completely undetectable. Even if they try to add code to detect it at a later date.

Read the description of the script to understand about the timing of eating too as leaving it very low would be suspicious, even if it would take a lot of painstaking log reading for admins to spot. If someone was caught for  using a script for auto trying even chest combination, they probably did not add any pauses between tries, which would be obvious if all the logs were looked at too.

If you are fighting in the outlands then change the auto-eat script to check every one or two seconds, but remember to change it back after.

Happy auto eating!

Low health alarm

Instead of auto-eating when you lose HP, this script will launch a website that plays a sound to alert you that you may soon die.

This is all done on your own computer without it talking to the Syrnia server, so Syrnia admins and mods can not  see what this script performs.  Some may feel safer with this than one that auto-eats and actually interacts with the Syrnia server.

Description: https://userscripts.org/scripts/show/105694
Source code: https://userscripts.org/scripts/review/105694
List of scripts for different HP amounts: https://userscripts.org/users/354300

Greasemonkey needs to be installed for these to work.

What can be detected and what can not

As of Greasemonkey 0.6.4, however, user scripts now have their own JavaScript context and execute completely separately from the content document. This means that except by noticing changes the changes which they make to the DOM, content scripts can neither detect Greasemonkey scripts, nor interfere with them.

Sometimes, you will want to access the global variables in the content document. For example, maybe the content document defines a function which you want to call. In these cases, you can access the content document's global scope with the unsafeWindow variable. Just be aware that accessing the members of this variable means that content scripts can detect your script and potentially interfere with it if they choose.

Source: http://greasemonkey.mozdev.org/authoring.html

Greasemonkey is becoming more common on casual users computers these days as there are scripts which help you do so many things on so many sites or display things better.  One script for example reformats the BBC news page to look better, another turns non-clickable links on a page into clickable links.  So if a site can detect greasemonkey installed (which greasemonkey developers go out of their way to make it hard) and that a script is active on their page, that in itself is no proof that you are doing something you shouldn't be.  Same if you have iMacros installed, it is a legitmate program used by millions for many tasks.

Some scripts do need to call functions, so although its not straight forward, it does appears it is now possible to detect if a greasemoneky script is being used, depending on what it does and if it changes to the DOM. It is not trivial to do this though.

However.... the above type detection cannot tell you exactly what the script does, which would explain the lack of outright freezings and the way mods are trying to get players to confess.   Harmless scripts that do not help you cheat would show up the same if they access these functions or change certain things.  Other harmless scripts do not use these functions so would not be detectable.  A script that reads your health from the server and displays it in another frame, say closer to where you are reading chat, should not show any different from a script that reads your health for auto-eating purposes.

So to make the detection, code would have been added syrnia server/pages to look for access to the variable. This means that anyone who used scripts in the past but does not now, would not be flagged. This may explain why some high level fighters who I know 100% to have used auto eat scripts have not been frozen, as they are at levels where they wouldn't need to use them anymore at many locations.  So the long term users who got most gains from these kind of scripts have gotten away with it.

In one case, a mod in the multi/chat department was fully aware of a friend cheating (yes I have the proof but have chosen not share it) but obviously did nothing to in order to protect them. Makes you wonder how many mods friends have been protected ;)

I am sure someone is looking at ways of disabling any extra code added to syrnia pages for detection (if there actually is any) or looking at running a local proxy on their machine to stop any attempts at detection.  Google chrome the equivalent of greasemonkey built in, so most scripts would work in chrome without greasemonkey installed.  Some may need a little tweaking to work though.

It is also possible these players did something silly, like running out of food and an auto-eating script still tried to eat.

RULE: 5. 2. User scripts (for example, greasemonkey) are not permitted in Syrnia regardless of their function.

Players would feel its unfair if current mods were caught breaking this rule without being frozen or punished...oh wait don't forget mod RuboxJr being caught red handed!  MadamMasque can try and lay attention elsewhere and call people liars, but the proof was there. Unfortunately you can not fix stupid  :)

window.addEventListener