Greasemonkey Script Overhaul (new battle order script)
•
by Buck Roger
Greasemonkey scripts rely on pattern-matching to determine which pages might possibly be re-written using a script within the addon's arsenal.
Recently, eRepublik released a "cluster" architecture for improved server performance. The impact on scripts and their users is that the URL may now be either "www" or "www2."
I maintain the "eGR_BattleOrders translated" Greasemonkey script, which shows the eGreek battle orders on the home page of the user in their native language, using Google translate.
Following the lead of its antecedent, the eGR_BattleOrders script, I have updated my derivative script to a version 0.2.1 that accomodates the new www2 subdomain. In another change mimicking the parent script, it now has a link to the Greasemonkey script page, where you can click through to find any future versions (without, however, any notification that you should do so... at this time). Unlike the parent, it also supports the five other languages (Spanish, Portuguese, French, German, and Russian).
In the next version, I will most likely generalize the subdomain part of the pattern matching, so that any subdomain is acceptable. I recommend this route also to any other script authors, or to any users of scripts who want to do a very easy "hack" (skill level: able to use Notepad.exe) to fix their scripts to keep working.
Just right click the Monkey in the lower right of the browser, "Manage User Scripts..." and find your script (click on it). Then click on each entry for "Included Pages" and where it says "http://www.erepublik.com/blah" replace it with "http://*.erepublik.com/blah" through use of the "Edit..." button. Done.
Please install the new eGR_BattleOrders translated if you prefer reading a language other than Greek (usually, English) and want the eGreece battle orders on your eRepublik home page.
Bug reports, suggestions, ideas for this or other scripts, and scraps of Q1 Food are gratefully accepted.
Facebook
Twitter
Discord
Comments
voted
v
Voted
Voted!
Buck, I disagree with something 😉
erepublik.com/" target="_blank">http://*.erepublik.com/ means everything on this site, like http://api.erepublik.com/" target="_blank">http://api.erepublik.com/ or others I don't know, or haven't come up yet. So erepublik.com/" target="_blank">http://ww*.erepublik.com/ would be a better approach, it covers every wwwX subdomain and the plain www. I doubt they will ever change the server naming any more than wwwX, there is no need to!
That would work at this time. Of course, nobody really knows whether they will keep any format for the URL, so forward-looking statements must be qualified.
However, there's nothing wrong with the pattern I suggested.
(1) Users don't visit "api.erepublik.com" so it doesn't matter even if they did have matches to the pattern.
(2) The "blah" portion (in this case, "en" or "es" and so on) is part of the directory structure of the www* subdomains. Other subdomains would not have matches unless they started (and, in this case, ended) with that.
voted
Yeah, you've got a point with the subdirectories 😉
It's just some scripts apply to the whole site (.com/😉 but they are a few. So, there is no perfect solution...
voted
Buck Rogers...Will you ever publish the Media Mogul Project or do you want me to give it to another citizen????
It would be great if it was you who is publishing it, cause you have a lot of subs😛