Feedback talk:Game updates/20200930

Hello,

Since installing this update, I cannot make any version of texmod/umod to work.

I have heard other peaople experiencing the same.

If anyone has since or in the future could figure out a solution and please share, that would be much appreciated.

Thnak you in advance!

Zes (talk) 13:20, 1 October 2020 (UTC)

I've run into this issue (or a similar one) before. For me, it's the game relaunching itself rather because it detects it was started in the wrong location. If the location you're running it from does not match the original install location, and there is another copy of the game installed there as well, Guild Wars will exit and re-launch the executable in the location that the registry thinks it should be in, and in the process removes umod/texmod's injected textures. Best advice I can give would be to check your registry, or re-install GW from GwSetup.exe rather than copying it. horrible | contribs 23:37, 1 October 2020 (UTC)

Did this update also disable the "-password" command line argument? Mine isn't working anymore. --RoyHarmon (talk) 18:11, 5 October 2020 (UTC)

I've read of some people having similar issues - you may still have to use the -character flag with a valid character name when logging in that way. My shortcuts from before the patch (with -email, -password, and -character) are unchanged and still seem to work. horrible | contribs 18:37, 5 October 2020 (UTC)

Yep, that did it. Thanks! I had just been using -password because the "Remember my account name and character name" checkbox was checked, so I didn't think about it. I tried adding just the -email argument and it didn't work, but once I added the -character too, it's good. Weird, though... It doesn't seem consistent with their goal of removing the need to enter a character name. --RoyHarmon (talk) 06:12, 6 October 2020 (UTC)