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

Update

.
Now it is obvious to see who has been frozen it is also clear that these freezes are pure guesswork.

The players I know 100% to be using scripts daily for a very long time have not been frozen, which shows they cannot detect the scripts.

So its possible some have been done due to having multi's, some for long playing hours, but none have actually been detected using the scripts that are floating around.

Its scaremongering to try and stop players using scripts and friends of mods who are jealous of other players xp gains complaining.

Boils down to crap mods, which has always been Syrnias downfall.

Cheating Suspects

Word has come to me of people being temp frozen for being suspected of cheating.

If they had any sort of proof then players would just be frozen.  As they do not have the proof, they have temp frozen players to give them a chance to explain their xp gains or whatever.  What they are actually doing is giving players a chance to put their foot in their mouth by conversing with them.

Its the same tactics the police use when they arrest someone on suspicion of something, get them in an interview room and the more they say, the more likely they are to implicate themselves.

So this is just a fishing trip to try and get people to admit to something they have no proof of, or to get the player to mail them and hopefully slip up with some excuse that does not add up.

Notice how none of SYRAIDS friends are part of this group.  Even cheats said Krazydude was getting more xp than them, it was reported and nothing done.  The excuse of 'he plays a lot on his phone' was the accepted answer, yet others who do this are frozen.

Also remember that Lestro abused the OL bug with PvP.  No punishment whatsoever.  Evert also cheated, no punishment.

Then we have RuboxJr who was shown to be using banned scripts with screenshot proof, no punishment and he is still a moderator.

So remember that this is just SYRAID trying to get rid of players who outgain his poor clannies in xp, while he lets some members of his clan and mod team continue to cheat.

Syrnia mods have always been a joke, run by megalomaniacs who just want to punish for every small pathetic thing they can.  It is surprising that M2H has allowed it to go on for so long.

Also remember that there are programs similar to iMacros (https://addons.mozilla.org/en-US/firefox/addon/imacros-for-firefox/) that you can use to do many tasks in Syrnia and it will work as if a real person has done it.