Guide to modifying in-game graphics/Texmod
- This article is about how to use Texmod. For how to create Texmod projects, see /Creating Mods. For GWW's database of player-made modifications, see /Player made modifications.
|Warning: Directly modifying the Guild Wars program files through any third party tools is completely unsupported by ArenaNet and NCSoft. If anything breaks, do not contact support for help; there's nothing they can do about it. Also, third party programs not supported by ArenaNet might contain trojans, spyware, adware, and other harmful programs. See also: ANet's official stance.|
This is a guide on how to modify (mod) Guild Wars through a program called Texmod.
TexMod can be downloaded here.
To be sure that your copy of this software is safe, verify one of the following checksums.
File MD5 SHA1 Zipped 2291f3095f14efb847d366e2fbe4be51 c05a59ef20c5cb682230de2be9973945562ab86d Unzipped Texmod.exe 3a561b80cfba394a810d528d4c05dc7e 6da72f02cb63e04210d590213073ec677bdd20fd
- Online tech-tips provides a basic overview of checksums.
- You can download a simple utility from CNet or upload a file here to calculate the checksum. Various anti-viral programs (e.g. AVG) also provide checksums automatically on files on their exception lists or that are tagged as potential threats.
(This information is copied from the Readme.txt file inside the Texmod download.)
| TexMod Beta Version
TexMod is a utility to find, save and modify Direct3D textures in DirectX 9 or greater(!) applications. In order to share and distribute texture modifications, packages can be created, which are both compressed and prevent a further modification. Benefits are that you don't have to modify any files of your application's installation and you don't need any game specific modding tools.
The application interface offers three modes:
Please note: This is an early beta version and does not offer application specific fixes. Don't be surprised if your application crashes or shows other strange behavior and expect a slight performance drop, especially when you use the logging features.
Definition file syntax
The definition file, which contains a checksum and a path to a texture file has to look like this:
<checksum>|<texture file path>
If the checksum is in hex format, it has to start with 0x, e.g. 0x00ABCDEF. The file path can be absolute or relative to the definition file.
Controls in logging mode
All controls are located on your numpad.
Running a mod
- First, you will need a .tpf file, which is a file containing all the edited textures. These can be downloaded on many Guild Wars fansites, as well as the Wiki's own database of mods located here
- Once you have your mod and Texmod downloaded, unzip and run TexMod.exe.
- Click the big folder icon in the Target Application section and select Browse.
- Find your GuildWars folder and select your Gw.exe (usually located within "C:\Program Files").
- Switch to Package Mode (should be default).
- In the Select package section press the small folder icon and find the .tpf file(s) you want to use and select it.
- Once all the mods you wish to run are in the list, press Run and the game will launch. Enjoy.
Creating a mod
- Open TexMod.
- Click the big folder icon on the Target Application section and select Browse.
- Find your GuildWars folder and select your gw.exe.
- Switch to Logging Mode.
- Select the options you want. I would advise you to keep "Show Texture on the upper left corner" and "Replace Texture (with a green texture)" on.
- Press Run.
- Keep pressing "+"(Numpad) until you find the texture you want (Notice the selected texture becomes green) and press the "Log with" key to export it.
- Edit the image all you want but leave the dimensions and name of the image alone, as well as the .log file as Texmod will use this later to build the package.
- Go back to TexMod and press the "Package Build" button.
- In the Definition File browse to the Output folder and select the TexMod.log file that accompanied your edited texture.
- Enter your name and some comments (e.g. what you changed).
- Press Build. A new window will open up and ask you to specify a name and a place to save it. Give it a name and press save.
- Are mods permanent?
- No. Any modifications must be run through TexMod every time, and no changes are made to any Guild Wars files.
- How can I remove a mod?
- Run Guild Wars normally.
- Can I create new models / new UI elements?
- No. Texmod only supports modification of existing textures, and can not access model data.
- Can other people see my mods?
- If they have the same mod active, then yes. Otherwise, no, only you will be able to see the changes.
- Where can I find mods other people have created?
- A list of player-made modifications can be found here.
Requirements and options
- What version of DirectX is required?
- Texmod currently requires at least DirectX 9 (or higher) to run. In particular, DirectX 10 and 11 are ok.
- Can I use Guild Wars command line switches with TexMod? (such as "-password" or "-noshaders")
- TexMod does not yet support command line switches.
- What are some common troubleshooting tips?
- Check you security software: Add Texmod to your anti-virus/security software's allowed or exceptions list (or disable it temporarily for testing).
- Ensure you have the most recent version of Guild Wars: Run gw.exe with the "-image" argument (without TexMod running).
- Replace your mods/software: Re-download Texmod and/or the mods you wish to use (don't forget to confirm the checksum; see above)
- I downloaded an armor/weapon reskin, why isn't it working?
- Many armor/weapon reskins only work if the item is a specific color to start with.
- I get a strange error message, with the text "D'OH". What does it mean?
- This is a general error message used for nearly all exceptions - as TexMod is beta software, error handling isn't up to par.
- However some known instances where this error may occur are:
- * After being browsed to, gw.exe can no longer be found in that location.
- * One or more of the selected .tpf files can no longer be found or are corrupted and cannot be run.
- * A virus scanner has blocked TexMod's access to the gw.exe file. If you are using a virus scanner or other malware protection software, it could be detecting TexMod as a threat (see below). Turn your virus scanner off, then use TexMod. Once Guild Wars starts, you should turn your virus scanner back on.
- * Try running TexMod as an administrator, especially for Windows Vista or Windows 7.
- My anti-virus/anti-malware software claims that Texmod has a trojan in it. Is this true?
- If your anti-virus/anti-malware program uses heuristic detection, a program's ability to modify the way another program works, it might detect TexMod as a trojan. These scanners cannot tell good modifications from bad ones. TexMod is obviously a false alarm, since the basis of it is to modify how a program runs by replacing textures that the program uses. To verify that you have a valid copy of TexMod, compare the checksum of your downloaded zip file or texmod.exe with the known good checksums (see top of page).
- I followed all the directions, have DirectX 9 installed, and nothing changes. Why?
- Texmod requires a graphics card that is fully DirectX 9 compatible in order to work. Older graphics cards do not have the ability to fully use DirectX 9. This means that some programs that require it may not function properly, including Texmod. In addition, if a new Guild Wars.exe build comes out, it will restart Guild Wars, which means that Texmod will no longer be modifying the game. If this occurs, simply close Guild Wars and re-run it via Texmod.
- TexMod used to work. Now it doesn't. Was there an update? Did an update to Guild Wars cause it to stop working?
- TexMod has not been updated in several years; you almost certainly have the latest version.
- There is very, very little chance that an update to Guild Wars will cause TexMod to stop working.
- The most common reasons that TexMod might suddenly stop working are:
- You changed anti-virus software or a recent (usually automatic) update to the software requires that you tell it that TexMod is okay.
- TexMod points to an outdated version of Guild Wars; update gw.exe to the latest version.
- Without realizing, you moved files around on the computer and TexMod cannot find them. There are many ways to resolve this; the simplest is to reinstall TexMod and/or the mods.
- While rare, it is possible that updating the Guild Wars client while TexMod is running can cause TexMod to stop working properly. A possible fix is to run Guild Wars with the -repair argument. If problems persist, try using the -image argument.
The following quotes are from ArenaNet staff:
As a general rule of thumb, we don't mind if you do things like this to make your own playing experience more fun. Some people really like to mod, and we recognize that this can often be a valuable learning tool. When you're doing it, though, keep in mind that we ask that you don't use our content to mod other games. Please do not attempt to extract anything from your GW.dat with the intent to use it in a mod for another game or project. Also keep in mind that we can't support any changes you make.
In other words, if you try to make some changes and your game crashes, don't contact support because there really isn't anything they will be able to do for you. Make sure you have your disks handy to reinstall.
In case anyone was concerned about this reply, keep in mind that alterations that people make to their own .dat files will not affect the play experience of others. All of that important data is stored server side, so any changes that would be able to be made are purely cosmetic. For instance, if someone re-textures their sword to look like a gigantic pickle, they will be the only one to see this change. You won't start seeing people wielding pickle swords running around in random arena any time soon.
Also keep in mind that we are always interested to see what stuff you guys come up with. If you do something exceptionally cool that you feel would really benefit the community as a whole, don't be afraid to let us know about it.
To all modders: It's important to note that the parameters concerning the use of third-party programs do still apply. We cannot condone the use of such programs, and we cannot support the accounts of those who may be negatively impacted in using such programs. That's called the "If it eats your hard drive and blows up your refrigerator, don't call us" policy.
Honestly, though, as previously stated, it is unlikely that we would actively pursue or action those who use such programs in a positive manner, that is, those whose only interest is creating benign mods of our games. Keep in mind that occasionally people get creative and might bring up the use of a harmless program to attempt to mask other harmful activities. We see that with other situations, such as where they say "But I was only using an alternative OS, why was I blocked?" and we discover they are using major bot programs.
If you feel that this creates a "mixed message," then I guess we should discuss that concern. I can understand where the strict "Don't do that" is clearer than "We can't say you can do that, but we won't take action if you do choose to do it." There are some cases where it's not black and white. One example that comes to mind is the use of emulators to play Guild Wars. We develop only for the PC, but others play on other systems and that's totally ok. However, if they develop difficulties, our Support Team is not available to help them resolve those issues. So we don't prohibit the alternative, we simply decline to support it.
What I want to say above all about this matter is that if you're going to mod, have fun, but do stick with the benign and positive uses of the programs and create mods that impact the game only in ways that are fun and harmless. If there's more information to share, I will do so as soon as it becomes available to me.