Cross-Platform Modding: Difference between revisions
Jump to navigation
Jump to search
Dr. Kylstien (talk | contribs) Not sure what happened to this, but I re-added a note on beta-testing. |
Dr. Kylstien (talk | contribs) added list of hard-coded filenames. |
||
| Line 3: | Line 3: | ||
==Checklist== | ==Checklist== | ||
#'''Is my mod in a file that users of other operating systems can open?''' (No self-extracting files or installer programs. zip, rar, and 7z files are good.) | #'''Is my mod in a file that users of other operating systems can open?''' (No self-extracting files or installer programs. zip, rar, and 7z files are good.) | ||
#'''Did I type all the filenames with the same case as the actual files and directories?''' All Unix-like operating systems (Unix, Linux, BSD, Mac OS X) are case-sensitive. This means that MyMod.con, MYMOD.CON and mymod.con are all different files. Make sure you type the paths exactly as they appear, or EDuke32 will not find them. It is recommended (and standard practice on these systems) to always use lowercase file and directory names so that there is not confusion. | #'''Did I type all the filenames with the same case as the actual files and directories?''' All Unix-like operating systems (Unix, Linux, BSD, Mac OS X) are case-sensitive. This means that MyMod.con, MYMOD.CON and mymod.con are all different files. Make sure you type the paths exactly as they appear, or EDuke32 will not find them. It is recommended (and standard practice on these systems) to always use lowercase file and directory names so that there is not confusion. The case of some filenames are hard-coded in EDuke32 and must be typed as follows: | ||
##EDUKE.CON | |||
##GAME.CON | |||
##duke3d.def | |||
##duke3d.grp | |||
##tiles###.art | |||
#'''Can my mod play nicely with other mods and existing EDuke32 installs?''' Operating systems like Linux keep their programs, data, and configuration in separate locations and will have only one copy of EDuke32 and a standard directory to load mods from. Therefore, well-behaved mods will keep their files separate from files for other mods and not autoload by default. If you keep your mod together in a zip file, or a directory to be loaded with "-game_dir", you should be okay. Bundling your whole working directory with a full install of EDuke32 and DukePlus, loose EDUKE.CON and duke3d.def files, and a complicated batch file is not acceptable. As simple as it may be for Windows users, it requires a lot of work for users of other operating systems to play your mod. (It may also cause problems for people that have EDuke32 set up a specific way on Windows.) | #'''Can my mod play nicely with other mods and existing EDuke32 installs?''' Operating systems like Linux keep their programs, data, and configuration in separate locations and will have only one copy of EDuke32 and a standard directory to load mods from. Therefore, well-behaved mods will keep their files separate from files for other mods and not autoload by default. If you keep your mod together in a zip file, or a directory to be loaded with "-game_dir", you should be okay. Bundling your whole working directory with a full install of EDuke32 and DukePlus, loose EDUKE.CON and duke3d.def files, and a complicated batch file is not acceptable. As simple as it may be for Windows users, it requires a lot of work for users of other operating systems to play your mod. (It may also cause problems for people that have EDuke32 set up a specific way on Windows.) | ||
#'''Has my mod been tested on other Operating Systems?''' This is not always possible, but it helps to have beta testers on different systems. They can help you answer the previous checks more certainly and also reveal unexpected issues that you can fix. | #'''Has my mod been tested on other Operating Systems?''' This is not always possible, but it helps to have beta testers on different systems. They can help you answer the previous checks more certainly and also reveal unexpected issues that you can fix. | ||
Revision as of 11:26, 6 March 2010
EDuke32 is cross-platform and supports Mac OS X and Linux as well as Windows. A properly made mod can run on any OS supported by EDuke32, but some considerations need to be made.
Checklist
- Is my mod in a file that users of other operating systems can open? (No self-extracting files or installer programs. zip, rar, and 7z files are good.)
- Did I type all the filenames with the same case as the actual files and directories? All Unix-like operating systems (Unix, Linux, BSD, Mac OS X) are case-sensitive. This means that MyMod.con, MYMOD.CON and mymod.con are all different files. Make sure you type the paths exactly as they appear, or EDuke32 will not find them. It is recommended (and standard practice on these systems) to always use lowercase file and directory names so that there is not confusion. The case of some filenames are hard-coded in EDuke32 and must be typed as follows:
- EDUKE.CON
- GAME.CON
- duke3d.def
- duke3d.grp
- tiles###.art
- Can my mod play nicely with other mods and existing EDuke32 installs? Operating systems like Linux keep their programs, data, and configuration in separate locations and will have only one copy of EDuke32 and a standard directory to load mods from. Therefore, well-behaved mods will keep their files separate from files for other mods and not autoload by default. If you keep your mod together in a zip file, or a directory to be loaded with "-game_dir", you should be okay. Bundling your whole working directory with a full install of EDuke32 and DukePlus, loose EDUKE.CON and duke3d.def files, and a complicated batch file is not acceptable. As simple as it may be for Windows users, it requires a lot of work for users of other operating systems to play your mod. (It may also cause problems for people that have EDuke32 set up a specific way on Windows.)
- Has my mod been tested on other Operating Systems? This is not always possible, but it helps to have beta testers on different systems. They can help you answer the previous checks more certainly and also reveal unexpected issues that you can fix.