Runes of Magic US / AU

Dude that's new style right there see all the weed on the ground. They are changing the Zone to "Ron Paul 2012"

I haven't played in a couple months, patched up, logged on and thats what my game looks like too. uninstalled whole client and am in process of redownloading all 9 gigs and repatching. lame that you have to run through a bunch of patches right on a clean install. read a dev post somewhere that it was from a corrupted patching, so trying it

Quoted from "lj781;567327"

corrupt patch....does this game not check the MD5 before applying a patch? wow.....

MD5 is indeed checked before patching - you can see it happening if you look quickly enough.

The RoM patch process seems very prone to being mistaken as virus activity by most anti-virus softwares too & if the anti-virus blocks the patch from operating correctly, it is usually the textures that show it. So, disable your anti-virus during patching & you won't experience this error.

Quoted from "Inferiority;567329"

MD5 is indeed checked before patching - you can see it happening if you look quickly enough.

The RoM patch process seems very prone to being mistaken as virus activity by most anti-virus softwares too & if the anti-virus blocks the patch from operating correctly, it is usually the textures that show it. So, disable your anti-virus during patching & you won't experience this error.

It would be easier to do that if the patch process didn't start automatically. I go to load RoM, and some days it decides to do a patch.

And frankly, disabling AV is not a good answer; RoM needs a robust patch process, i.e. test with AV software before releasing the patch.

While they are at it, they should probably test on heavily loaded computers. I know the game itself leaks memory, and perhaps other resources, then eventually crashes; I suspect due to dereferencing NULL pointers. My best guess is that the game updater has the same type of bug - not so much leaking resources, as misbehaving (corrupting the installation) when it doesn't get the resources it wants.

Why does the game feel the need to accept incoming network connections? Windows firewall just blocked it from trying, and warned me. But the truth is, if I recall correctly, I've already got that blocked at my main firewall, which filters packets based on the destination - and drops all connection attempts to insecure operating systems such as windows. (Only my *nix machines are allowed to appear as servers on the net.)

Responses in Boldface

Quoted from "kobnach;567384"

It would be easier to do that if the patch process didn't start automatically. I go to load RoM, and some days it decides to do a patch.

When you start the launcher, the first thing it does is check it's own revision level against the server's revision level. If the server is at a higher revision level, the launcher subroutine goes out to find, download, and install the next most recent patch. Patches are on a secure server. The check is run again and if another patch is found, the process is repeated. When the revision levels match, the launcher is ready to go.


And frankly, disabling AV is not a good answer; RoM needs a robust patch process, i.e. test with AV software before releasing the patch.

Some a/v programs are over-aggressive and, in some ways, a tad bit out of date. Most, if not all of the uncompressed RoM patch files include a dollar sign ($) in their filenames. Some of those "overaggressive" a/v programs will see that character and either delete the file without notification, notify the user that an infected file has been found and recommend that it be deleted or quarantined, or move it to a "quarantine" folder automatically with or without notification. Frogster has contacted most or all of the noted a/v companies whose products do this in an attempt to get them to "back off" a bit, but with no real success.

I have, in the past, recommended to people that they can temporarily disable or turn off their a/v program in order to install RoM or update the RoM game client, so long as they re-enable the a/v program afterwards. This can be done entirely safely. The other option for them is to find an a/v program that doesn't throw out "false positive" notifications. The problem with doing that is that they may have paid for a subscription to their current a/v program, and changing programs would cause them to waste that money.


While they are at it, they should probably test on heavily loaded computers. I know the game itself leaks memory, and perhaps other resources, then eventually crashes; I suspect due to dereferencing NULL pointers. My best guess is that the game updater has the same type of bug - not so much leaking resources, as misbehaving (corrupting the installation) when it doesn't get the resources it wants.

Again, the issue is with over-aggressive a/v programs, not with the launcher and updater.

Quoted from "kobnach;567385"

Why does the game feel the need to accept incoming network connections? Windows firewall just blocked it from trying, and warned me. But the truth is, if I recall correctly, I've already got that blocked at my main firewall, which filters packets based on the destination - and drops all connection attempts to insecure operating systems such as windows. (Only my *nix machines are allowed to appear as servers on the net.)

If the game cannot communicate with the game servers because your firewall has blocked the communication path, or because you've told it to do so, then you won't be able to play the game. It is as simple as that.

I've been playing RoM for more than three years, using Windows XP, Vista, and Windows 7, all with the standard Windows Firewall. At no time, and let me repeat, at no time, has Windows Firewall ever blocked incoming traffic from the RoM login or game servers, nor has it ever "warned" me or made any sort of query regarding incoming network traffic from the login or game servers. For both Vista and Windows 7, User Account Control has been at the default which Microsoft sets for it, straight "out of the box". I have never altered that setting.

Quoted from "Kalvan;567401"

If the game cannot communicate with the game servers because your firewall has blocked the communication path, or because you've told it to do so, then you won't be able to play the game. It is as simple as that.

I've been playing RoM for more than three years, using Windows XP, Vista, and Windows 7, all with the standard Windows Firewall. At no time, and let me repeat, at no time, has Windows Firewall ever blocked incoming traffic from the RoM login or game servers, nor has it ever "warned" me or made any sort of query regarding incoming network traffic from the login or game servers. For both Vista and Windows 7, User Account Control has been at the default which Microsoft sets for it, straight "out of the box". I have never altered that setting.

I don't understand anything developed or sold by microsoft ;-) But I'm running 64 bit vista, and I got firewall warnings for both the game download program and the game itself, in the past few days. It is however possible that my employer's IT department has managed to mess with my firewall settings - they like to impose extra "security" on anything which might ever contain any of their data, and I use that box to connect to work over a vpn connection.

Other than that, I've never had a problem with the game until my (apparent) bad patch, and given that the same patch apparently reinstalled OK after I downloaded the chapter 5 client, _without_ changing any anti-virus settings, I'm finding this explanation hard to believe. If my AV was seeing bogus viruses on Monday, it would most likely see the same bogus viruses on Thursday, short of a coincident update to the AV definitions that reduced false positives.

The game is working fine since the redownload, except that I lost a lot of configuration. (I didn't dare overwrite the old installation, and I don't know what to copy to preserve either game or add-on configuration. (I did copy all my add-ons; that part was easy.)