Ultronomicon - User contributions [en]

https://wiki.uqm.stack.nl/api.php?action=feedcontributions&feedformat=atom&user=Fossil Ultronomicon - User contributions [en] 2026-04-14T06:49:35Z User contributions MediaWiki 1.43.6 https://wiki.uqm.stack.nl/index.php?title=Translations&diff=27603 Translations 2013-12-13T21:40:18Z

<p>Fossil: /* Russian */</p> <hr /> <div>This article describes the current localization efforts in the [[The Ur-Quan Masters]] project.<br /> <br /> ==General information==<br /> <br /> ===Current status===<br /> The resource system is suitable for creating language packs. An add-on package can be created to override any content file.<br /> <br /> The game works with [[wikipedia:UTF-8|UTF-8]] encoded [[wikipedia:UNICODE|UNICODE]] characters. The currently available characters are mostly the [[wikipedia:ASCII|ASCII]] characters. The various translation projects use their own characters where needed. Eventually, we will want to have shared font packs.<br /> <br /> Currently, all text is in simple text files. Eventually, we'll move to a richer XML-based file format. A conversion tool will be created to convert existing material.<br /> <br /> Some text still is hard-coded in the game. This will change at some point in the future.<br /> <br /> Currently, only left-to-right writing systems are supported.<br /> <br /> Support for non-ascii input in text fields is still limited.<br /> <br /> ===Using language packs===<br /> A language pack can be used [[The Ur-Quan Masters Technical FAQ#How do I use add-on packages?|like any other add-on package]].<br /> <br /> ===Creating language packs===<br /> Language packs are normal add-on packages, which means they will be a .zip file (renamed to .uqm), with in it a directory structure which overrides the files in the default content.<br /> <br /> '''NOTE: You can skip manually extracting files below and use the contents of [http://www.bjwaymods.net/uploads/translation_skeleton483.zip this] skeleton translation pack.'''<br /> <br /> ====Text files====<br /> The game expects all of its text files to be in [[wikipedia:UTF-8|UTF-8]] format.<br /> <br /> The subtitle files can be found in comm/<race>/<race>.txt in the content tree.<br /> <br /> The melee strings for the various ships can be found in the <race>/<race>.txt files.<br /> <br /> The text displayed for planetary exploration finds is contained in the ipanims/*.txt files.<br /> <br /> The file lbm/starcon.txt contains various other game strings.<br /> <br /> The file slides/intro/intro.txt contains the text for the intro sequence, as used by the DOS version of [[Star Control II]]. The files slides/ending/victory1.txt, slides/ending/victory2.txt and slides/ending/final.txt contain the text for the victory slides.<br /> <br /> ====Hard-coded strings====<br /> There are several places in the game where strings are used that are hard-coded in the source code. Most of those are error strings you may never see, but some are actually important in the game. For now, it would be best to ignore these strings, and translate them when these strings are no longer hard-coded.<br /> If you do translate them at this time, you would need to distribute game binaries of your own.<br /> <br /> ====Fonts====<br /> If you need additional characters you will need to add appropriate entries to the font dirs slides/slides.fon/, ipanims/lander.fon/, lbm/micro.fon/, lbm/tiny.fon/, lbm/player.fon/, lbm/starcon.fon/, credits/pt13.fon, credits/pt17.fon, credits/pt45.fon and comm/<race>/<race>.fon/ (note that starbas.fon, rebel.fon and spahome.fon do not exist). The number of the file is the UNICODE character code converted into decimal (from hex). [http://unicode.org/charts/ Here] are the official UNICODE character code charts. For hex-decimal conversion you can use [http://www.easycalculation.com/hex-converter.php this] online converter.<br /> <br /> Note that translation projects for other languages may have already created glyphs usable for your language.<br /> <br /> ====Images====<br /> Some game images include text. A full translation would need modified versions of those. Here goes a full list:<br /> <br /> lbm/activity.[0-1].png, modules.[0-15].png, newgame.[0-5].png, playmenu.[0-37,58-66].png, shipyard.[3-16,20,22,23].png, sismods.55.png, title.png, title.0.png<br /> <br /> melee/melebkgd.[0-27].png<br /> <br /> lastbat/lascap.0.png<br /> <br /> sis_ship/siscap.[0,9-14].png<br /> <br /> shofixti/oldcap.0.png, shocap.[0,12-19].png<br /> <br /> ipanims/lander.32.png, orbenter.0.png<br /> <br /> slides/intro/title.[1-2].png<br /> <br /> slides/ending/ending.6.png<br /> <br /> ====Speech====<br /> If you want to dub the actual speech, you'll need to create new versions of the .ogg files in comm/<race>/ in the content dir. You'll also need to create new .ts files for synchronisation with the subtitles. See [[#Tools|Tools]] below.<br /> <br /> ====Sounds====<br /> In melee, some ships play sound effects containing speech. Here's a list:<br /> <br /> orz/intruder.wav, secondary.wav<br /> <br /> pkunk/insult[01-14].wav<br /> <br /> slylandr/secondary.wav<br /> <br /> urquan/secondary.wav<br /> <br /> ====Documentation====<br /> The game comes with several documentation files. In particular the game manual would be a good candidate for translation.<br /> <br /> ===Tools===<br /> The Russian translation project created a program to make editing the UQM fonts easy. It's available [http://cs.ozerki.net/zap/sc2-rus/ here].<br /> <br /> Unix-like systems will have a program '''iconv''' which can be used to easilly change the encoding of a text file (from latin1 to UTF-8 for instance).<br /> <br /> A tool for generating the time stamps used to synchronise the speech with the subtitles is available in the official CVS tree of the [[The Ur-Quan Masters]] project, in the '''tools''' module. [http://cvs.sourceforge.net/viewcvs.py/sc2/tools/synch/]<br /> <br /> ==Translation projects==<br /> <br /> ===Finnish===<br /> Project site: http://web.archive.org/web/20090306075410/http://www2.kyamk.fi/~vi3dhepe/uqm-fin/index.html<br /> <br /> Download link: http://koti.mbnet.fi/tuukkar/uqm_fin_099.zip<br /> <br /> Forum thread: [http://uqm.stack.nl/forum/index.php?topic=2070.0]<br /> <br /> Status: almost complete<br /> <br /> ===German===<br /> Home page: http://sc2de.berlios.de/<br /> <br /> Project site: http://developer.berlios.de/projects/sc2de/<br /> <br /> Download: http://developer.berlios.de/project/showfiles.php?group_id=818<br /> <br /> CVS tree: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/sc2de/Sternkontrolle/<br /> <br /> Forum threads: [http://uqm.stack.nl/forum/index.php?topic=1952.0], [http://uqm.stack.nl/forum/index.php?topic=2070.0], [http://uqm.stack.nl/forum/index.php?topic=2236.0] [http://forum.uqm.stack.nl/index.php?topic=4879.0]<br /> <br /> Status: almost complete<br /> <br /> ===Italian===<br /> Home page: http://urquanitalia.blogspot.it<br /> <br /> The project is just started. We need help. If interested in contributing contact [mailto:giacomog88@gmail.com Giacomo]<br /> <br /> Forum thread: [http://forum.uqm.stack.nl/index.php?topic=5252.0]<br /> <br /> Status: ?%, accelerating towards light speed<br /> <br /> ===Japanese===<br /> There currently is no Japanese translation project underway, but the original 3DO version was also released in Japanese. We have a copy, and if the copyrights allow it, we may be able to add Japanese speech files without much problems.<br /> <br /> Bugzilla entry: [[uqmbug:605|#605]]<br /> <br /> Status: 0% complete<br /> <br /> ===Polish===<br /> For information contact [mailto:arael@tenbit.pl Arael]<br /> <br /> Forum threads: [http://uqm.stack.nl/forum/index.php?topic=2391]<br /> <br /> Status: temporarily stalled<br /> <br /> ===Portuguese===<br /> The project has already been started. Plans are to do both a Brazilian and Portuguese version. A call for contributors has been made. Contact [[User:nightshadow|nightshadow]] if interested.<br /> <br /> Project Site: http://pt-masters.net/<br /> <br /> Forum threads: [http://uqm.stack.nl/forum/index.php?topic=2425.0],[http://uqm.stack.nl/forum/index.php?topic=2044.0], [http://uqm.stack.nl/forum/index.php?topic=2070.0], [http://uqm.stack.nl/forum/index.php?topic=3639.0]<br /> <br /> Status: Just Started<br /> <br /> ===Russian===<br /> Main site: http://uqm-rus.uvw.ru/<br /> <br /> Forum threads: [http://uqm.stack.nl/forum/index.php?topic=2070.0], [http://uqm.stack.nl/forum/index.php?topic=1952.0], [http://uqm.stack.nl/forum/index.php?topic=2221.0] [http://uqm.stack.nl/forum/index.php?topic=2426.0]<br /> <br /> Status: complete<br /> <br /> ===Spanish===<br /> The Spanish translation project is in need of help. Contact [mailto:volka@custom-creations.org Volka] if you're interested in contributing.<br /> <br /> Version 0.3 of the translation is available. Most of the conversation text has been translated, and the focus is now on the translation of the images. Visit the [http://www.custom-creations.org/~starsite/UQM-spa/descargas.php Downloads] section of the proyect.<br /> <br /> Main site: http://www.custom-creations.org/~starsite/UQM-spa/<br /> <br /> Forum threads: [http://uqm.stack.nl/forum/index.php?topic=2070.0] [http://uqm.stack.nl/forum/index.php?topic=2332.0] [http://uqm.stack.nl/forum/index.php?topic=2633.0]<br /> <br /> Status: 70%<br /> <br /> <br /> [[Category:About the Star Control series]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Content_Management&diff=26041 Content Management 2011-07-18T19:35:07Z

<p>Fossil: /* Add-on layout */</p> <hr /> <div>{{safe}}<br /> <br /> ==Introduction==<br /> The game still uses a virtual file system as before: see [[Content Management]] for information on this. However, starting in 0.6.4, the "layering" effect of the directory system is no longer used to index files for the purposes of regular addons. The concept of addon shadow packages was introduced in 0.6.6 as a stop-gap since the resource system is not yet finished.<br /> <br /> ==Hey, my remixes don't work!==<br /> <br /> UQM 0.6.4 (SVN revision 2869) changed addon pack mechanics incompatibly. Your remix zips are still OK, but you will need to perform these steps:<br /> <br /> * Move the addons directory from content/packages to content/<br /> * Download the appropriate .rmp files from http://sc2.sourceforge.net/remix-rmp/ and put them in the same directory as the remix zips.<br /> * Ensure that the remix directory is, in fact, addons/remix.<br /> <br /> ==Detailed description==<br /> <br /> Still needs to be done.<br /> <br /> ==A typical layout==<br /> <br /> ===On Windows===<br /> A typical The Ur-Quan Masters installation on Windows looks like this:<br /> <code><br /> C:\Program Files\The Ur-Quan Masters\uqm.exe<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.7.0-content.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-0.7.0-3domusic.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-0.7.0-voice.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc1.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc2.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc3.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\version<br /> </code><br /> <br /> ===On Mac OS X===<br /> A typical The Ur-Quan Masters installation on Mac OS X looks like this:<br /> <code><br /> /Applications/The Ur-Quan Masters/Contents/PkgInfo<br /> /Applications/The Ur-Quan Masters/Contents/Info.plist<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Ogg.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL_image.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Vorbis.framework<br /> /Applications/The Ur-Quan Masters/Contents/MacOS/The Ur-Quan Masters<br /> /Applications/The Ur-Quan Masters/Contents/Resources/The Ur-Quan Masters.icns<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/version<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.7.0-content.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-0.7.0-voice.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc1.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc2.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc3.uqm<br /> </code><br /> <br /> ===On Linux===<br /> A typical The Ur-Quan Masters installation on Linux looks like this:<br /> <code><br /> /usr/local/bin/uqm (wrapper script)<br /> /usr/local/lib/uqm/uqm (the actual executable)<br /> /usr/local/share/uqm/content/packages/uqm-0.7.0-content.uqm<br /> /usr/local/share/uqm/content/addons/uqm-0.7.0-3domusic.uqm<br /> /usr/local/share/uqm/content/addons/uqm-0.7.0-voice.uqm<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc1.uqm<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc2.uqm<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc3.uqm<br /> /usr/local/share/uqm/content/version<br /> </code><br /> <br /> ==Content directories==<br /> The following list shows which directories are mounted in the game in 0.7. The later mentioned ones are mounted on top of the earlier mentioned ones.<br /> {|border=1<br /> !Directory!!Mounted on!!flags<br /> |-<br /> |[[#Default packages|default packages]], in alphabetic order||/ ||read-only<br /> |-<br /> |[[#Add-on packages|add-on packages]], in alphabetic order ||/addons/[name] ||read-only<br /> |-<br /> |[[#Content base directory|content base directory]] ||/ ||read-only<br /> |-<br /> |[[#Add-on shadow packages|add-on shadow packages]], in specified order ||/ ||read-only<br /> |-<br /> |[[#User data directory|user data directory]] ||/ ||read-write<br /> |-<br /> |[[#Temporary directory|temporary directory]] ||/tmp||read-write<br /> |}<br /> Note that addon packages are now mounted in their own tree branches, with one exception. The only way to override (or ''shadow'') the content is with an add-on shadow package. This is necessary in cases like extending fonts or supplying different menu keys because the resource system is not yet finished.<br /> <br /> ==Add-on layout==<br /> This is better illustrated with an example:<br /> <code><br /> addons/russian-trans-2.0.zip<br /> </code><br /> Where ''russian-trans-2.0.zip'' contains:<br /> <code><br /> lang-russian/russian.rmp<br /> lang-russian/uqmpack.nfo<br /> lang-russian/shadow-content/russian-shadow.zip (see notes below)<br /> lang-russian/comm/commander.txt<br /> lang-russian/comm/arilou.txt<br /> [etc., files with layout of author's choosing, all under lang-russian/ ]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /addons/lang-russian/russian.rmp<br /> /addons/lang-russian/uqmpack.nfo<br /> /addons/lang-russian/comm/commander.txt<br /> /addons/lang-russian/comm/arilou.txt<br /> [etc.]<br /> </code><br /> <br /> And ''russian-shadow.zip'' contains:<br /> <code><br /> base/fonts/micro.fon/<br /> base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /base/fonts/micro.fon/<br /> /base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> A shadow content zip works like the add-ons worked in the prior versions: the file structure must match the default content layout, and the files in the zip will ''shadow'' (or override) the default content.<br /> <br /> ''russian.rmp'' contains:<br /> <code><br /> comm.arilou.dialogue = CONVERSATION:addons/lang-russian/comm/arilou.txt:addons/3dovoice/arilou/:addons/3dovoice/arilou/arilou.ts <br /> comm.commander.dialogue = CONVERSATION:addons/lang-russian/comm/commander.txt:addons/3dovoice/commander/:addons/3dovoice/commander/commander.ts <br /> [etc., resource identifiers of author's choosing; see content/uqm.rmp for resource strings]<br /> </code><br /> An add-on must contain at least one .rmp file or it will not be loaded.<br /> Note that CONVERSATION resource type has three parts: the subtitles file, the voice ogg directory, and the timestamps file. If the last two are omitted, the voices will not play when this add-on is loaded. See the ''3domusic'' and ''3dovoice'' standard add-on for more examples. You may add completely new resource identifiers if you plan to add brand new content in your mod.<br /> <br /> ''uqmpack.nfo'' contains:<br /> <code><br /> name=Russian Pack<br /> author=John Doe<br /> version=2<br /> description=Russian translation of the game.<br /> year=2011<br /> min_uqm_version=0.7<br /> </code><br /> While ''uqmpack.nfo'' file is not currently required in the add-on, we ask that you add one for the future online add-on management. This will make your add-on more user-friendly.<br /> <br /> ====Shadow content====<br /> Shadow content works like the add-ons worked in the prior versions: the file structure must match the default content layout, and the files will ''shadow'' (or override) the default content.<br /> <br /> Currently, add-on ''shadow-content'' directory '''must''' contain .zip (or .uqm) files. Only zipped files will be mounted under the root directory. This means that in order to create a single zipped add-on file with shadow content, you have to put a zip inside a zip. In that case, it may be a good idea to zip the shadow content with method ''store'' (no compression) in order to improve the in-game performance. Please note that we intend to remove this limitation in v0.7.1. We hope to release the 0.7.1 with bugfixes as quickly as we possible, so modders may want to wait for it.<br /> <br /> ==Current Development Status==<br /> <br /> The resource system (and thus the content directory) are in flux as the development team works on implementing a new resource system. This should remove a lot of the more brittle components from the legacy system and make addons easier to add, and mods to the source easier to make work. Detailed goals, milestones, and comments are in this section.<br /> <br /> ===Top-Level Roadmap===<br /> <br /> This actually may migrate over time as we see what works and what doesn't, but it will at least mark where we've been and where we think we're going.<br /> <br /> # Implement a generic string-based key-to-value system for doing resource lookups. ''Completed in Revision 1916.''<br /> # Drop requirement on binary resource indices by translating them to text. ''Completed in Revision 2003.''<br /> # Replace the integer-based resource system with string-based key mappings that are easier to extend. ''Completed in Revision 2963.''<br /> # Rework resource types to allow for a wider range of resources. Migrate all 3DO content into standalone addon packs. ''Completed in Revision 3104.''<br /> # Uniform API for all uses of the resource-map system, merging about six redundant subsystems into one. ''In progress.''<br /> <br /> ===Current goals===<br /> <br /> It's now feasible to start moving hardcoded data like the starship constants and the starmap itself into .rmp files. It's not clear how much of this is wise for 0.7.0 itself, but we should probably do at least a ''little'' to gather interest.<br /> <br /> * Keep user settings in a resource-map. ''Completed in Revision 1916.''<br /> * Keep key configuration in a resource-map. ''Completed in Revision 2705.''<br /> * Allow loads of resource files to be placed into isolated submaps to keep values separated. ''Completed in Revision 3105.''<br /> * Allow saves to strip some or all of the common prefix to save only the "submap" component. ''Completed in Revision 3105.''<br /> * Merge user settings and key configuration into the main resource map, eliminating the now-redundant mapres.c routines. ''Completed in Revision 3108.''<br /> * Turn melee data (teams, current situation) into resource maps like the other two.<br /> <br /> ===Other work===<br /> <br /> This is a bit more nebulous since we haven't advanced far enough to see what's a good idea and what isn't.<br /> <br /> *Massive, cathartic violence against the content directory structure, ending in convenient subprojects. ''Incomplete, but started in revision 2870.''<br /> *Let .rmp files include other ones to make uqm.rmp less monolithic. This could also be used to automatically include addon packs (such as, say, a Cyrillic Font Pack) if necessary.<br /> **At the moment we just load all .rmp files in any given directory. This may be good enough.<br /> *The hack to make the remix packs work is kind of ugly. A more permanent fix would allow special variable expansion to map to wherever uio elected to put it, giving each extension its own space for files. Best of all would be a magic variable for "The home of the extension named X." Implementing this would give us full namespaces and namespace imports.<br /> ** It's only ugly under the surface, though, and will only affect mod writers, and that rather minimally. The users just shove packages blindly into content/addons.<br /> *Online configuration of which extensions to use.<br /> *It would be nice to have an offline application for building extensions.<br /> *A more "self-aware" resource system should give us a much better handle on the remaining resource-related bugs.<br /> *Can we leverage this for improving save game formats?<br /> *Planet data is aliased in #defines and structure initializers when it should probably be in the resource map.<br /> *Ship data is *not* aliased, requiring a bunch of structure initializers that probably (though less probably than in the planet data case) should be name normalized.<br /> <br /> [[Category:About the Star Control series]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Content_Management&diff=26037 Content Management 2011-07-17T05:37:32Z

<p>Fossil: /* Add-on layout */</p> <hr /> <div>{{safe}}<br /> <br /> ==Introduction==<br /> The game still uses a virtual file system as before: see [[Content Management]] for information on this. However, starting in 0.6.4, the "layering" effect of the directory system is no longer used to index files for the purposes of regular addons. The concept of addon shadow packages was introduced in 0.6.6 as a stop-gap since the resource system is not yet finished.<br /> <br /> ==Hey, my remixes don't work!==<br /> <br /> UQM 0.6.4 (SVN revision 2869) changed addon pack mechanics incompatibly. Your remix zips are still OK, but you will need to perform these steps:<br /> <br /> * Move the addons directory from content/packages to content/<br /> * Download the appropriate .rmp files from http://sc2.sourceforge.net/remix-rmp/ and put them in the same directory as the remix zips.<br /> * Ensure that the remix directory is, in fact, addons/remix.<br /> <br /> ==Detailed description==<br /> <br /> Still needs to be done.<br /> <br /> ==A typical layout==<br /> <br /> ===On Windows===<br /> A typical The Ur-Quan Masters installation on Windows looks like this:<br /> <code><br /> C:\Program Files\The Ur-Quan Masters\uqm.exe<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.7.0-content.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-0.7.0-3domusic.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-0.7.0-voice.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc1.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc2.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc3.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\version<br /> </code><br /> <br /> ===On Mac OS X===<br /> A typical The Ur-Quan Masters installation on Mac OS X looks like this:<br /> <code><br /> /Applications/The Ur-Quan Masters/Contents/PkgInfo<br /> /Applications/The Ur-Quan Masters/Contents/Info.plist<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Ogg.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL_image.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Vorbis.framework<br /> /Applications/The Ur-Quan Masters/Contents/MacOS/The Ur-Quan Masters<br /> /Applications/The Ur-Quan Masters/Contents/Resources/The Ur-Quan Masters.icns<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/version<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.7.0-content.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-0.7.0-voice.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc1.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc2.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc3.uqm<br /> </code><br /> <br /> ===On Linux===<br /> A typical The Ur-Quan Masters installation on Linux looks like this:<br /> <code><br /> /usr/local/bin/uqm (wrapper script)<br /> /usr/local/lib/uqm/uqm (the actual executable)<br /> /usr/local/share/uqm/content/packages/uqm-0.7.0-content.uqm<br /> /usr/local/share/uqm/content/addons/uqm-0.7.0-3domusic.uqm<br /> /usr/local/share/uqm/content/addons/uqm-0.7.0-voice.uqm<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc1.uqm<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc2.uqm<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc3.uqm<br /> /usr/local/share/uqm/content/version<br /> </code><br /> <br /> ==Content directories==<br /> The following list shows which directories are mounted in the game in 0.7. The later mentioned ones are mounted on top of the earlier mentioned ones.<br /> {|border=1<br /> !Directory!!Mounted on!!flags<br /> |-<br /> |[[#Default packages|default packages]], in alphabetic order||/ ||read-only<br /> |-<br /> |[[#Add-on packages|add-on packages]], in alphabetic order ||/addons/[name] ||read-only<br /> |-<br /> |[[#Content base directory|content base directory]] ||/ ||read-only<br /> |-<br /> |[[#Add-on shadow packages|add-on shadow packages]], in specified order ||/ ||read-only<br /> |-<br /> |[[#User data directory|user data directory]] ||/ ||read-write<br /> |-<br /> |[[#Temporary directory|temporary directory]] ||/tmp||read-write<br /> |}<br /> Note that addon packages are now mounted in their own tree branches, with one exception. The only way to override (or ''shadow'') the content is with an add-on shadow package. This is necessary in cases like extending fonts or supplying different menu keys because the resource system is not yet finished.<br /> <br /> ==Add-on layout==<br /> This is better illustrated with an example:<br /> <code><br /> addons/russian-trans-2.0.zip<br /> </code><br /> Where ''russian-trans-2.0.zip'' contains:<br /> <code><br /> lang-russian/russian.rmp<br /> lang-russian/uqmpack.nfo<br /> lang-russian/shadow-content/russian-shadow.zip<br /> lang-russian/comm/commander.txt<br /> lang-russian/comm/arilou.txt<br /> [etc., files with layout of author's choosing, all under lang-russian/ ]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /addons/lang-russian/russian.rmp<br /> /addons/lang-russian/uqmpack.nfo<br /> /addons/lang-russian/comm/commander.txt<br /> /addons/lang-russian/comm/arilou.txt<br /> [etc.]<br /> </code><br /> <br /> And ''russian-shadow.zip'' contains:<br /> <code><br /> base/fonts/micro.fon/<br /> base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /base/fonts/micro.fon/<br /> /base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> <br /> ''russian.rmp'' contains:<br /> <code><br /> comm.arilou.dialogue = CONVERSATION:addons/lang-russian/comm/arilou.txt:addons/3dovoice/arilou/:addons/3dovoice/arilou/arilou.ts <br /> comm.commander.dialogue = CONVERSATION:addons/lang-russian/comm/commander.txt:addons/3dovoice/commander/:addons/3dovoice/commander/commander.ts <br /> [etc., resource identifiers of author's choosing; see content/uqm.rmp for resource strings]<br /> </code><br /> An add-on must contain at least one .rmp file or it will not be loaded.<br /> Note that CONVERSATION resource type has three parts: the subtitles file, the voice ogg directory, and the timestamps file. If the last two are omitted, the voices will not play when this add-on is loaded. See the ''3domusic'' and ''3dovoice'' standard add-on for more examples. You may add completely new resource identifiers if you plan to add brand new content in your mod.<br /> <br /> ''uqmpack.nfo'' contains:<br /> <code><br /> name=Russian Pack<br /> author=John Doe<br /> version=2<br /> description=Russian translation of the game.<br /> year=2011<br /> min_uqm_version=0.7<br /> </code><br /> While ''uqmpack.nfo'' file is not currently required in the add-on, we ask that you add one for the future online add-on management. This will make your add-on more user-friendly.<br /> <br /> Currently, addon ''shadow-content'' directory '''must''' contain .zip (or .uqm) files. Only zipped files will be mounted under the root directory. This means that in order to create a single zipped addon file with shadow content, you have to put a zip inside a zip. In that case, it may be a good idea to zip the shadow content with method ''store'' (no compression) in order to improve the in-game performance.<br /> <br /> ==Current Development Status==<br /> <br /> The resource system (and thus the content directory) are in flux as the development team works on implementing a new resource system. This should remove a lot of the more brittle components from the legacy system and make addons easier to add, and mods to the source easier to make work. Detailed goals, milestones, and comments are in this section.<br /> <br /> ===Top-Level Roadmap===<br /> <br /> This actually may migrate over time as we see what works and what doesn't, but it will at least mark where we've been and where we think we're going.<br /> <br /> # Implement a generic string-based key-to-value system for doing resource lookups. ''Completed in Revision 1916.''<br /> # Drop requirement on binary resource indices by translating them to text. ''Completed in Revision 2003.''<br /> # Replace the integer-based resource system with string-based key mappings that are easier to extend. ''Completed in Revision 2963.''<br /> # Rework resource types to allow for a wider range of resources. Migrate all 3DO content into standalone addon packs. ''Completed in Revision 3104.''<br /> # Uniform API for all uses of the resource-map system, merging about six redundant subsystems into one. ''In progress.''<br /> <br /> ===Current goals===<br /> <br /> It's now feasible to start moving hardcoded data like the starship constants and the starmap itself into .rmp files. It's not clear how much of this is wise for 0.7.0 itself, but we should probably do at least a ''little'' to gather interest.<br /> <br /> * Keep user settings in a resource-map. ''Completed in Revision 1916.''<br /> * Keep key configuration in a resource-map. ''Completed in Revision 2705.''<br /> * Allow loads of resource files to be placed into isolated submaps to keep values separated. ''Completed in Revision 3105.''<br /> * Allow saves to strip some or all of the common prefix to save only the "submap" component. ''Completed in Revision 3105.''<br /> * Merge user settings and key configuration into the main resource map, eliminating the now-redundant mapres.c routines. ''Completed in Revision 3108.''<br /> * Turn melee data (teams, current situation) into resource maps like the other two.<br /> <br /> ===Other work===<br /> <br /> This is a bit more nebulous since we haven't advanced far enough to see what's a good idea and what isn't.<br /> <br /> *Massive, cathartic violence against the content directory structure, ending in convenient subprojects. ''Incomplete, but started in revision 2870.''<br /> *Let .rmp files include other ones to make uqm.rmp less monolithic. This could also be used to automatically include addon packs (such as, say, a Cyrillic Font Pack) if necessary.<br /> **At the moment we just load all .rmp files in any given directory. This may be good enough.<br /> *The hack to make the remix packs work is kind of ugly. A more permanent fix would allow special variable expansion to map to wherever uio elected to put it, giving each extension its own space for files. Best of all would be a magic variable for "The home of the extension named X." Implementing this would give us full namespaces and namespace imports.<br /> ** It's only ugly under the surface, though, and will only affect mod writers, and that rather minimally. The users just shove packages blindly into content/addons.<br /> *Online configuration of which extensions to use.<br /> *It would be nice to have an offline application for building extensions.<br /> *A more "self-aware" resource system should give us a much better handle on the remaining resource-related bugs.<br /> *Can we leverage this for improving save game formats?<br /> *Planet data is aliased in #defines and structure initializers when it should probably be in the resource map.<br /> *Ship data is *not* aliased, requiring a bunch of structure initializers that probably (though less probably than in the planet data case) should be name normalized.<br /> <br /> [[Category:About the Star Control series]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Content_Management&diff=26036 Content Management 2011-07-17T05:07:26Z

<p>Fossil: /* On Linux */</p> <hr /> <div>{{safe}}<br /> <br /> ==Introduction==<br /> The game still uses a virtual file system as before: see [[Content Management]] for information on this. However, starting in 0.6.4, the "layering" effect of the directory system is no longer used to index files for the purposes of regular addons. The concept of addon shadow packages was introduced in 0.6.6 as a stop-gap since the resource system is not yet finished.<br /> <br /> ==Hey, my remixes don't work!==<br /> <br /> UQM 0.6.4 (SVN revision 2869) changed addon pack mechanics incompatibly. Your remix zips are still OK, but you will need to perform these steps:<br /> <br /> * Move the addons directory from content/packages to content/<br /> * Download the appropriate .rmp files from http://sc2.sourceforge.net/remix-rmp/ and put them in the same directory as the remix zips.<br /> * Ensure that the remix directory is, in fact, addons/remix.<br /> <br /> ==Detailed description==<br /> <br /> Still needs to be done.<br /> <br /> ==A typical layout==<br /> <br /> ===On Windows===<br /> A typical The Ur-Quan Masters installation on Windows looks like this:<br /> <code><br /> C:\Program Files\The Ur-Quan Masters\uqm.exe<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.7.0-content.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-0.7.0-3domusic.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-0.7.0-voice.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc1.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc2.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc3.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\version<br /> </code><br /> <br /> ===On Mac OS X===<br /> A typical The Ur-Quan Masters installation on Mac OS X looks like this:<br /> <code><br /> /Applications/The Ur-Quan Masters/Contents/PkgInfo<br /> /Applications/The Ur-Quan Masters/Contents/Info.plist<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Ogg.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL_image.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Vorbis.framework<br /> /Applications/The Ur-Quan Masters/Contents/MacOS/The Ur-Quan Masters<br /> /Applications/The Ur-Quan Masters/Contents/Resources/The Ur-Quan Masters.icns<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/version<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.7.0-content.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-0.7.0-voice.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc1.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc2.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc3.uqm<br /> </code><br /> <br /> ===On Linux===<br /> A typical The Ur-Quan Masters installation on Linux looks like this:<br /> <code><br /> /usr/local/bin/uqm (wrapper script)<br /> /usr/local/lib/uqm/uqm (the actual executable)<br /> /usr/local/share/uqm/content/packages/uqm-0.7.0-content.uqm<br /> /usr/local/share/uqm/content/addons/uqm-0.7.0-3domusic.uqm<br /> /usr/local/share/uqm/content/addons/uqm-0.7.0-voice.uqm<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc1.uqm<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc2.uqm<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc3.uqm<br /> /usr/local/share/uqm/content/version<br /> </code><br /> <br /> ==Content directories==<br /> The following list shows which directories are mounted in the game in 0.7. The later mentioned ones are mounted on top of the earlier mentioned ones.<br /> {|border=1<br /> !Directory!!Mounted on!!flags<br /> |-<br /> |[[#Default packages|default packages]], in alphabetic order||/ ||read-only<br /> |-<br /> |[[#Add-on packages|add-on packages]], in alphabetic order ||/addons/[name] ||read-only<br /> |-<br /> |[[#Content base directory|content base directory]] ||/ ||read-only<br /> |-<br /> |[[#Add-on shadow packages|add-on shadow packages]], in specified order ||/ ||read-only<br /> |-<br /> |[[#User data directory|user data directory]] ||/ ||read-write<br /> |-<br /> |[[#Temporary directory|temporary directory]] ||/tmp||read-write<br /> |}<br /> Note that addon packages are now mounted in their own tree branches, with one exception. The only way to override (or ''shadow'') the content is with an add-on shadow package. This is necessary in cases like extending fonts or supplying different menu keys because the resource system is not yet finished.<br /> <br /> ==Add-on layout==<br /> This is better illustrated with an example:<br /> <code><br /> addons/lang-russian/russian.zip<br /> addons/lang-russian/shadow-content/russian-shadow.zip<br /> </code><br /> Where ''russian.zip'' contains:<br /> <code><br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /addons/lang-russian/russian.rmp<br /> /addons/lang-russian/comm/commander.txt<br /> /addons/lang-russian/comm/arilou.txt<br /> [etc.]<br /> </code><br /> <br /> And ''russian-shadow.zip'' contains:<br /> <code><br /> base/fonts/micro.fon/<br /> base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /base/fonts/micro.fon/<br /> /base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> <br /> Addon ''shadow-content'' directory '''must''' contain .zip (or .uqm) files. Only zipped files will be mounted under the root directory. This means that in order to create a single zipped addon file with shadow content, you have to put a zip inside a zip. In that case, it may be a good idea to zip the shadow content with method ''store'' (no compression) in order to improve the in-game performance. A single ''russian.zip'' package would then look like this:<br /> <code><br /> shadow-content/russian-shadow.zip<br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> <br /> ==Current Development Status==<br /> <br /> The resource system (and thus the content directory) are in flux as the development team works on implementing a new resource system. This should remove a lot of the more brittle components from the legacy system and make addons easier to add, and mods to the source easier to make work. Detailed goals, milestones, and comments are in this section.<br /> <br /> ===Top-Level Roadmap===<br /> <br /> This actually may migrate over time as we see what works and what doesn't, but it will at least mark where we've been and where we think we're going.<br /> <br /> # Implement a generic string-based key-to-value system for doing resource lookups. ''Completed in Revision 1916.''<br /> # Drop requirement on binary resource indices by translating them to text. ''Completed in Revision 2003.''<br /> # Replace the integer-based resource system with string-based key mappings that are easier to extend. ''Completed in Revision 2963.''<br /> # Rework resource types to allow for a wider range of resources. Migrate all 3DO content into standalone addon packs. ''Completed in Revision 3104.''<br /> # Uniform API for all uses of the resource-map system, merging about six redundant subsystems into one. ''In progress.''<br /> <br /> ===Current goals===<br /> <br /> It's now feasible to start moving hardcoded data like the starship constants and the starmap itself into .rmp files. It's not clear how much of this is wise for 0.7.0 itself, but we should probably do at least a ''little'' to gather interest.<br /> <br /> * Keep user settings in a resource-map. ''Completed in Revision 1916.''<br /> * Keep key configuration in a resource-map. ''Completed in Revision 2705.''<br /> * Allow loads of resource files to be placed into isolated submaps to keep values separated. ''Completed in Revision 3105.''<br /> * Allow saves to strip some or all of the common prefix to save only the "submap" component. ''Completed in Revision 3105.''<br /> * Merge user settings and key configuration into the main resource map, eliminating the now-redundant mapres.c routines. ''Completed in Revision 3108.''<br /> * Turn melee data (teams, current situation) into resource maps like the other two.<br /> <br /> ===Other work===<br /> <br /> This is a bit more nebulous since we haven't advanced far enough to see what's a good idea and what isn't.<br /> <br /> *Massive, cathartic violence against the content directory structure, ending in convenient subprojects. ''Incomplete, but started in revision 2870.''<br /> *Let .rmp files include other ones to make uqm.rmp less monolithic. This could also be used to automatically include addon packs (such as, say, a Cyrillic Font Pack) if necessary.<br /> **At the moment we just load all .rmp files in any given directory. This may be good enough.<br /> *The hack to make the remix packs work is kind of ugly. A more permanent fix would allow special variable expansion to map to wherever uio elected to put it, giving each extension its own space for files. Best of all would be a magic variable for "The home of the extension named X." Implementing this would give us full namespaces and namespace imports.<br /> ** It's only ugly under the surface, though, and will only affect mod writers, and that rather minimally. The users just shove packages blindly into content/addons.<br /> *Online configuration of which extensions to use.<br /> *It would be nice to have an offline application for building extensions.<br /> *A more "self-aware" resource system should give us a much better handle on the remaining resource-related bugs.<br /> *Can we leverage this for improving save game formats?<br /> *Planet data is aliased in #defines and structure initializers when it should probably be in the resource map.<br /> *Ship data is *not* aliased, requiring a bunch of structure initializers that probably (though less probably than in the planet data case) should be name normalized.<br /> <br /> [[Category:About the Star Control series]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Content_Management&diff=26035 Content Management 2011-07-17T05:06:36Z

<p>Fossil: /* On Linux */</p> <hr /> <div>{{safe}}<br /> <br /> ==Introduction==<br /> The game still uses a virtual file system as before: see [[Content Management]] for information on this. However, starting in 0.6.4, the "layering" effect of the directory system is no longer used to index files for the purposes of regular addons. The concept of addon shadow packages was introduced in 0.6.6 as a stop-gap since the resource system is not yet finished.<br /> <br /> ==Hey, my remixes don't work!==<br /> <br /> UQM 0.6.4 (SVN revision 2869) changed addon pack mechanics incompatibly. Your remix zips are still OK, but you will need to perform these steps:<br /> <br /> * Move the addons directory from content/packages to content/<br /> * Download the appropriate .rmp files from http://sc2.sourceforge.net/remix-rmp/ and put them in the same directory as the remix zips.<br /> * Ensure that the remix directory is, in fact, addons/remix.<br /> <br /> ==Detailed description==<br /> <br /> Still needs to be done.<br /> <br /> ==A typical layout==<br /> <br /> ===On Windows===<br /> A typical The Ur-Quan Masters installation on Windows looks like this:<br /> <code><br /> C:\Program Files\The Ur-Quan Masters\uqm.exe<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.7.0-content.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-0.7.0-3domusic.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-0.7.0-voice.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc1.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc2.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc3.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\version<br /> </code><br /> <br /> ===On Mac OS X===<br /> A typical The Ur-Quan Masters installation on Mac OS X looks like this:<br /> <code><br /> /Applications/The Ur-Quan Masters/Contents/PkgInfo<br /> /Applications/The Ur-Quan Masters/Contents/Info.plist<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Ogg.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL_image.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Vorbis.framework<br /> /Applications/The Ur-Quan Masters/Contents/MacOS/The Ur-Quan Masters<br /> /Applications/The Ur-Quan Masters/Contents/Resources/The Ur-Quan Masters.icns<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/version<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.7.0-content.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-0.7.0-voice.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc1.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc2.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc3.uqm<br /> </code><br /> <br /> ===On Linux===<br /> A typical The Ur-Quan Masters installation on Linux looks like this:<br /> <code><br /> /usr/local/bin/uqm (wrapper script)<br /> /usr/local/lib/uqm/uqm (the actual executable)<br /> /usr/local/share/uqm/content/packages/uqm-0.7.0-content.uqm<br /> /usr/local/share/uqm/content/addons/uqm-0.7.0-3domusic.uqm<br /> /usr/local/share/uqm/content/addons/uqm-0.7.0-voice.uqm<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc1.zip<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc2.zip<br /> /usr/local/share/uqm/content/addons/uqm-remix-disc3.zip<br /> /usr/local/share/uqm/content/version<br /> </code><br /> <br /> ==Content directories==<br /> The following list shows which directories are mounted in the game in 0.7. The later mentioned ones are mounted on top of the earlier mentioned ones.<br /> {|border=1<br /> !Directory!!Mounted on!!flags<br /> |-<br /> |[[#Default packages|default packages]], in alphabetic order||/ ||read-only<br /> |-<br /> |[[#Add-on packages|add-on packages]], in alphabetic order ||/addons/[name] ||read-only<br /> |-<br /> |[[#Content base directory|content base directory]] ||/ ||read-only<br /> |-<br /> |[[#Add-on shadow packages|add-on shadow packages]], in specified order ||/ ||read-only<br /> |-<br /> |[[#User data directory|user data directory]] ||/ ||read-write<br /> |-<br /> |[[#Temporary directory|temporary directory]] ||/tmp||read-write<br /> |}<br /> Note that addon packages are now mounted in their own tree branches, with one exception. The only way to override (or ''shadow'') the content is with an add-on shadow package. This is necessary in cases like extending fonts or supplying different menu keys because the resource system is not yet finished.<br /> <br /> ==Add-on layout==<br /> This is better illustrated with an example:<br /> <code><br /> addons/lang-russian/russian.zip<br /> addons/lang-russian/shadow-content/russian-shadow.zip<br /> </code><br /> Where ''russian.zip'' contains:<br /> <code><br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /addons/lang-russian/russian.rmp<br /> /addons/lang-russian/comm/commander.txt<br /> /addons/lang-russian/comm/arilou.txt<br /> [etc.]<br /> </code><br /> <br /> And ''russian-shadow.zip'' contains:<br /> <code><br /> base/fonts/micro.fon/<br /> base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /base/fonts/micro.fon/<br /> /base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> <br /> Addon ''shadow-content'' directory '''must''' contain .zip (or .uqm) files. Only zipped files will be mounted under the root directory. This means that in order to create a single zipped addon file with shadow content, you have to put a zip inside a zip. In that case, it may be a good idea to zip the shadow content with method ''store'' (no compression) in order to improve the in-game performance. A single ''russian.zip'' package would then look like this:<br /> <code><br /> shadow-content/russian-shadow.zip<br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> <br /> ==Current Development Status==<br /> <br /> The resource system (and thus the content directory) are in flux as the development team works on implementing a new resource system. This should remove a lot of the more brittle components from the legacy system and make addons easier to add, and mods to the source easier to make work. Detailed goals, milestones, and comments are in this section.<br /> <br /> ===Top-Level Roadmap===<br /> <br /> This actually may migrate over time as we see what works and what doesn't, but it will at least mark where we've been and where we think we're going.<br /> <br /> # Implement a generic string-based key-to-value system for doing resource lookups. ''Completed in Revision 1916.''<br /> # Drop requirement on binary resource indices by translating them to text. ''Completed in Revision 2003.''<br /> # Replace the integer-based resource system with string-based key mappings that are easier to extend. ''Completed in Revision 2963.''<br /> # Rework resource types to allow for a wider range of resources. Migrate all 3DO content into standalone addon packs. ''Completed in Revision 3104.''<br /> # Uniform API for all uses of the resource-map system, merging about six redundant subsystems into one. ''In progress.''<br /> <br /> ===Current goals===<br /> <br /> It's now feasible to start moving hardcoded data like the starship constants and the starmap itself into .rmp files. It's not clear how much of this is wise for 0.7.0 itself, but we should probably do at least a ''little'' to gather interest.<br /> <br /> * Keep user settings in a resource-map. ''Completed in Revision 1916.''<br /> * Keep key configuration in a resource-map. ''Completed in Revision 2705.''<br /> * Allow loads of resource files to be placed into isolated submaps to keep values separated. ''Completed in Revision 3105.''<br /> * Allow saves to strip some or all of the common prefix to save only the "submap" component. ''Completed in Revision 3105.''<br /> * Merge user settings and key configuration into the main resource map, eliminating the now-redundant mapres.c routines. ''Completed in Revision 3108.''<br /> * Turn melee data (teams, current situation) into resource maps like the other two.<br /> <br /> ===Other work===<br /> <br /> This is a bit more nebulous since we haven't advanced far enough to see what's a good idea and what isn't.<br /> <br /> *Massive, cathartic violence against the content directory structure, ending in convenient subprojects. ''Incomplete, but started in revision 2870.''<br /> *Let .rmp files include other ones to make uqm.rmp less monolithic. This could also be used to automatically include addon packs (such as, say, a Cyrillic Font Pack) if necessary.<br /> **At the moment we just load all .rmp files in any given directory. This may be good enough.<br /> *The hack to make the remix packs work is kind of ugly. A more permanent fix would allow special variable expansion to map to wherever uio elected to put it, giving each extension its own space for files. Best of all would be a magic variable for "The home of the extension named X." Implementing this would give us full namespaces and namespace imports.<br /> ** It's only ugly under the surface, though, and will only affect mod writers, and that rather minimally. The users just shove packages blindly into content/addons.<br /> *Online configuration of which extensions to use.<br /> *It would be nice to have an offline application for building extensions.<br /> *A more "self-aware" resource system should give us a much better handle on the remaining resource-related bugs.<br /> *Can we leverage this for improving save game formats?<br /> *Planet data is aliased in #defines and structure initializers when it should probably be in the resource map.<br /> *Ship data is *not* aliased, requiring a bunch of structure initializers that probably (though less probably than in the planet data case) should be name normalized.<br /> <br /> [[Category:About the Star Control series]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Content_Management&diff=26034 Content Management 2011-07-17T05:06:00Z

<p>Fossil: /* On Windows */</p> <hr /> <div>{{safe}}<br /> <br /> ==Introduction==<br /> The game still uses a virtual file system as before: see [[Content Management]] for information on this. However, starting in 0.6.4, the "layering" effect of the directory system is no longer used to index files for the purposes of regular addons. The concept of addon shadow packages was introduced in 0.6.6 as a stop-gap since the resource system is not yet finished.<br /> <br /> ==Hey, my remixes don't work!==<br /> <br /> UQM 0.6.4 (SVN revision 2869) changed addon pack mechanics incompatibly. Your remix zips are still OK, but you will need to perform these steps:<br /> <br /> * Move the addons directory from content/packages to content/<br /> * Download the appropriate .rmp files from http://sc2.sourceforge.net/remix-rmp/ and put them in the same directory as the remix zips.<br /> * Ensure that the remix directory is, in fact, addons/remix.<br /> <br /> ==Detailed description==<br /> <br /> Still needs to be done.<br /> <br /> ==A typical layout==<br /> <br /> ===On Windows===<br /> A typical The Ur-Quan Masters installation on Windows looks like this:<br /> <code><br /> C:\Program Files\The Ur-Quan Masters\uqm.exe<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.7.0-content.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-0.7.0-3domusic.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-0.7.0-voice.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc1.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc2.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\uqm-remix-disc3.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\version<br /> </code><br /> <br /> ===On Mac OS X===<br /> A typical The Ur-Quan Masters installation on Mac OS X looks like this:<br /> <code><br /> /Applications/The Ur-Quan Masters/Contents/PkgInfo<br /> /Applications/The Ur-Quan Masters/Contents/Info.plist<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Ogg.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL_image.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Vorbis.framework<br /> /Applications/The Ur-Quan Masters/Contents/MacOS/The Ur-Quan Masters<br /> /Applications/The Ur-Quan Masters/Contents/Resources/The Ur-Quan Masters.icns<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/version<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.7.0-content.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-0.7.0-voice.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc1.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc2.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc3.uqm<br /> </code><br /> <br /> ===On Linux===<br /> A typical The Ur-Quan Masters installation on Linux looks like this:<br /> <code><br /> /usr/local/bin/uqm (wrapper script)<br /> /usr/local/lib/uqm/uqm (the actual executable)<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-content.uqm<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-3domusic.uqm<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-voice.uqm<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack1.zip<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack2.zip<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack3.zip<br /> /usr/local/share/uqm/content/addons/remix/remix1.rmp<br /> /usr/local/share/uqm/content/addons/remix/remix2.rmp<br /> /usr/local/share/uqm/content/addons/remix/remix3.rmp<br /> /usr/local/share/uqm/content/version<br /> </code><br /> <br /> ==Content directories==<br /> The following list shows which directories are mounted in the game in 0.7. The later mentioned ones are mounted on top of the earlier mentioned ones.<br /> {|border=1<br /> !Directory!!Mounted on!!flags<br /> |-<br /> |[[#Default packages|default packages]], in alphabetic order||/ ||read-only<br /> |-<br /> |[[#Add-on packages|add-on packages]], in alphabetic order ||/addons/[name] ||read-only<br /> |-<br /> |[[#Content base directory|content base directory]] ||/ ||read-only<br /> |-<br /> |[[#Add-on shadow packages|add-on shadow packages]], in specified order ||/ ||read-only<br /> |-<br /> |[[#User data directory|user data directory]] ||/ ||read-write<br /> |-<br /> |[[#Temporary directory|temporary directory]] ||/tmp||read-write<br /> |}<br /> Note that addon packages are now mounted in their own tree branches, with one exception. The only way to override (or ''shadow'') the content is with an add-on shadow package. This is necessary in cases like extending fonts or supplying different menu keys because the resource system is not yet finished.<br /> <br /> ==Add-on layout==<br /> This is better illustrated with an example:<br /> <code><br /> addons/lang-russian/russian.zip<br /> addons/lang-russian/shadow-content/russian-shadow.zip<br /> </code><br /> Where ''russian.zip'' contains:<br /> <code><br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /addons/lang-russian/russian.rmp<br /> /addons/lang-russian/comm/commander.txt<br /> /addons/lang-russian/comm/arilou.txt<br /> [etc.]<br /> </code><br /> <br /> And ''russian-shadow.zip'' contains:<br /> <code><br /> base/fonts/micro.fon/<br /> base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /base/fonts/micro.fon/<br /> /base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> <br /> Addon ''shadow-content'' directory '''must''' contain .zip (or .uqm) files. Only zipped files will be mounted under the root directory. This means that in order to create a single zipped addon file with shadow content, you have to put a zip inside a zip. In that case, it may be a good idea to zip the shadow content with method ''store'' (no compression) in order to improve the in-game performance. A single ''russian.zip'' package would then look like this:<br /> <code><br /> shadow-content/russian-shadow.zip<br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> <br /> ==Current Development Status==<br /> <br /> The resource system (and thus the content directory) are in flux as the development team works on implementing a new resource system. This should remove a lot of the more brittle components from the legacy system and make addons easier to add, and mods to the source easier to make work. Detailed goals, milestones, and comments are in this section.<br /> <br /> ===Top-Level Roadmap===<br /> <br /> This actually may migrate over time as we see what works and what doesn't, but it will at least mark where we've been and where we think we're going.<br /> <br /> # Implement a generic string-based key-to-value system for doing resource lookups. ''Completed in Revision 1916.''<br /> # Drop requirement on binary resource indices by translating them to text. ''Completed in Revision 2003.''<br /> # Replace the integer-based resource system with string-based key mappings that are easier to extend. ''Completed in Revision 2963.''<br /> # Rework resource types to allow for a wider range of resources. Migrate all 3DO content into standalone addon packs. ''Completed in Revision 3104.''<br /> # Uniform API for all uses of the resource-map system, merging about six redundant subsystems into one. ''In progress.''<br /> <br /> ===Current goals===<br /> <br /> It's now feasible to start moving hardcoded data like the starship constants and the starmap itself into .rmp files. It's not clear how much of this is wise for 0.7.0 itself, but we should probably do at least a ''little'' to gather interest.<br /> <br /> * Keep user settings in a resource-map. ''Completed in Revision 1916.''<br /> * Keep key configuration in a resource-map. ''Completed in Revision 2705.''<br /> * Allow loads of resource files to be placed into isolated submaps to keep values separated. ''Completed in Revision 3105.''<br /> * Allow saves to strip some or all of the common prefix to save only the "submap" component. ''Completed in Revision 3105.''<br /> * Merge user settings and key configuration into the main resource map, eliminating the now-redundant mapres.c routines. ''Completed in Revision 3108.''<br /> * Turn melee data (teams, current situation) into resource maps like the other two.<br /> <br /> ===Other work===<br /> <br /> This is a bit more nebulous since we haven't advanced far enough to see what's a good idea and what isn't.<br /> <br /> *Massive, cathartic violence against the content directory structure, ending in convenient subprojects. ''Incomplete, but started in revision 2870.''<br /> *Let .rmp files include other ones to make uqm.rmp less monolithic. This could also be used to automatically include addon packs (such as, say, a Cyrillic Font Pack) if necessary.<br /> **At the moment we just load all .rmp files in any given directory. This may be good enough.<br /> *The hack to make the remix packs work is kind of ugly. A more permanent fix would allow special variable expansion to map to wherever uio elected to put it, giving each extension its own space for files. Best of all would be a magic variable for "The home of the extension named X." Implementing this would give us full namespaces and namespace imports.<br /> ** It's only ugly under the surface, though, and will only affect mod writers, and that rather minimally. The users just shove packages blindly into content/addons.<br /> *Online configuration of which extensions to use.<br /> *It would be nice to have an offline application for building extensions.<br /> *A more "self-aware" resource system should give us a much better handle on the remaining resource-related bugs.<br /> *Can we leverage this for improving save game formats?<br /> *Planet data is aliased in #defines and structure initializers when it should probably be in the resource map.<br /> *Ship data is *not* aliased, requiring a bunch of structure initializers that probably (though less probably than in the planet data case) should be name normalized.<br /> <br /> [[Category:About the Star Control series]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Content_Management&diff=26033 Content Management 2011-07-17T05:04:56Z

<p>Fossil: /* On Mac OS X */</p> <hr /> <div>{{safe}}<br /> <br /> ==Introduction==<br /> The game still uses a virtual file system as before: see [[Content Management]] for information on this. However, starting in 0.6.4, the "layering" effect of the directory system is no longer used to index files for the purposes of regular addons. The concept of addon shadow packages was introduced in 0.6.6 as a stop-gap since the resource system is not yet finished.<br /> <br /> ==Hey, my remixes don't work!==<br /> <br /> UQM 0.6.4 (SVN revision 2869) changed addon pack mechanics incompatibly. Your remix zips are still OK, but you will need to perform these steps:<br /> <br /> * Move the addons directory from content/packages to content/<br /> * Download the appropriate .rmp files from http://sc2.sourceforge.net/remix-rmp/ and put them in the same directory as the remix zips.<br /> * Ensure that the remix directory is, in fact, addons/remix.<br /> <br /> ==Detailed description==<br /> <br /> Still needs to be done.<br /> <br /> ==A typical layout==<br /> <br /> ===On Windows===<br /> A typical The Ur-Quan Masters installation on Windows looks like this:<br /> <code><br /> C:\Program Files\The Ur-Quan Masters\uqm.exe<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-content.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-3domusic.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-voice.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\uqm-remix-pack1.zip<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\uqm-remix-pack2.zip<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\uqm-remix-pack3.zip<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\remix1.rmp<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\remix2.rmp<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\remix3.rmp<br /> C:\Program Files\The Ur-Quan Masters\content\version<br /> </code><br /> <br /> ===On Mac OS X===<br /> A typical The Ur-Quan Masters installation on Mac OS X looks like this:<br /> <code><br /> /Applications/The Ur-Quan Masters/Contents/PkgInfo<br /> /Applications/The Ur-Quan Masters/Contents/Info.plist<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Ogg.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL_image.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Vorbis.framework<br /> /Applications/The Ur-Quan Masters/Contents/MacOS/The Ur-Quan Masters<br /> /Applications/The Ur-Quan Masters/Contents/Resources/The Ur-Quan Masters.icns<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/version<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.7.0-content.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-0.7.0-voice.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc1.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc2.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/uqm-remix-disc3.uqm<br /> </code><br /> <br /> ===On Linux===<br /> A typical The Ur-Quan Masters installation on Linux looks like this:<br /> <code><br /> /usr/local/bin/uqm (wrapper script)<br /> /usr/local/lib/uqm/uqm (the actual executable)<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-content.uqm<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-3domusic.uqm<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-voice.uqm<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack1.zip<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack2.zip<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack3.zip<br /> /usr/local/share/uqm/content/addons/remix/remix1.rmp<br /> /usr/local/share/uqm/content/addons/remix/remix2.rmp<br /> /usr/local/share/uqm/content/addons/remix/remix3.rmp<br /> /usr/local/share/uqm/content/version<br /> </code><br /> <br /> ==Content directories==<br /> The following list shows which directories are mounted in the game in 0.7. The later mentioned ones are mounted on top of the earlier mentioned ones.<br /> {|border=1<br /> !Directory!!Mounted on!!flags<br /> |-<br /> |[[#Default packages|default packages]], in alphabetic order||/ ||read-only<br /> |-<br /> |[[#Add-on packages|add-on packages]], in alphabetic order ||/addons/[name] ||read-only<br /> |-<br /> |[[#Content base directory|content base directory]] ||/ ||read-only<br /> |-<br /> |[[#Add-on shadow packages|add-on shadow packages]], in specified order ||/ ||read-only<br /> |-<br /> |[[#User data directory|user data directory]] ||/ ||read-write<br /> |-<br /> |[[#Temporary directory|temporary directory]] ||/tmp||read-write<br /> |}<br /> Note that addon packages are now mounted in their own tree branches, with one exception. The only way to override (or ''shadow'') the content is with an add-on shadow package. This is necessary in cases like extending fonts or supplying different menu keys because the resource system is not yet finished.<br /> <br /> ==Add-on layout==<br /> This is better illustrated with an example:<br /> <code><br /> addons/lang-russian/russian.zip<br /> addons/lang-russian/shadow-content/russian-shadow.zip<br /> </code><br /> Where ''russian.zip'' contains:<br /> <code><br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /addons/lang-russian/russian.rmp<br /> /addons/lang-russian/comm/commander.txt<br /> /addons/lang-russian/comm/arilou.txt<br /> [etc.]<br /> </code><br /> <br /> And ''russian-shadow.zip'' contains:<br /> <code><br /> base/fonts/micro.fon/<br /> base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /base/fonts/micro.fon/<br /> /base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> <br /> Addon ''shadow-content'' directory '''must''' contain .zip (or .uqm) files. Only zipped files will be mounted under the root directory. This means that in order to create a single zipped addon file with shadow content, you have to put a zip inside a zip. In that case, it may be a good idea to zip the shadow content with method ''store'' (no compression) in order to improve the in-game performance. A single ''russian.zip'' package would then look like this:<br /> <code><br /> shadow-content/russian-shadow.zip<br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> <br /> ==Current Development Status==<br /> <br /> The resource system (and thus the content directory) are in flux as the development team works on implementing a new resource system. This should remove a lot of the more brittle components from the legacy system and make addons easier to add, and mods to the source easier to make work. Detailed goals, milestones, and comments are in this section.<br /> <br /> ===Top-Level Roadmap===<br /> <br /> This actually may migrate over time as we see what works and what doesn't, but it will at least mark where we've been and where we think we're going.<br /> <br /> # Implement a generic string-based key-to-value system for doing resource lookups. ''Completed in Revision 1916.''<br /> # Drop requirement on binary resource indices by translating them to text. ''Completed in Revision 2003.''<br /> # Replace the integer-based resource system with string-based key mappings that are easier to extend. ''Completed in Revision 2963.''<br /> # Rework resource types to allow for a wider range of resources. Migrate all 3DO content into standalone addon packs. ''Completed in Revision 3104.''<br /> # Uniform API for all uses of the resource-map system, merging about six redundant subsystems into one. ''In progress.''<br /> <br /> ===Current goals===<br /> <br /> It's now feasible to start moving hardcoded data like the starship constants and the starmap itself into .rmp files. It's not clear how much of this is wise for 0.7.0 itself, but we should probably do at least a ''little'' to gather interest.<br /> <br /> * Keep user settings in a resource-map. ''Completed in Revision 1916.''<br /> * Keep key configuration in a resource-map. ''Completed in Revision 2705.''<br /> * Allow loads of resource files to be placed into isolated submaps to keep values separated. ''Completed in Revision 3105.''<br /> * Allow saves to strip some or all of the common prefix to save only the "submap" component. ''Completed in Revision 3105.''<br /> * Merge user settings and key configuration into the main resource map, eliminating the now-redundant mapres.c routines. ''Completed in Revision 3108.''<br /> * Turn melee data (teams, current situation) into resource maps like the other two.<br /> <br /> ===Other work===<br /> <br /> This is a bit more nebulous since we haven't advanced far enough to see what's a good idea and what isn't.<br /> <br /> *Massive, cathartic violence against the content directory structure, ending in convenient subprojects. ''Incomplete, but started in revision 2870.''<br /> *Let .rmp files include other ones to make uqm.rmp less monolithic. This could also be used to automatically include addon packs (such as, say, a Cyrillic Font Pack) if necessary.<br /> **At the moment we just load all .rmp files in any given directory. This may be good enough.<br /> *The hack to make the remix packs work is kind of ugly. A more permanent fix would allow special variable expansion to map to wherever uio elected to put it, giving each extension its own space for files. Best of all would be a magic variable for "The home of the extension named X." Implementing this would give us full namespaces and namespace imports.<br /> ** It's only ugly under the surface, though, and will only affect mod writers, and that rather minimally. The users just shove packages blindly into content/addons.<br /> *Online configuration of which extensions to use.<br /> *It would be nice to have an offline application for building extensions.<br /> *A more "self-aware" resource system should give us a much better handle on the remaining resource-related bugs.<br /> *Can we leverage this for improving save game formats?<br /> *Planet data is aliased in #defines and structure initializers when it should probably be in the resource map.<br /> *Ship data is *not* aliased, requiring a bunch of structure initializers that probably (though less probably than in the planet data case) should be name normalized.<br /> <br /> [[Category:About the Star Control series]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Content_Management&diff=23226 Content Management 2009-07-09T22:28:45Z

<p>Fossil: /* Content directories */</p> <hr /> <div>{{safe}}<br /> <br /> ==Introduction==<br /> The game still uses a virtual file system as before: see [[Content Management]] for information on this. However, starting in 0.6.4, the "layering" effect of the directory system is no longer used to index files for the purposes of regular addons. The concept of addon shadow packages was introduced in 0.6.6 as a stop-gap since the resource system is not yet finished.<br /> <br /> ==Hey, my remixes don't work!==<br /> <br /> UQM 0.6.4 (SVN revision 2869) changed addon pack mechanics incompatibly. Your remix zips are still OK, but you will need to perform these steps:<br /> <br /> * Move the addons directory from content/packages to content/<br /> * Download the appropriate .rmp files from http://sc2.sourceforge.net/remix-rmp/ and put them in the same directory as the remix zips.<br /> * Ensure that the remix directory is, in fact, addons/remix.<br /> <br /> ==Detailed description==<br /> <br /> Still needs to be done.<br /> <br /> ==A typical layout==<br /> <br /> ===On Windows===<br /> A typical The Ur-Quan Masters installation on Windows looks like this:<br /> <code><br /> C:\Program Files\The Ur-Quan Masters\uqm.exe<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-content.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-3domusic.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-voice.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\uqm-remix-pack1.zip<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\uqm-remix-pack2.zip<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\uqm-remix-pack3.zip<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\remix1.rmp<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\remix2.rmp<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\remix3.rmp<br /> C:\Program Files\The Ur-Quan Masters\content\version<br /> </code><br /> <br /> ===On Mac OS X===<br /> A typical The Ur-Quan Masters installation on Mac OS X looks like this:<br /> <code><br /> /Applications/The Ur-Quan Masters/Contents/PkgInfo<br /> /Applications/The Ur-Quan Masters/Contents/Info.plist<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Ogg.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL_image.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Vorbis.framework<br /> /Applications/The Ur-Quan Masters/Contents/MacOS/The Ur-Quan Masters<br /> /Applications/The Ur-Quan Masters/Contents/Resources/The Ur-Quan Masters.icns<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/version<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.6.0-content.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.6.0-voice.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/uqm-remix-pack1.zip<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/uqm-remix-pack1.zip<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/uqm-remix-pack1.zip<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/remix1.rmp<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/remix2.rmp<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/remix3.rmp<br /> </code><br /> <br /> ===On Linux===<br /> A typical The Ur-Quan Masters installation on Linux looks like this:<br /> <code><br /> /usr/local/bin/uqm (wrapper script)<br /> /usr/local/lib/uqm/uqm (the actual executable)<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-content.uqm<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-3domusic.uqm<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-voice.uqm<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack1.zip<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack2.zip<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack3.zip<br /> /usr/local/share/uqm/content/addons/remix/remix1.rmp<br /> /usr/local/share/uqm/content/addons/remix/remix2.rmp<br /> /usr/local/share/uqm/content/addons/remix/remix3.rmp<br /> /usr/local/share/uqm/content/version<br /> </code><br /> <br /> ==Content directories==<br /> The following list shows which directories are mounted in the game in 0.7. The later mentioned ones are mounted on top of the earlier mentioned ones.<br /> {|border=1<br /> !Directory!!Mounted on!!flags<br /> |-<br /> |[[#Default packages|default packages]], in alphabetic order||/ ||read-only<br /> |-<br /> |[[#Add-on packages|add-on packages]], in alphabetic order ||/addons/[name] ||read-only<br /> |-<br /> |[[#Content base directory|content base directory]] ||/ ||read-only<br /> |-<br /> |[[#Add-on shadow packages|add-on shadow packages]], in specified order ||/ ||read-only<br /> |-<br /> |[[#User data directory|user data directory]] ||/ ||read-write<br /> |-<br /> |[[#Temporary directory|temporary directory]] ||/tmp||read-write<br /> |}<br /> Note that addon packages are now mounted in their own tree branches, with one exception. The only way to override (or ''shadow'') the content is with an add-on shadow package. This is necessary in cases like extending fonts or supplying different menu keys because the resource system is not yet finished.<br /> <br /> ==Add-on layout==<br /> This is better illustrated with an example:<br /> <code><br /> addons/lang-russian/russian.zip<br /> addons/lang-russian/shadow-content/russian-shadow.zip<br /> </code><br /> Where ''russian.zip'' contains:<br /> <code><br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /addons/lang-russian/russian.rmp<br /> /addons/lang-russian/comm/commander.txt<br /> /addons/lang-russian/comm/arilou.txt<br /> [etc.]<br /> </code><br /> <br /> And ''russian-shadow.zip'' contains:<br /> <code><br /> base/fonts/micro.fon/<br /> base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /base/fonts/micro.fon/<br /> /base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> <br /> Addon ''shadow-content'' directory '''must''' contain .zip (or .uqm) files. Only zipped files will be mounted under the root directory. This means that in order to create a single zipped addon file with shadow content, you have to put a zip inside a zip. In that case, it may be a good idea to zip the shadow content with method ''store'' (no compression) in order to improve the in-game performance. A single ''russian.zip'' package would then look like this:<br /> <code><br /> shadow-content/russian-shadow.zip<br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> <br /> ==Current Development Status==<br /> <br /> The resource system (and thus the content directory) are in flux as the development team works on implementing a new resource system. This should remove a lot of the more brittle components from the legacy system and make addons easier to add, and mods to the source easier to make work. Detailed goals, milestones, and comments are in this section.<br /> <br /> ===Top-Level Roadmap===<br /> <br /> This actually may migrate over time as we see what works and what doesn't, but it will at least mark where we've been and where we think we're going.<br /> <br /> # Implement a generic string-based key-to-value system for doing resource lookups. ''Completed in Revision 1916.''<br /> # Drop requirement on binary resource indices by translating them to text. ''Completed in Revision 2003.''<br /> # Replace the integer-based resource system with string-based key mappings that are easier to extend. ''Completed in Revision 2963.''<br /> # Rework resource types to allow for a wider range of resources. Migrate all 3DO content into standalone addon packs. ''Completed in Revision 3104.''<br /> # Uniform API for all uses of the resource-map system, merging about six redundant subsystems into one. ''In progress.''<br /> <br /> ===Current goals===<br /> <br /> It's now feasible to start moving hardcoded data like the starship constants and the starmap itself into .rmp files. It's not clear how much of this is wise for 0.7.0 itself, but we should probably do at least a ''little'' to gather interest.<br /> <br /> * Keep user settings in a resource-map. ''Completed in Revision 1916.''<br /> * Keep key configuration in a resource-map. ''Completed in Revision 2705.''<br /> * Allow loads of resource files to be placed into isolated submaps to keep values separated. ''Completed in Revision 3105.''<br /> * Allow saves to strip some or all of the common prefix to save only the "submap" component. ''Completed in Revision 3105.''<br /> * Merge user settings and key configuration into the main resource map, eliminating the now-redundant mapres.c routines. ''Completed in Revision 3108.''<br /> * Turn melee data (teams, current situation) into resource maps like the other two.<br /> <br /> ===Other work===<br /> <br /> This is a bit more nebulous since we haven't advanced far enough to see what's a good idea and what isn't.<br /> <br /> *Massive, cathartic violence against the content directory structure, ending in convenient subprojects. ''Incomplete, but started in revision 2870.''<br /> *Let .rmp files include other ones to make uqm.rmp less monolithic. This could also be used to automatically include addon packs (such as, say, a Cyrillic Font Pack) if necessary.<br /> **At the moment we just load all .rmp files in any given directory. This may be good enough.<br /> *The hack to make the remix packs work is kind of ugly. A more permanent fix would allow special variable expansion to map to wherever uio elected to put it, giving each extension its own space for files. Best of all would be a magic variable for "The home of the extension named X." Implementing this would give us full namespaces and namespace imports.<br /> ** It's only ugly under the surface, though, and will only affect mod writers, and that rather minimally. The users just shove packages blindly into content/addons.<br /> *Online configuration of which extensions to use.<br /> *It would be nice to have an offline application for building extensions.<br /> *A more "self-aware" resource system should give us a much better handle on the remaining resource-related bugs.<br /> *Can we leverage this for improving save game formats?<br /> *Planet data is aliased in #defines and structure initializers when it should probably be in the resource map.<br /> *Ship data is *not* aliased, requiring a bunch of structure initializers that probably (though less probably than in the planet data case) should be name normalized.<br /> <br /> [[Category:About the Star Control series]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Content_Management&diff=23225 Content Management 2009-07-09T22:26:54Z

<p>Fossil: </p> <hr /> <div>{{safe}}<br /> <br /> ==Introduction==<br /> The game still uses a virtual file system as before: see [[Content Management]] for information on this. However, starting in 0.6.4, the "layering" effect of the directory system is no longer used to index files for the purposes of regular addons. The concept of addon shadow packages was introduced in 0.6.6 as a stop-gap since the resource system is not yet finished.<br /> <br /> ==Hey, my remixes don't work!==<br /> <br /> UQM 0.6.4 (SVN revision 2869) changed addon pack mechanics incompatibly. Your remix zips are still OK, but you will need to perform these steps:<br /> <br /> * Move the addons directory from content/packages to content/<br /> * Download the appropriate .rmp files from http://sc2.sourceforge.net/remix-rmp/ and put them in the same directory as the remix zips.<br /> * Ensure that the remix directory is, in fact, addons/remix.<br /> <br /> ==Detailed description==<br /> <br /> Still needs to be done.<br /> <br /> ==A typical layout==<br /> <br /> ===On Windows===<br /> A typical The Ur-Quan Masters installation on Windows looks like this:<br /> <code><br /> C:\Program Files\The Ur-Quan Masters\uqm.exe<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-content.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-3domusic.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-voice.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\uqm-remix-pack1.zip<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\uqm-remix-pack2.zip<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\uqm-remix-pack3.zip<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\remix1.rmp<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\remix2.rmp<br /> C:\Program Files\The Ur-Quan Masters\content\addons\remix\remix3.rmp<br /> C:\Program Files\The Ur-Quan Masters\content\version<br /> </code><br /> <br /> ===On Mac OS X===<br /> A typical The Ur-Quan Masters installation on Mac OS X looks like this:<br /> <code><br /> /Applications/The Ur-Quan Masters/Contents/PkgInfo<br /> /Applications/The Ur-Quan Masters/Contents/Info.plist<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Ogg.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL_image.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Vorbis.framework<br /> /Applications/The Ur-Quan Masters/Contents/MacOS/The Ur-Quan Masters<br /> /Applications/The Ur-Quan Masters/Contents/Resources/The Ur-Quan Masters.icns<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/version<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.6.0-content.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.6.0-voice.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/uqm-remix-pack1.zip<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/uqm-remix-pack1.zip<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/uqm-remix-pack1.zip<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/remix1.rmp<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/remix2.rmp<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/addons/remix/remix3.rmp<br /> </code><br /> <br /> ===On Linux===<br /> A typical The Ur-Quan Masters installation on Linux looks like this:<br /> <code><br /> /usr/local/bin/uqm (wrapper script)<br /> /usr/local/lib/uqm/uqm (the actual executable)<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-content.uqm<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-3domusic.uqm<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-voice.uqm<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack1.zip<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack2.zip<br /> /usr/local/share/uqm/content/addons/remix/uqm-remix-pack3.zip<br /> /usr/local/share/uqm/content/addons/remix/remix1.rmp<br /> /usr/local/share/uqm/content/addons/remix/remix2.rmp<br /> /usr/local/share/uqm/content/addons/remix/remix3.rmp<br /> /usr/local/share/uqm/content/version<br /> </code><br /> <br /> ==Content directories==<br /> The following list shows which directories are mounted in the game in 0.7. The later mentioned ones are mounted on top of the earlier mentioned ones.<br /> {|border=1<br /> !Directory!!Mounted on!!flags<br /> |-<br /> |[[#Default packages|default packages]], in alphabetic order||/ ||read-only<br /> |-<br /> |[[#Add-on packages|add-on packages]], in alphabetic order ||/addons/[name] ||read-only<br /> |-<br /> |[[#Content base directory|content base directory]] ||/ ||read-only<br /> |-<br /> |[[#Add-on shadow packages|add-on shadow packages]], in alphabetic order ||/ ||read-only<br /> |-<br /> |[[#User data directory|user data directory]] ||/ ||read-write<br /> |-<br /> |[[#Temporary directory|temporary directory]] ||/tmp||read-write<br /> |}<br /> Note that addon packages are now mounted in their own tree branches, with one exception. The only way to override (or ''shadow'') the content is with an add-on shadow package. This is necessary in cases like extending fonts or supplying different menu keys because the resource system is not yet finished.<br /> <br /> ==Add-on layout==<br /> This is better illustrated with an example:<br /> <code><br /> addons/lang-russian/russian.zip<br /> addons/lang-russian/shadow-content/russian-shadow.zip<br /> </code><br /> Where ''russian.zip'' contains:<br /> <code><br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /addons/lang-russian/russian.rmp<br /> /addons/lang-russian/comm/commander.txt<br /> /addons/lang-russian/comm/arilou.txt<br /> [etc.]<br /> </code><br /> <br /> And ''russian-shadow.zip'' contains:<br /> <code><br /> base/fonts/micro.fon/<br /> base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> and is mounted like so:<br /> <code><br /> /base/fonts/micro.fon/<br /> /base/fonts/player.fon/<br /> [etc.]<br /> </code><br /> <br /> Addon ''shadow-content'' directory '''must''' contain .zip (or .uqm) files. Only zipped files will be mounted under the root directory. This means that in order to create a single zipped addon file with shadow content, you have to put a zip inside a zip. In that case, it may be a good idea to zip the shadow content with method ''store'' (no compression) in order to improve the in-game performance. A single ''russian.zip'' package would then look like this:<br /> <code><br /> shadow-content/russian-shadow.zip<br /> russian.rmp<br /> comm/commander.txt<br /> comm/arilou.txt<br /> [etc., files with layout of author's choosing]<br /> </code><br /> <br /> ==Current Development Status==<br /> <br /> The resource system (and thus the content directory) are in flux as the development team works on implementing a new resource system. This should remove a lot of the more brittle components from the legacy system and make addons easier to add, and mods to the source easier to make work. Detailed goals, milestones, and comments are in this section.<br /> <br /> ===Top-Level Roadmap===<br /> <br /> This actually may migrate over time as we see what works and what doesn't, but it will at least mark where we've been and where we think we're going.<br /> <br /> # Implement a generic string-based key-to-value system for doing resource lookups. ''Completed in Revision 1916.''<br /> # Drop requirement on binary resource indices by translating them to text. ''Completed in Revision 2003.''<br /> # Replace the integer-based resource system with string-based key mappings that are easier to extend. ''Completed in Revision 2963.''<br /> # Rework resource types to allow for a wider range of resources. Migrate all 3DO content into standalone addon packs. ''Completed in Revision 3104.''<br /> # Uniform API for all uses of the resource-map system, merging about six redundant subsystems into one. ''In progress.''<br /> <br /> ===Current goals===<br /> <br /> It's now feasible to start moving hardcoded data like the starship constants and the starmap itself into .rmp files. It's not clear how much of this is wise for 0.7.0 itself, but we should probably do at least a ''little'' to gather interest.<br /> <br /> * Keep user settings in a resource-map. ''Completed in Revision 1916.''<br /> * Keep key configuration in a resource-map. ''Completed in Revision 2705.''<br /> * Allow loads of resource files to be placed into isolated submaps to keep values separated. ''Completed in Revision 3105.''<br /> * Allow saves to strip some or all of the common prefix to save only the "submap" component. ''Completed in Revision 3105.''<br /> * Merge user settings and key configuration into the main resource map, eliminating the now-redundant mapres.c routines. ''Completed in Revision 3108.''<br /> * Turn melee data (teams, current situation) into resource maps like the other two.<br /> <br /> ===Other work===<br /> <br /> This is a bit more nebulous since we haven't advanced far enough to see what's a good idea and what isn't.<br /> <br /> *Massive, cathartic violence against the content directory structure, ending in convenient subprojects. ''Incomplete, but started in revision 2870.''<br /> *Let .rmp files include other ones to make uqm.rmp less monolithic. This could also be used to automatically include addon packs (such as, say, a Cyrillic Font Pack) if necessary.<br /> **At the moment we just load all .rmp files in any given directory. This may be good enough.<br /> *The hack to make the remix packs work is kind of ugly. A more permanent fix would allow special variable expansion to map to wherever uio elected to put it, giving each extension its own space for files. Best of all would be a magic variable for "The home of the extension named X." Implementing this would give us full namespaces and namespace imports.<br /> ** It's only ugly under the surface, though, and will only affect mod writers, and that rather minimally. The users just shove packages blindly into content/addons.<br /> *Online configuration of which extensions to use.<br /> *It would be nice to have an offline application for building extensions.<br /> *A more "self-aware" resource system should give us a much better handle on the remaining resource-related bugs.<br /> *Can we leverage this for improving save game formats?<br /> *Planet data is aliased in #defines and structure initializers when it should probably be in the resource map.<br /> *Ship data is *not* aliased, requiring a bunch of structure initializers that probably (though less probably than in the planet data case) should be name normalized.<br /> <br /> [[Category:About the Star Control series]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Content_Management_before_0.7.0&diff=23224 Content Management before 0.7.0 2009-07-09T18:44:12Z

<p>Fossil: /* Content directories */</p> <hr /> <div>:''Note: the information contained in this page pertains to the [[The Ur-Quan Masters]] versions 0.3 through 0.6.0. The content system is currently under revision: See [[Content Management in 0.7.0]] for details.<br /> <br /> {{safe}}<br /> <br /> ==Introduction==<br /> The game uses a virtual file system to access the content. Directories from various locations are combined ("mounted") to form one big file system, where files from a mounted directory are hidden if files with the same name exist on a directory mounted "on top" of it.<br /> A directory to be mounted may exist as an actual directory on the operating system's file system, or as a directory within a .zip or .uqm file. An .uqm file is internally a .zip file but with another name given, so that people won't accidentally unpack them.<br /> <br /> If a file exists in a directory which is mounted read-only, but not in a directory mounted read-write on top of it, then writing to the file will produce a copy in the latter directory.<br /> <br /> Whether file name matching is case-sensitive or not depends on the file system of each layer. Files in .zip files are always matched case-sensitively, while files outside of .zip files are matched as normal for the operating system UQM is run on.<br /> <br /> ==Content directories==<br /> The following list shows which directories are mounted in the game. The later mentioned ones are mounted on top of the earlier mentioned ones.<br /> {|border=1<br /> !Directory!!Mounted on!!flags<br /> |-<br /> |[[#Default packages|default packages]], in alphabetic order||/ ||read-only<br /> |-<br /> |[[#Add-on packages|add-on packages]], in alphabetic order ||/ ||read-only<br /> |-<br /> |[[#Content base directory|content base directory]] ||/ ||read-only<br /> |-<br /> |[[#User data directory|user data directory]] ||/ ||read-write<br /> |-<br /> |[[#Temporary directory|temporary directory]] ||/tmp||read-write<br /> |}<br /> <br /> You can see from this table that unzipped files always override zipped files. This means that using add-on packages to override unzipped base content won't work. This is one of the issues that will be addressed in a next release.<br /> <br /> ==Detailed description==<br /> <br /> ===Content base directory===<br /> This is the base directory where the content files are stored.<br /> It needs to contain a file named <code>version</code> with the UQM version number to be accepted by the game.<br /> In it, you'll usually find a directory <code>packages</code>, which contains the default packages, and indirectly the add-on packages (optionally). The add-on packages are kept in a directory <code>addons</code> within the <code>packages</code> directory.<br /> <br /> On Windows Systems the content base directory is located in the installation root directory, which can be specified by the user at installation time. Using the installation default <code>C:\Program Files\The Ur-Quan Masters\</code>, that would place the content directory in <code>C:\Program Files\The Ur-Quan Masters\content\</code>. The game tries the directory where it is started and the directory "content" within that dir as the content base directory.<br /> <br /> On Unix systems, the content directory may vary per packager. If you're building from source, you can specify the installation directory yourself. Per default, the content is stored in <code>lib/uqm/content/</code> in the specified installation prefix, which is <code>/usr/local/</code> per default.<br /> A wrapper script supplies the content dir location to the game.<br /> <br /> To override the default content directory, pass something like <code>--content-dir /path/to/content</code> to the game.<br /> <br /> ===Default packages===<br /> Default packages are .uqm files located in the directory <code>packages/</code> in the content directory. They are mounted automatically, in alphabetic order, with the later ones overriding the earlier ones.<br /> <br /> ===Add-on packages===<br /> Add-on packages are .uqm or .zip files located in subdirectories of <code>packages/addons/</code> in the content directory. If the <code>--addon</code> argument is passed to the game, the game will use the succeeding argument as the name of a subdirectory in <code>packages/addons/</code> from which additional packages will be loaded. The game will mount all the .zip/.uqm files in such a directory in alphabetic order, with the later ones overriding the earlier ones.<br /> The <code>--addon</code> argument can be supplied multiple times to include multiple add-on directories. They will be mounted in the order they are supplied, with the later ones overriding the earlier ones.<br /> <br /> Files in add-on packages will override files from the default packages.<br /> <br /> When creating add-on packages, make sure that the use of capitals in the file names matches what is expected. This is even important if a package is for use on Windows only; the matching of file names inside content files does not go through the operating system, and is case sensitive.<br /> <br /> ===User data directory===<br /> In the user data directory the user's key config, melee config, melee teams, and saved games are stored.<br /> <br /> On Unix systems (including Darwin/MacOS X) the user data directory is <code>~/.uqm/</code>.<br /> <br /> On English Windows systems, the user data directory is the directory <code>uqm</code> in the <code>Application Data</code> directory for the current user. The <code>Application Data</code> directory is usually in one of the following locations, and may be hidden:<br /> ; Windows 95, 98, SE without separate users : <code>C:\Windows\Application Data\</code><br /> ; Windows 95/98/SE with separate users : <code>C:\Windows\Profiles\YourName\Application Data\</code><br /> ; Windows NT/2k/XP : <code>C:\Documents and Settings\YourName\Application Data\</code><br /> <br /> On localized versions of Windows, these locations may differ. For instance, in the German version it would be "Anwendungsdaten", not "Application Data".<br /> <br /> ===Temporary directory===<br /> A temporary directory is used to store some data during the game. This was necessary in older versions of Star-Control, but on modern systems the memory involved is not worth it. It will be removed in a future version.<br /> <br /> The temporary directory for the game is a directory created in the operating system's default temporary directory. If an environment variable <code>TMP</code> or <code>TEMP</code> is set, that will be where the temporary directory for the game will be created, otherwise a directory <code>/tmp/</code> will be used if that exist. If that directory doesn't exist either, a directory is created in the current working directory.<br /> <br /> ==A typical layout==<br /> <br /> ===On Mac OS X===<br /> A typical The Ur-Quan Masters installation on Mac OS X looks like this:<br /> <code><br /> /Applications/The Ur-Quan Masters/Contents/PkgInfo<br /> /Applications/The Ur-Quan Masters/Contents/Info.plist<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Ogg.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL_image.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/SDL.framework<br /> /Applications/The Ur-Quan Masters/Contents/Frameworks/Vorbis.framework<br /> /Applications/The Ur-Quan Masters/Contents/MacOS/The Ur-Quan Masters<br /> /Applications/The Ur-Quan Masters/Contents/Resources/The Ur-Quan Masters.icns<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/version<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.6.0-content.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/uqm-0.6.0-voice.uqm<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/addons/remix/uqm-remix-pack1.zip<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/addons/remix/uqm-remix-pack2.zip<br /> /Applications/The Ur-Quan Masters/Contents/Resources/content/packages/addons/remix/uqm-remix-pack3.zip<br /> </code><br /> <br /> ===On Windows===<br /> A typical The Ur-Quan Masters installation on Windows looks like this:<br /> <code><br /> C:\Program Files\The Ur-Quan Masters\uqm.exe<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-content.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-3domusic.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\packages\uqm-0.6.0-voice.uqm<br /> C:\Program Files\The Ur-Quan Masters\content\packages\addons\remix\uqm-remix-pack1.zip<br /> C:\Program Files\The Ur-Quan Masters\content\packages\addons\remix\uqm-remix-pack2.zip<br /> C:\Program Files\The Ur-Quan Masters\content\packages\addons\remix\uqm-remix-pack3.zip<br /> C:\Program Files\The Ur-Quan Masters\content\version<br /> </code><br /> <br /> ===On Linux===<br /> A typical The Ur-Quan Masters installation on Linux looks like this:<br /> <code><br /> /usr/local/bin/uqm (wrapper script)<br /> /usr/local/lib/uqm/uqm (the actual executable)<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-content.uqm<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-3domusic.uqm<br /> /usr/local/share/uqm/content/packages/uqm-0.6.0-voice.uqm<br /> /usr/local/share/uqm/content/packages/addons/remix/uqm-remix-pack1.zip<br /> /usr/local/share/uqm/content/packages/addons/remix/uqm-remix-pack2.zip<br /> /usr/local/share/uqm/content/packages/addons/remix/uqm-remix-pack3.zip<br /> /usr/local/share/uqm/content/version<br /> </code><br /> <br /> [[Category:About the Star Control series]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Netplay_howto&diff=14043 Netplay howto 2006-11-03T09:17:17Z

<p>Fossil: /* Caveats */</p> <hr /> <div>This page describes how to play [[SuperMelee]] in [[The Ur-Quan Masters]] over a network. Take your time and read it thoroughly; every word is there for a reason.<br /> <br /> __TOC__<br /> <br /> <br /> ==Installing a network-capable version of The Ur-Quan Masters==<br /> Netplay is still in the testing phase, and there hasn't been a release yet which includes netplay. So to play netplay, you need the more recent developer sources. If you know how to compile the game yourself, you can just download the [http://sourceforge.net/cvs/?group_id=59452 latest sources from CVS] and compile as usual.<br /> <br /> If you're a Windows user, there is an easier way to go:<br /> #First, install the [http://sc2.sourceforge.net/downloads.php 0.5.0 release] of the game as normally. Do not install any melee-altering add-on packs unless your opponent has them installed too. Otherwise the two parties would lose synchronisation and the game would be aborted. Audio packs should be ok though.<br /> #From the [http://uqm.stack.nl/files/snapshots/ CVS snapshots page] download the latest precompiled binary (either release or debug; the debug version may give more information to help the developers if a bug occurs; the release version will be faster), as well as the latest content update.<br /> #Unpack the downloaded file (you will need a program such as [http://www.winzip.com/ WinZip] for this). You will end up with an <code>uqm.exe</code> or <code>uqm-debug.exe</code> file.<br /> #Find the <code>uqm.exe</code> file that came with 0.5.0, and replace it by the extracted .exe file (if you have <code>uqm-debug.exe</code> rename it to <code>uqm.exe</code>). If you installed The Ur-Quan Masters in the default location, you'll find it in <code>C:\Program Files\The Ur-Quan Masters\</code>).<br /> #In the folder where you found the <code>uqm.exe</code> file, there's another folder named <code>packages</code>, which contains the file <code>uqm-0.5.0-content.uqm</code> (and possibly other .uqm files for alternative music). Put the downloaded content update .zip file in here. '''DO NOT UNPACK THIS FILE!'''. The game knows how to read the files from inside the archive.<br /> If you later want to upgrade, just remove the old content upgrade .zip file and redo steps 2 and onwards.<br /> <br /> ==Setting up the network==<br /> <br /> Network experts can skip to the section "Settings Summary". For the others, read on, everything will be explained.<br /> <br /> ===Introduction===<br /> ====Network basics====<br /> Every computer on the internet has an ''internet address'', consisting of 4 numbers seperated by periods, like <code>131.155.140.133</code>. Information sent over the internet is split up in ''packets'', each packet labeled with the destination address.<br /> <br /> A computer may also have a ''host name'', like <code>uqm.stack.nl</code>, to make refering to it a bit easier to read for humans. When information needs to be sent to a computer known only by host name, its address will first be looked up.<br /> <br /> A computer may run many programs simultaneously which want to receive information from over the network. To direct packets to the correct program, the address will include a number known as the ''port number'' or ''port'' for short. The Ur-Quan Masters accepts packets sent to port ''21837''.<br /> <br /> ====Router basics====<br /> The little box which comes with most modern internet subscriptions is a ''router''. A router is a device which passes packets to other computer.<br /> <br /> Several computer may be connected to a single router, but usually there's only one internet address for one router (the ''public address''). To be able to address the different computers connected to the router, the router gives them all a ''local address''. Special ranges of address are reserved for use like this (192.168.x.x, 10.x.x.x and 172.16.x.x through 172.31.x.x); these addresses are not accessible directly from the internet.<br /> <br /> When a local computer sends a packet over the internet to another computer, the router will replace the return address (which was the local address) with the public address, and send it along.<br /> And when a packet arrives from the internet, the router will change the destination address (which was the public address) to the address of the local computer for which it was destined.<br /> This relabeling is usually called ''NAT'' (for ''Network Address Translation'').<br /> <br /> And this is where the problems begin. How is a router to know for which local computer a packet is destined? The packet only comes with the public address and a port number.<br /> <br /> When a local computer sends packets first, the router can look at the originating address and port and remember them, so that when a reply comes to the same port, it knows for which computer it is meant.<br /> <br /> But if packets arrive from a computer over the internet out of the blue, the router does not know to which local computer it should direct them. (Even when there's only one local computer, most routers will just throw such packets away.) In this case, you need to tell your router explicitely where packets that match a specific pattern need to be sent to. For instance, you could tell it that packets that arrive for port 21837 should go to the computer with local address 192.168.0.2.<br /> <br /> ====Firewall basics====<br /> A firewall is a program which selectively blocks packets.<br /> <br /> Many programs will have some sort of network functionality, more than you're probably aware of, some which are part of Windows itself. When packets arrive these will happily respond to them. But while you may want to share your files with another local computer, you may not want your neighbours to see them. And every program that is accessible could also contain a bug that could compromise your system.<br /> <br /> This is where firewalls come in. They have rules which govern which packets are allowed to pass through unhindered, and which are blocked. And because it's better to be safe than sorry, firewalls usually block everything they don't know.<br /> <br /> So when you're running a program that needs to access the internet, you'll need to tell your firewall to allow it. A firewall may be running on your local computer (Windows XP has one built in), but your router may also have one. And frequently both will. Both may have to be instructed to allow your packets to get through.<br /> <br /> ===Finding out what your local address is===<br /> In Windows:<br /> *from the start menu, select "Run..."<br /> *type "cmd /K ipconfig" (on Windows 2000 and Windows XP), or "command /K ipconfig" (on older Windows versions)<br /> *the line saying "IP address" will contain your local address. You can ignore the rest.<br /> <br /> ===Finding out what your public address is===<br /> As your public address is sent as the return address everywhere you go on the internet, you just need to visit a web site that reports it back. [http://www.whatsmyip.org/ http://www.whatsmyip.org/] will do. You'll see your public internet address in big letters on the top of the page.<br /> <br /> Note that your ISP may give you a different public internet address each time your router asks for one (after a reboot of the router perhaps). Check, if you aren't sure.<br /> <br /> ===Finding out what your hostname is===<br /> First, find out what your public IP address is. <br /> Then on Windows:<br /> *from the start menu, select "Run..."<br /> *type "nslookup" (the nslookup tool will start and prompt you with ">")<br /> *type "set type=PTR"<br /> *type your public IP address<br /> *when the DNS server reponds, you will see something like<br /> <code>212.60.42.129.in-addr.arpa name = www.ibm.com</code><br /> *the part after <code>name = </code> is your publicly visible hostname.<br /> <br /> If you're logged in on IRC (see [#Finding someone to play against]), you can use the command <code>/whois</code> to find out what your hostname is. If your public internet address has no hostname, this will show your local address.<br /> <br /> ===Telling your router to forward UQM packets===<br /> There are many different routers, so this section will not contain specific instructions. You will need to find your router's manual, or find information on the internet. Typically, you use a web browser to connect to your router's own local internet address. Often [http://192.168.0.1/ http://192.168.0.1/], [http://192.168.1.1/ http://192.168.1.1/], or [http://10.0.0.1/ http://10.0.0.1/]. You'll probably need a password too.<br /> <br /> When you're logged in, look for a section with a name like "NAT", "IP masquerading" (another word for NAT), or "port forwarding".<br /> <br /> You'll need to tell it to forward packets addressed to port 21837 to port 21837 on your local address (see [[#Finding out what your local address is]]).<br /> <br /> If the router configuration doesn't work with single ports, but instead takes a range of addresses to forward, just use the range "21837-21837".<br /> <br /> If it wants to know a specific ''protocol'' (a class of packets) of packets to forward, use "TCP" (but The Ur-Quan Masters might use "UDP" in the future).<br /> <br /> The Ur-Quan Masters will probably also use port 21836 in the future, so you might as well forward it too.<br /> <br /> ===Telling your router's firewall not to block UQM packets===<br /> In the router's configuration menu (see [[#Telling your router to forward UQM packets|above]]), look for a section named something like "firewall" or "packet filtering".<br /> <br /> To allow incoming UQM packets, add a rule to pass packets from any address, from any port, to the public address, to port 21837. If it wants to know the protocol for the packets too, use "TCP" (but "UDP" may be used too in the future).<br /> <br /> Your router will likely allow any outgoing packets, so you probably won't have to add a rule for that, but if you do, it would look like this: pass packets from the public address, from port 21837, to any address, to any port.<br /> <br /> ===Telling your computer's firewall not to block UQM packets===<br /> This varies per firewall software.<br /> <br /> Using Windows XP's own firewall (be sure you have the latest Windows XP service pack installed), you will get a popup dialog when a program first tries to send packets, or begins to ''listen'' for incoming packets. Just start UQM, try to establish an incoming or outgoing connection as normal (see [[#Running the game|below]]), and when you get the popup, allow the incoming or outgoing connection attempt, and you'll be set.<br /> <br /> ===Network Summary===<br /> Ports used by The Ur-Quan Masters:<br /> *TCP port 21837<br /> *(reserved for the future) UDP port 21837 (not currently used)<br /> *(reserved for the future) TCP port 21836 (not currently used; for the meta-server)<br /> <br /> ==Alternative: Using Hamachi==<br /> Hamachi is a program which can usually obviate the need to do all the network settings above.<br /> <br /> The disadvantages are that you can only play against other Hamachi users and the increased network latency (and so the need for a higher netdelay)<br /> <br /> [TODO]<br /> <br /> ==Finding someone to play against==<br /> The IRC channel [irc://irc.freenode.net/#uqm-arena #uqm-arena] on irc.freenode.net is a good place to find people to eat your flaming plasma death.<br /> <br /> ==Running the game==<br /> ===Command-line switches===<br /> [TODO]<br /> See the [http://http://sc2.cvs.sourceforge.net/sc2/sc2/doc/users/netplay-howto.txt?view=markup netplay-howto.txt] file that came with the source for now.<br /> <br /> ===Starting a netplay game===<br /> [TODO]<br /> <br /> ==When it's not working==<br /> ===If you cannot establish a connection===<br /> This is usually caused by a routing of firewalling problem. See above.<br /> <br /> *When you are connecting to someone: if you start UQM with the '''--nethost2''' option, the outgoing address you specify is set for the '''top''' player. So make the top player network-controlled. If you used the '''--nethost1''' option, make the '''bottom''' player network-controlled.<br /> <br /> [TODO]<br /> <br /> ===If you can establish a connection, but are immediately disconnected===<br /> This will happen when the local and remote versions of The Ur-Quan Masters aren't compatible with eachother. Both players should upgrade to the latest version.<br /> Some time in the future, there will be a nicer error message.<br /> <br /> ===If the game aborts immediately after starting the battle===<br /> This usually happens if one player has installed some melee-affecting add-on, while the other player has not.<br /> <br /> It can also happen if one player isn't using the latest content upgrade to go with the UQM version he is using.<br /> <br /> ==Caveats==<br /> Netplay is still in the testing phase, so don't be surprised by the incidental crash or disconnect because of loss of synchronisation.<br /> See [[#If you've found a bug]].<br /> <br /> ==If you've found a bug==<br /> Bugs should go to the project's Bugzilla [http://bugs.uqm.stack.nl/ bug database]. Be verbose.</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Netplay_howto&diff=14042 Netplay howto 2006-11-03T09:15:46Z

<p>Fossil: /* If you cannot establish a connection */</p> <hr /> <div>This page describes how to play [[SuperMelee]] in [[The Ur-Quan Masters]] over a network. Take your time and read it thoroughly; every word is there for a reason.<br /> <br /> __TOC__<br /> <br /> <br /> ==Installing a network-capable version of The Ur-Quan Masters==<br /> Netplay is still in the testing phase, and there hasn't been a release yet which includes netplay. So to play netplay, you need the more recent developer sources. If you know how to compile the game yourself, you can just download the [http://sourceforge.net/cvs/?group_id=59452 latest sources from CVS] and compile as usual.<br /> <br /> If you're a Windows user, there is an easier way to go:<br /> #First, install the [http://sc2.sourceforge.net/downloads.php 0.5.0 release] of the game as normally. Do not install any melee-altering add-on packs unless your opponent has them installed too. Otherwise the two parties would lose synchronisation and the game would be aborted. Audio packs should be ok though.<br /> #From the [http://uqm.stack.nl/files/snapshots/ CVS snapshots page] download the latest precompiled binary (either release or debug; the debug version may give more information to help the developers if a bug occurs; the release version will be faster), as well as the latest content update.<br /> #Unpack the downloaded file (you will need a program such as [http://www.winzip.com/ WinZip] for this). You will end up with an <code>uqm.exe</code> or <code>uqm-debug.exe</code> file.<br /> #Find the <code>uqm.exe</code> file that came with 0.5.0, and replace it by the extracted .exe file (if you have <code>uqm-debug.exe</code> rename it to <code>uqm.exe</code>). If you installed The Ur-Quan Masters in the default location, you'll find it in <code>C:\Program Files\The Ur-Quan Masters\</code>).<br /> #In the folder where you found the <code>uqm.exe</code> file, there's another folder named <code>packages</code>, which contains the file <code>uqm-0.5.0-content.uqm</code> (and possibly other .uqm files for alternative music). Put the downloaded content update .zip file in here. '''DO NOT UNPACK THIS FILE!'''. The game knows how to read the files from inside the archive.<br /> If you later want to upgrade, just remove the old content upgrade .zip file and redo steps 2 and onwards.<br /> <br /> ==Setting up the network==<br /> <br /> Network experts can skip to the section "Settings Summary". For the others, read on, everything will be explained.<br /> <br /> ===Introduction===<br /> ====Network basics====<br /> Every computer on the internet has an ''internet address'', consisting of 4 numbers seperated by periods, like <code>131.155.140.133</code>. Information sent over the internet is split up in ''packets'', each packet labeled with the destination address.<br /> <br /> A computer may also have a ''host name'', like <code>uqm.stack.nl</code>, to make refering to it a bit easier to read for humans. When information needs to be sent to a computer known only by host name, its address will first be looked up.<br /> <br /> A computer may run many programs simultaneously which want to receive information from over the network. To direct packets to the correct program, the address will include a number known as the ''port number'' or ''port'' for short. The Ur-Quan Masters accepts packets sent to port ''21837''.<br /> <br /> ====Router basics====<br /> The little box which comes with most modern internet subscriptions is a ''router''. A router is a device which passes packets to other computer.<br /> <br /> Several computer may be connected to a single router, but usually there's only one internet address for one router (the ''public address''). To be able to address the different computers connected to the router, the router gives them all a ''local address''. Special ranges of address are reserved for use like this (192.168.x.x, 10.x.x.x and 172.16.x.x through 172.31.x.x); these addresses are not accessible directly from the internet.<br /> <br /> When a local computer sends a packet over the internet to another computer, the router will replace the return address (which was the local address) with the public address, and send it along.<br /> And when a packet arrives from the internet, the router will change the destination address (which was the public address) to the address of the local computer for which it was destined.<br /> This relabeling is usually called ''NAT'' (for ''Network Address Translation'').<br /> <br /> And this is where the problems begin. How is a router to know for which local computer a packet is destined? The packet only comes with the public address and a port number.<br /> <br /> When a local computer sends packets first, the router can look at the originating address and port and remember them, so that when a reply comes to the same port, it knows for which computer it is meant.<br /> <br /> But if packets arrive from a computer over the internet out of the blue, the router does not know to which local computer it should direct them. (Even when there's only one local computer, most routers will just throw such packets away.) In this case, you need to tell your router explicitely where packets that match a specific pattern need to be sent to. For instance, you could tell it that packets that arrive for port 21837 should go to the computer with local address 192.168.0.2.<br /> <br /> ====Firewall basics====<br /> A firewall is a program which selectively blocks packets.<br /> <br /> Many programs will have some sort of network functionality, more than you're probably aware of, some which are part of Windows itself. When packets arrive these will happily respond to them. But while you may want to share your files with another local computer, you may not want your neighbours to see them. And every program that is accessible could also contain a bug that could compromise your system.<br /> <br /> This is where firewalls come in. They have rules which govern which packets are allowed to pass through unhindered, and which are blocked. And because it's better to be safe than sorry, firewalls usually block everything they don't know.<br /> <br /> So when you're running a program that needs to access the internet, you'll need to tell your firewall to allow it. A firewall may be running on your local computer (Windows XP has one built in), but your router may also have one. And frequently both will. Both may have to be instructed to allow your packets to get through.<br /> <br /> ===Finding out what your local address is===<br /> In Windows:<br /> *from the start menu, select "Run..."<br /> *type "cmd /K ipconfig" (on Windows 2000 and Windows XP), or "command /K ipconfig" (on older Windows versions)<br /> *the line saying "IP address" will contain your local address. You can ignore the rest.<br /> <br /> ===Finding out what your public address is===<br /> As your public address is sent as the return address everywhere you go on the internet, you just need to visit a web site that reports it back. [http://www.whatsmyip.org/ http://www.whatsmyip.org/] will do. You'll see your public internet address in big letters on the top of the page.<br /> <br /> Note that your ISP may give you a different public internet address each time your router asks for one (after a reboot of the router perhaps). Check, if you aren't sure.<br /> <br /> ===Finding out what your hostname is===<br /> First, find out what your public IP address is. <br /> Then on Windows:<br /> *from the start menu, select "Run..."<br /> *type "nslookup" (the nslookup tool will start and prompt you with ">")<br /> *type "set type=PTR"<br /> *type your public IP address<br /> *when the DNS server reponds, you will see something like<br /> <code>212.60.42.129.in-addr.arpa name = www.ibm.com</code><br /> *the part after <code>name = </code> is your publicly visible hostname.<br /> <br /> If you're logged in on IRC (see [#Finding someone to play against]), you can use the command <code>/whois</code> to find out what your hostname is. If your public internet address has no hostname, this will show your local address.<br /> <br /> ===Telling your router to forward UQM packets===<br /> There are many different routers, so this section will not contain specific instructions. You will need to find your router's manual, or find information on the internet. Typically, you use a web browser to connect to your router's own local internet address. Often [http://192.168.0.1/ http://192.168.0.1/], [http://192.168.1.1/ http://192.168.1.1/], or [http://10.0.0.1/ http://10.0.0.1/]. You'll probably need a password too.<br /> <br /> When you're logged in, look for a section with a name like "NAT", "IP masquerading" (another word for NAT), or "port forwarding".<br /> <br /> You'll need to tell it to forward packets addressed to port 21837 to port 21837 on your local address (see [[#Finding out what your local address is]]).<br /> <br /> If the router configuration doesn't work with single ports, but instead takes a range of addresses to forward, just use the range "21837-21837".<br /> <br /> If it wants to know a specific ''protocol'' (a class of packets) of packets to forward, use "TCP" (but The Ur-Quan Masters might use "UDP" in the future).<br /> <br /> The Ur-Quan Masters will probably also use port 21836 in the future, so you might as well forward it too.<br /> <br /> ===Telling your router's firewall not to block UQM packets===<br /> In the router's configuration menu (see [[#Telling your router to forward UQM packets|above]]), look for a section named something like "firewall" or "packet filtering".<br /> <br /> To allow incoming UQM packets, add a rule to pass packets from any address, from any port, to the public address, to port 21837. If it wants to know the protocol for the packets too, use "TCP" (but "UDP" may be used too in the future).<br /> <br /> Your router will likely allow any outgoing packets, so you probably won't have to add a rule for that, but if you do, it would look like this: pass packets from the public address, from port 21837, to any address, to any port.<br /> <br /> ===Telling your computer's firewall not to block UQM packets===<br /> This varies per firewall software.<br /> <br /> Using Windows XP's own firewall (be sure you have the latest Windows XP service pack installed), you will get a popup dialog when a program first tries to send packets, or begins to ''listen'' for incoming packets. Just start UQM, try to establish an incoming or outgoing connection as normal (see [[#Running the game|below]]), and when you get the popup, allow the incoming or outgoing connection attempt, and you'll be set.<br /> <br /> ===Network Summary===<br /> Ports used by The Ur-Quan Masters:<br /> *TCP port 21837<br /> *(reserved for the future) UDP port 21837 (not currently used)<br /> *(reserved for the future) TCP port 21836 (not currently used; for the meta-server)<br /> <br /> ==Alternative: Using Hamachi==<br /> Hamachi is a program which can usually obviate the need to do all the network settings above.<br /> <br /> The disadvantages are that you can only play against other Hamachi users and the increased network latency (and so the need for a higher netdelay)<br /> <br /> [TODO]<br /> <br /> ==Finding someone to play against==<br /> The IRC channel [irc://irc.freenode.net/#uqm-arena #uqm-arena] on irc.freenode.net is a good place to find people to eat your flaming plasma death.<br /> <br /> ==Running the game==<br /> ===Command-line switches===<br /> [TODO]<br /> See the [http://http://sc2.cvs.sourceforge.net/sc2/sc2/doc/users/netplay-howto.txt?view=markup netplay-howto.txt] file that came with the source for now.<br /> <br /> ===Starting a netplay game===<br /> [TODO]<br /> <br /> ==When it's not working==<br /> ===If you cannot establish a connection===<br /> This is usually caused by a routing of firewalling problem. See above.<br /> <br /> *When you are connecting to someone: if you start UQM with the '''--nethost2''' option, the outgoing address you specify is set for the '''top''' player. So make the top player network-controlled. If you used the '''--nethost1''' option, make the '''bottom''' player network-controlled.<br /> <br /> [TODO]<br /> <br /> ===If you can establish a connection, but are immediately disconnected===<br /> This will happen when the local and remote versions of The Ur-Quan Masters aren't compatible with eachother. Both players should upgrade to the latest version.<br /> Some time in the future, there will be a nicer error message.<br /> <br /> ===If the game aborts immediately after starting the battle===<br /> This usually happens if one player has installed some melee-affecting add-on, while the other player has not.<br /> <br /> It can also happen if one player isn't using the latest content upgrade to go with the UQM version he is using.<br /> <br /> ==Caveats==<br /> Netplay is still in the testing phase, so don't be surprised of the incidental crash or disconnect because of loss of synchronisation.<br /> See [[#If you've found a bug]].<br /> <br /> ==If you've found a bug==<br /> Bugs should go to the project's Bugzilla [http://bugs.uqm.stack.nl/ bug database]. Be verbose.</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Netplay_howto&diff=14041 Netplay howto 2006-11-03T09:07:59Z

<p>Fossil: /* Alternative: Using Hamachi */</p> <hr /> <div>This page describes how to play [[SuperMelee]] in [[The Ur-Quan Masters]] over a network. Take your time and read it thoroughly; every word is there for a reason.<br /> <br /> __TOC__<br /> <br /> <br /> ==Installing a network-capable version of The Ur-Quan Masters==<br /> Netplay is still in the testing phase, and there hasn't been a release yet which includes netplay. So to play netplay, you need the more recent developer sources. If you know how to compile the game yourself, you can just download the [http://sourceforge.net/cvs/?group_id=59452 latest sources from CVS] and compile as usual.<br /> <br /> If you're a Windows user, there is an easier way to go:<br /> #First, install the [http://sc2.sourceforge.net/downloads.php 0.5.0 release] of the game as normally. Do not install any melee-altering add-on packs unless your opponent has them installed too. Otherwise the two parties would lose synchronisation and the game would be aborted. Audio packs should be ok though.<br /> #From the [http://uqm.stack.nl/files/snapshots/ CVS snapshots page] download the latest precompiled binary (either release or debug; the debug version may give more information to help the developers if a bug occurs; the release version will be faster), as well as the latest content update.<br /> #Unpack the downloaded file (you will need a program such as [http://www.winzip.com/ WinZip] for this). You will end up with an <code>uqm.exe</code> or <code>uqm-debug.exe</code> file.<br /> #Find the <code>uqm.exe</code> file that came with 0.5.0, and replace it by the extracted .exe file (if you have <code>uqm-debug.exe</code> rename it to <code>uqm.exe</code>). If you installed The Ur-Quan Masters in the default location, you'll find it in <code>C:\Program Files\The Ur-Quan Masters\</code>).<br /> #In the folder where you found the <code>uqm.exe</code> file, there's another folder named <code>packages</code>, which contains the file <code>uqm-0.5.0-content.uqm</code> (and possibly other .uqm files for alternative music). Put the downloaded content update .zip file in here. '''DO NOT UNPACK THIS FILE!'''. The game knows how to read the files from inside the archive.<br /> If you later want to upgrade, just remove the old content upgrade .zip file and redo steps 2 and onwards.<br /> <br /> ==Setting up the network==<br /> <br /> Network experts can skip to the section "Settings Summary". For the others, read on, everything will be explained.<br /> <br /> ===Introduction===<br /> ====Network basics====<br /> Every computer on the internet has an ''internet address'', consisting of 4 numbers seperated by periods, like <code>131.155.140.133</code>. Information sent over the internet is split up in ''packets'', each packet labeled with the destination address.<br /> <br /> A computer may also have a ''host name'', like <code>uqm.stack.nl</code>, to make refering to it a bit easier to read for humans. When information needs to be sent to a computer known only by host name, its address will first be looked up.<br /> <br /> A computer may run many programs simultaneously which want to receive information from over the network. To direct packets to the correct program, the address will include a number known as the ''port number'' or ''port'' for short. The Ur-Quan Masters accepts packets sent to port ''21837''.<br /> <br /> ====Router basics====<br /> The little box which comes with most modern internet subscriptions is a ''router''. A router is a device which passes packets to other computer.<br /> <br /> Several computer may be connected to a single router, but usually there's only one internet address for one router (the ''public address''). To be able to address the different computers connected to the router, the router gives them all a ''local address''. Special ranges of address are reserved for use like this (192.168.x.x, 10.x.x.x and 172.16.x.x through 172.31.x.x); these addresses are not accessible directly from the internet.<br /> <br /> When a local computer sends a packet over the internet to another computer, the router will replace the return address (which was the local address) with the public address, and send it along.<br /> And when a packet arrives from the internet, the router will change the destination address (which was the public address) to the address of the local computer for which it was destined.<br /> This relabeling is usually called ''NAT'' (for ''Network Address Translation'').<br /> <br /> And this is where the problems begin. How is a router to know for which local computer a packet is destined? The packet only comes with the public address and a port number.<br /> <br /> When a local computer sends packets first, the router can look at the originating address and port and remember them, so that when a reply comes to the same port, it knows for which computer it is meant.<br /> <br /> But if packets arrive from a computer over the internet out of the blue, the router does not know to which local computer it should direct them. (Even when there's only one local computer, most routers will just throw such packets away.) In this case, you need to tell your router explicitely where packets that match a specific pattern need to be sent to. For instance, you could tell it that packets that arrive for port 21837 should go to the computer with local address 192.168.0.2.<br /> <br /> ====Firewall basics====<br /> A firewall is a program which selectively blocks packets.<br /> <br /> Many programs will have some sort of network functionality, more than you're probably aware of, some which are part of Windows itself. When packets arrive these will happily respond to them. But while you may want to share your files with another local computer, you may not want your neighbours to see them. And every program that is accessible could also contain a bug that could compromise your system.<br /> <br /> This is where firewalls come in. They have rules which govern which packets are allowed to pass through unhindered, and which are blocked. And because it's better to be safe than sorry, firewalls usually block everything they don't know.<br /> <br /> So when you're running a program that needs to access the internet, you'll need to tell your firewall to allow it. A firewall may be running on your local computer (Windows XP has one built in), but your router may also have one. And frequently both will. Both may have to be instructed to allow your packets to get through.<br /> <br /> ===Finding out what your local address is===<br /> In Windows:<br /> *from the start menu, select "Run..."<br /> *type "cmd /K ipconfig" (on Windows 2000 and Windows XP), or "command /K ipconfig" (on older Windows versions)<br /> *the line saying "IP address" will contain your local address. You can ignore the rest.<br /> <br /> ===Finding out what your public address is===<br /> As your public address is sent as the return address everywhere you go on the internet, you just need to visit a web site that reports it back. [http://www.whatsmyip.org/ http://www.whatsmyip.org/] will do. You'll see your public internet address in big letters on the top of the page.<br /> <br /> Note that your ISP may give you a different public internet address each time your router asks for one (after a reboot of the router perhaps). Check, if you aren't sure.<br /> <br /> ===Finding out what your hostname is===<br /> First, find out what your public IP address is. <br /> Then on Windows:<br /> *from the start menu, select "Run..."<br /> *type "nslookup" (the nslookup tool will start and prompt you with ">")<br /> *type "set type=PTR"<br /> *type your public IP address<br /> *when the DNS server reponds, you will see something like<br /> <code>212.60.42.129.in-addr.arpa name = www.ibm.com</code><br /> *the part after <code>name = </code> is your publicly visible hostname.<br /> <br /> If you're logged in on IRC (see [#Finding someone to play against]), you can use the command <code>/whois</code> to find out what your hostname is. If your public internet address has no hostname, this will show your local address.<br /> <br /> ===Telling your router to forward UQM packets===<br /> There are many different routers, so this section will not contain specific instructions. You will need to find your router's manual, or find information on the internet. Typically, you use a web browser to connect to your router's own local internet address. Often [http://192.168.0.1/ http://192.168.0.1/], [http://192.168.1.1/ http://192.168.1.1/], or [http://10.0.0.1/ http://10.0.0.1/]. You'll probably need a password too.<br /> <br /> When you're logged in, look for a section with a name like "NAT", "IP masquerading" (another word for NAT), or "port forwarding".<br /> <br /> You'll need to tell it to forward packets addressed to port 21837 to port 21837 on your local address (see [[#Finding out what your local address is]]).<br /> <br /> If the router configuration doesn't work with single ports, but instead takes a range of addresses to forward, just use the range "21837-21837".<br /> <br /> If it wants to know a specific ''protocol'' (a class of packets) of packets to forward, use "TCP" (but The Ur-Quan Masters might use "UDP" in the future).<br /> <br /> The Ur-Quan Masters will probably also use port 21836 in the future, so you might as well forward it too.<br /> <br /> ===Telling your router's firewall not to block UQM packets===<br /> In the router's configuration menu (see [[#Telling your router to forward UQM packets|above]]), look for a section named something like "firewall" or "packet filtering".<br /> <br /> To allow incoming UQM packets, add a rule to pass packets from any address, from any port, to the public address, to port 21837. If it wants to know the protocol for the packets too, use "TCP" (but "UDP" may be used too in the future).<br /> <br /> Your router will likely allow any outgoing packets, so you probably won't have to add a rule for that, but if you do, it would look like this: pass packets from the public address, from port 21837, to any address, to any port.<br /> <br /> ===Telling your computer's firewall not to block UQM packets===<br /> This varies per firewall software.<br /> <br /> Using Windows XP's own firewall (be sure you have the latest Windows XP service pack installed), you will get a popup dialog when a program first tries to send packets, or begins to ''listen'' for incoming packets. Just start UQM, try to establish an incoming or outgoing connection as normal (see [[#Running the game|below]]), and when you get the popup, allow the incoming or outgoing connection attempt, and you'll be set.<br /> <br /> ===Network Summary===<br /> Ports used by The Ur-Quan Masters:<br /> *TCP port 21837<br /> *(reserved for the future) UDP port 21837 (not currently used)<br /> *(reserved for the future) TCP port 21836 (not currently used; for the meta-server)<br /> <br /> ==Alternative: Using Hamachi==<br /> Hamachi is a program which can usually obviate the need to do all the network settings above.<br /> <br /> The disadvantages are that you can only play against other Hamachi users and the increased network latency (and so the need for a higher netdelay)<br /> <br /> [TODO]<br /> <br /> ==Finding someone to play against==<br /> The IRC channel [irc://irc.freenode.net/#uqm-arena #uqm-arena] on irc.freenode.net is a good place to find people to eat your flaming plasma death.<br /> <br /> ==Running the game==<br /> ===Command-line switches===<br /> [TODO]<br /> See the [http://http://sc2.cvs.sourceforge.net/sc2/sc2/doc/users/netplay-howto.txt?view=markup netplay-howto.txt] file that came with the source for now.<br /> <br /> ===Starting a netplay game===<br /> [TODO]<br /> <br /> ==When it's not working==<br /> ===If you cannot establish a connection===<br /> This is usually caused by a routing of firewalling problem. See above.<br /> [TODO]<br /> <br /> ===If you can establish a connection, but are immediately disconnected===<br /> This will happen when the local and remote versions of The Ur-Quan Masters aren't compatible with eachother. Both players should upgrade to the latest version.<br /> Some time in the future, there will be a nicer error message.<br /> <br /> ===If the game aborts immediately after starting the battle===<br /> This usually happens if one player has installed some melee-affecting add-on, while the other player has not.<br /> <br /> It can also happen if one player isn't using the latest content upgrade to go with the UQM version he is using.<br /> <br /> ==Caveats==<br /> Netplay is still in the testing phase, so don't be surprised of the incidental crash or disconnect because of loss of synchronisation.<br /> See [[#If you've found a bug]].<br /> <br /> ==If you've found a bug==<br /> Bugs should go to the project's Bugzilla [http://bugs.uqm.stack.nl/ bug database]. Be verbose.</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Netplay_howto&diff=14040 Netplay howto 2006-11-03T09:02:03Z

<p>Fossil: /* Finding out what your hostname is */</p> <hr /> <div>This page describes how to play [[SuperMelee]] in [[The Ur-Quan Masters]] over a network. Take your time and read it thoroughly; every word is there for a reason.<br /> <br /> __TOC__<br /> <br /> <br /> ==Installing a network-capable version of The Ur-Quan Masters==<br /> Netplay is still in the testing phase, and there hasn't been a release yet which includes netplay. So to play netplay, you need the more recent developer sources. If you know how to compile the game yourself, you can just download the [http://sourceforge.net/cvs/?group_id=59452 latest sources from CVS] and compile as usual.<br /> <br /> If you're a Windows user, there is an easier way to go:<br /> #First, install the [http://sc2.sourceforge.net/downloads.php 0.5.0 release] of the game as normally. Do not install any melee-altering add-on packs unless your opponent has them installed too. Otherwise the two parties would lose synchronisation and the game would be aborted. Audio packs should be ok though.<br /> #From the [http://uqm.stack.nl/files/snapshots/ CVS snapshots page] download the latest precompiled binary (either release or debug; the debug version may give more information to help the developers if a bug occurs; the release version will be faster), as well as the latest content update.<br /> #Unpack the downloaded file (you will need a program such as [http://www.winzip.com/ WinZip] for this). You will end up with an <code>uqm.exe</code> or <code>uqm-debug.exe</code> file.<br /> #Find the <code>uqm.exe</code> file that came with 0.5.0, and replace it by the extracted .exe file (if you have <code>uqm-debug.exe</code> rename it to <code>uqm.exe</code>). If you installed The Ur-Quan Masters in the default location, you'll find it in <code>C:\Program Files\The Ur-Quan Masters\</code>).<br /> #In the folder where you found the <code>uqm.exe</code> file, there's another folder named <code>packages</code>, which contains the file <code>uqm-0.5.0-content.uqm</code> (and possibly other .uqm files for alternative music). Put the downloaded content update .zip file in here. '''DO NOT UNPACK THIS FILE!'''. The game knows how to read the files from inside the archive.<br /> If you later want to upgrade, just remove the old content upgrade .zip file and redo steps 2 and onwards.<br /> <br /> ==Setting up the network==<br /> <br /> Network experts can skip to the section "Settings Summary". For the others, read on, everything will be explained.<br /> <br /> ===Introduction===<br /> ====Network basics====<br /> Every computer on the internet has an ''internet address'', consisting of 4 numbers seperated by periods, like <code>131.155.140.133</code>. Information sent over the internet is split up in ''packets'', each packet labeled with the destination address.<br /> <br /> A computer may also have a ''host name'', like <code>uqm.stack.nl</code>, to make refering to it a bit easier to read for humans. When information needs to be sent to a computer known only by host name, its address will first be looked up.<br /> <br /> A computer may run many programs simultaneously which want to receive information from over the network. To direct packets to the correct program, the address will include a number known as the ''port number'' or ''port'' for short. The Ur-Quan Masters accepts packets sent to port ''21837''.<br /> <br /> ====Router basics====<br /> The little box which comes with most modern internet subscriptions is a ''router''. A router is a device which passes packets to other computer.<br /> <br /> Several computer may be connected to a single router, but usually there's only one internet address for one router (the ''public address''). To be able to address the different computers connected to the router, the router gives them all a ''local address''. Special ranges of address are reserved for use like this (192.168.x.x, 10.x.x.x and 172.16.x.x through 172.31.x.x); these addresses are not accessible directly from the internet.<br /> <br /> When a local computer sends a packet over the internet to another computer, the router will replace the return address (which was the local address) with the public address, and send it along.<br /> And when a packet arrives from the internet, the router will change the destination address (which was the public address) to the address of the local computer for which it was destined.<br /> This relabeling is usually called ''NAT'' (for ''Network Address Translation'').<br /> <br /> And this is where the problems begin. How is a router to know for which local computer a packet is destined? The packet only comes with the public address and a port number.<br /> <br /> When a local computer sends packets first, the router can look at the originating address and port and remember them, so that when a reply comes to the same port, it knows for which computer it is meant.<br /> <br /> But if packets arrive from a computer over the internet out of the blue, the router does not know to which local computer it should direct them. (Even when there's only one local computer, most routers will just throw such packets away.) In this case, you need to tell your router explicitely where packets that match a specific pattern need to be sent to. For instance, you could tell it that packets that arrive for port 21837 should go to the computer with local address 192.168.0.2.<br /> <br /> ====Firewall basics====<br /> A firewall is a program which selectively blocks packets.<br /> <br /> Many programs will have some sort of network functionality, more than you're probably aware of, some which are part of Windows itself. When packets arrive these will happily respond to them. But while you may want to share your files with another local computer, you may not want your neighbours to see them. And every program that is accessible could also contain a bug that could compromise your system.<br /> <br /> This is where firewalls come in. They have rules which govern which packets are allowed to pass through unhindered, and which are blocked. And because it's better to be safe than sorry, firewalls usually block everything they don't know.<br /> <br /> So when you're running a program that needs to access the internet, you'll need to tell your firewall to allow it. A firewall may be running on your local computer (Windows XP has one built in), but your router may also have one. And frequently both will. Both may have to be instructed to allow your packets to get through.<br /> <br /> ===Finding out what your local address is===<br /> In Windows:<br /> *from the start menu, select "Run..."<br /> *type "cmd /K ipconfig" (on Windows 2000 and Windows XP), or "command /K ipconfig" (on older Windows versions)<br /> *the line saying "IP address" will contain your local address. You can ignore the rest.<br /> <br /> ===Finding out what your public address is===<br /> As your public address is sent as the return address everywhere you go on the internet, you just need to visit a web site that reports it back. [http://www.whatsmyip.org/ http://www.whatsmyip.org/] will do. You'll see your public internet address in big letters on the top of the page.<br /> <br /> Note that your ISP may give you a different public internet address each time your router asks for one (after a reboot of the router perhaps). Check, if you aren't sure.<br /> <br /> ===Finding out what your hostname is===<br /> First, find out what your public IP address is. <br /> Then on Windows:<br /> *from the start menu, select "Run..."<br /> *type "nslookup" (the nslookup tool will start and prompt you with ">")<br /> *type "set type=PTR"<br /> *type your public IP address<br /> *when the DNS server reponds, you will see something like<br /> <code>212.60.42.129.in-addr.arpa name = www.ibm.com</code><br /> *the part after <code>name = </code> is your publicly visible hostname.<br /> <br /> If you're logged in on IRC (see [#Finding someone to play against]), you can use the command <code>/whois</code> to find out what your hostname is. If your public internet address has no hostname, this will show your local address.<br /> <br /> ===Telling your router to forward UQM packets===<br /> There are many different routers, so this section will not contain specific instructions. You will need to find your router's manual, or find information on the internet. Typically, you use a web browser to connect to your router's own local internet address. Often [http://192.168.0.1/ http://192.168.0.1/], [http://192.168.1.1/ http://192.168.1.1/], or [http://10.0.0.1/ http://10.0.0.1/]. You'll probably need a password too.<br /> <br /> When you're logged in, look for a section with a name like "NAT", "IP masquerading" (another word for NAT), or "port forwarding".<br /> <br /> You'll need to tell it to forward packets addressed to port 21837 to port 21837 on your local address (see [[#Finding out what your local address is]]).<br /> <br /> If the router configuration doesn't work with single ports, but instead takes a range of addresses to forward, just use the range "21837-21837".<br /> <br /> If it wants to know a specific ''protocol'' (a class of packets) of packets to forward, use "TCP" (but The Ur-Quan Masters might use "UDP" in the future).<br /> <br /> The Ur-Quan Masters will probably also use port 21836 in the future, so you might as well forward it too.<br /> <br /> ===Telling your router's firewall not to block UQM packets===<br /> In the router's configuration menu (see [[#Telling your router to forward UQM packets|above]]), look for a section named something like "firewall" or "packet filtering".<br /> <br /> To allow incoming UQM packets, add a rule to pass packets from any address, from any port, to the public address, to port 21837. If it wants to know the protocol for the packets too, use "TCP" (but "UDP" may be used too in the future).<br /> <br /> Your router will likely allow any outgoing packets, so you probably won't have to add a rule for that, but if you do, it would look like this: pass packets from the public address, from port 21837, to any address, to any port.<br /> <br /> ===Telling your computer's firewall not to block UQM packets===<br /> This varies per firewall software.<br /> <br /> Using Windows XP's own firewall (be sure you have the latest Windows XP service pack installed), you will get a popup dialog when a program first tries to send packets, or begins to ''listen'' for incoming packets. Just start UQM, try to establish an incoming or outgoing connection as normal (see [[#Running the game|below]]), and when you get the popup, allow the incoming or outgoing connection attempt, and you'll be set.<br /> <br /> ===Network Summary===<br /> Ports used by The Ur-Quan Masters:<br /> *TCP port 21837<br /> *(reserved for the future) UDP port 21837 (not currently used)<br /> *(reserved for the future) TCP port 21836 (not currently used; for the meta-server)<br /> <br /> ==Alternative: Using Hamachi==<br /> Hamachi is a program which can usually obviate the need to do all the network settings above.<br /> <br /> The disadvantage is that you can only play against other Hamachi users.<br /> <br /> [TODO]<br /> <br /> <br /> ==Finding someone to play against==<br /> The IRC channel [irc://irc.freenode.net/#uqm-arena #uqm-arena] on irc.freenode.net is a good place to find people to eat your flaming plasma death.<br /> <br /> ==Running the game==<br /> ===Command-line switches===<br /> [TODO]<br /> See the [http://http://sc2.cvs.sourceforge.net/sc2/sc2/doc/users/netplay-howto.txt?view=markup netplay-howto.txt] file that came with the source for now.<br /> <br /> ===Starting a netplay game===<br /> [TODO]<br /> <br /> ==When it's not working==<br /> ===If you cannot establish a connection===<br /> This is usually caused by a routing of firewalling problem. See above.<br /> [TODO]<br /> <br /> ===If you can establish a connection, but are immediately disconnected===<br /> This will happen when the local and remote versions of The Ur-Quan Masters aren't compatible with eachother. Both players should upgrade to the latest version.<br /> Some time in the future, there will be a nicer error message.<br /> <br /> ===If the game aborts immediately after starting the battle===<br /> This usually happens if one player has installed some melee-affecting add-on, while the other player has not.<br /> <br /> It can also happen if one player isn't using the latest content upgrade to go with the UQM version he is using.<br /> <br /> ==Caveats==<br /> Netplay is still in the testing phase, so don't be surprised of the incidental crash or disconnect because of loss of synchronisation.<br /> See [[#If you've found a bug]].<br /> <br /> ==If you've found a bug==<br /> Bugs should go to the project's Bugzilla [http://bugs.uqm.stack.nl/ bug database]. Be verbose.</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Netplay_howto&diff=14039 Netplay howto 2006-11-03T09:01:07Z

<p>Fossil: /* Finding out what your hostname is */</p> <hr /> <div>This page describes how to play [[SuperMelee]] in [[The Ur-Quan Masters]] over a network. Take your time and read it thoroughly; every word is there for a reason.<br /> <br /> __TOC__<br /> <br /> <br /> ==Installing a network-capable version of The Ur-Quan Masters==<br /> Netplay is still in the testing phase, and there hasn't been a release yet which includes netplay. So to play netplay, you need the more recent developer sources. If you know how to compile the game yourself, you can just download the [http://sourceforge.net/cvs/?group_id=59452 latest sources from CVS] and compile as usual.<br /> <br /> If you're a Windows user, there is an easier way to go:<br /> #First, install the [http://sc2.sourceforge.net/downloads.php 0.5.0 release] of the game as normally. Do not install any melee-altering add-on packs unless your opponent has them installed too. Otherwise the two parties would lose synchronisation and the game would be aborted. Audio packs should be ok though.<br /> #From the [http://uqm.stack.nl/files/snapshots/ CVS snapshots page] download the latest precompiled binary (either release or debug; the debug version may give more information to help the developers if a bug occurs; the release version will be faster), as well as the latest content update.<br /> #Unpack the downloaded file (you will need a program such as [http://www.winzip.com/ WinZip] for this). You will end up with an <code>uqm.exe</code> or <code>uqm-debug.exe</code> file.<br /> #Find the <code>uqm.exe</code> file that came with 0.5.0, and replace it by the extracted .exe file (if you have <code>uqm-debug.exe</code> rename it to <code>uqm.exe</code>). If you installed The Ur-Quan Masters in the default location, you'll find it in <code>C:\Program Files\The Ur-Quan Masters\</code>).<br /> #In the folder where you found the <code>uqm.exe</code> file, there's another folder named <code>packages</code>, which contains the file <code>uqm-0.5.0-content.uqm</code> (and possibly other .uqm files for alternative music). Put the downloaded content update .zip file in here. '''DO NOT UNPACK THIS FILE!'''. The game knows how to read the files from inside the archive.<br /> If you later want to upgrade, just remove the old content upgrade .zip file and redo steps 2 and onwards.<br /> <br /> ==Setting up the network==<br /> <br /> Network experts can skip to the section "Settings Summary". For the others, read on, everything will be explained.<br /> <br /> ===Introduction===<br /> ====Network basics====<br /> Every computer on the internet has an ''internet address'', consisting of 4 numbers seperated by periods, like <code>131.155.140.133</code>. Information sent over the internet is split up in ''packets'', each packet labeled with the destination address.<br /> <br /> A computer may also have a ''host name'', like <code>uqm.stack.nl</code>, to make refering to it a bit easier to read for humans. When information needs to be sent to a computer known only by host name, its address will first be looked up.<br /> <br /> A computer may run many programs simultaneously which want to receive information from over the network. To direct packets to the correct program, the address will include a number known as the ''port number'' or ''port'' for short. The Ur-Quan Masters accepts packets sent to port ''21837''.<br /> <br /> ====Router basics====<br /> The little box which comes with most modern internet subscriptions is a ''router''. A router is a device which passes packets to other computer.<br /> <br /> Several computer may be connected to a single router, but usually there's only one internet address for one router (the ''public address''). To be able to address the different computers connected to the router, the router gives them all a ''local address''. Special ranges of address are reserved for use like this (192.168.x.x, 10.x.x.x and 172.16.x.x through 172.31.x.x); these addresses are not accessible directly from the internet.<br /> <br /> When a local computer sends a packet over the internet to another computer, the router will replace the return address (which was the local address) with the public address, and send it along.<br /> And when a packet arrives from the internet, the router will change the destination address (which was the public address) to the address of the local computer for which it was destined.<br /> This relabeling is usually called ''NAT'' (for ''Network Address Translation'').<br /> <br /> And this is where the problems begin. How is a router to know for which local computer a packet is destined? The packet only comes with the public address and a port number.<br /> <br /> When a local computer sends packets first, the router can look at the originating address and port and remember them, so that when a reply comes to the same port, it knows for which computer it is meant.<br /> <br /> But if packets arrive from a computer over the internet out of the blue, the router does not know to which local computer it should direct them. (Even when there's only one local computer, most routers will just throw such packets away.) In this case, you need to tell your router explicitely where packets that match a specific pattern need to be sent to. For instance, you could tell it that packets that arrive for port 21837 should go to the computer with local address 192.168.0.2.<br /> <br /> ====Firewall basics====<br /> A firewall is a program which selectively blocks packets.<br /> <br /> Many programs will have some sort of network functionality, more than you're probably aware of, some which are part of Windows itself. When packets arrive these will happily respond to them. But while you may want to share your files with another local computer, you may not want your neighbours to see them. And every program that is accessible could also contain a bug that could compromise your system.<br /> <br /> This is where firewalls come in. They have rules which govern which packets are allowed to pass through unhindered, and which are blocked. And because it's better to be safe than sorry, firewalls usually block everything they don't know.<br /> <br /> So when you're running a program that needs to access the internet, you'll need to tell your firewall to allow it. A firewall may be running on your local computer (Windows XP has one built in), but your router may also have one. And frequently both will. Both may have to be instructed to allow your packets to get through.<br /> <br /> ===Finding out what your local address is===<br /> In Windows:<br /> *from the start menu, select "Run..."<br /> *type "cmd /K ipconfig" (on Windows 2000 and Windows XP), or "command /K ipconfig" (on older Windows versions)<br /> *the line saying "IP address" will contain your local address. You can ignore the rest.<br /> <br /> ===Finding out what your public address is===<br /> As your public address is sent as the return address everywhere you go on the internet, you just need to visit a web site that reports it back. [http://www.whatsmyip.org/ http://www.whatsmyip.org/] will do. You'll see your public internet address in big letters on the top of the page.<br /> <br /> Note that your ISP may give you a different public internet address each time your router asks for one (after a reboot of the router perhaps). Check, if you aren't sure.<br /> <br /> ===Finding out what your hostname is===<br /> First, find out what your public IP address is. <br /> Then on Windows:<br /> *from the start menu, select "Run..."<br /> *type "nslookup" (the nslookup tool will start amd prompt you with ">")<br /> *type "set type=PTR"<br /> *type your public IP address<br /> *when the DNS server reponds, you will see something like<br /> <code>212.60.42.129.in-addr.arpa name = www.ibm.com</code><br /> *the part after <code>name = </code> is your publicly visible hostname.<br /> <br /> If you're logged in on IRC (see [#Finding someone to play against]), you can use the command <code>/whois</code> to find out what your hostname is. If your public internet address has no hostname, this will show your local address.<br /> <br /> ===Telling your router to forward UQM packets===<br /> There are many different routers, so this section will not contain specific instructions. You will need to find your router's manual, or find information on the internet. Typically, you use a web browser to connect to your router's own local internet address. Often [http://192.168.0.1/ http://192.168.0.1/], [http://192.168.1.1/ http://192.168.1.1/], or [http://10.0.0.1/ http://10.0.0.1/]. You'll probably need a password too.<br /> <br /> When you're logged in, look for a section with a name like "NAT", "IP masquerading" (another word for NAT), or "port forwarding".<br /> <br /> You'll need to tell it to forward packets addressed to port 21837 to port 21837 on your local address (see [[#Finding out what your local address is]]).<br /> <br /> If the router configuration doesn't work with single ports, but instead takes a range of addresses to forward, just use the range "21837-21837".<br /> <br /> If it wants to know a specific ''protocol'' (a class of packets) of packets to forward, use "TCP" (but The Ur-Quan Masters might use "UDP" in the future).<br /> <br /> The Ur-Quan Masters will probably also use port 21836 in the future, so you might as well forward it too.<br /> <br /> ===Telling your router's firewall not to block UQM packets===<br /> In the router's configuration menu (see [[#Telling your router to forward UQM packets|above]]), look for a section named something like "firewall" or "packet filtering".<br /> <br /> To allow incoming UQM packets, add a rule to pass packets from any address, from any port, to the public address, to port 21837. If it wants to know the protocol for the packets too, use "TCP" (but "UDP" may be used too in the future).<br /> <br /> Your router will likely allow any outgoing packets, so you probably won't have to add a rule for that, but if you do, it would look like this: pass packets from the public address, from port 21837, to any address, to any port.<br /> <br /> ===Telling your computer's firewall not to block UQM packets===<br /> This varies per firewall software.<br /> <br /> Using Windows XP's own firewall (be sure you have the latest Windows XP service pack installed), you will get a popup dialog when a program first tries to send packets, or begins to ''listen'' for incoming packets. Just start UQM, try to establish an incoming or outgoing connection as normal (see [[#Running the game|below]]), and when you get the popup, allow the incoming or outgoing connection attempt, and you'll be set.<br /> <br /> ===Network Summary===<br /> Ports used by The Ur-Quan Masters:<br /> *TCP port 21837<br /> *(reserved for the future) UDP port 21837 (not currently used)<br /> *(reserved for the future) TCP port 21836 (not currently used; for the meta-server)<br /> <br /> ==Alternative: Using Hamachi==<br /> Hamachi is a program which can usually obviate the need to do all the network settings above.<br /> <br /> The disadvantage is that you can only play against other Hamachi users.<br /> <br /> [TODO]<br /> <br /> <br /> ==Finding someone to play against==<br /> The IRC channel [irc://irc.freenode.net/#uqm-arena #uqm-arena] on irc.freenode.net is a good place to find people to eat your flaming plasma death.<br /> <br /> ==Running the game==<br /> ===Command-line switches===<br /> [TODO]<br /> See the [http://http://sc2.cvs.sourceforge.net/sc2/sc2/doc/users/netplay-howto.txt?view=markup netplay-howto.txt] file that came with the source for now.<br /> <br /> ===Starting a netplay game===<br /> [TODO]<br /> <br /> ==When it's not working==<br /> ===If you cannot establish a connection===<br /> This is usually caused by a routing of firewalling problem. See above.<br /> [TODO]<br /> <br /> ===If you can establish a connection, but are immediately disconnected===<br /> This will happen when the local and remote versions of The Ur-Quan Masters aren't compatible with eachother. Both players should upgrade to the latest version.<br /> Some time in the future, there will be a nicer error message.<br /> <br /> ===If the game aborts immediately after starting the battle===<br /> This usually happens if one player has installed some melee-affecting add-on, while the other player has not.<br /> <br /> It can also happen if one player isn't using the latest content upgrade to go with the UQM version he is using.<br /> <br /> ==Caveats==<br /> Netplay is still in the testing phase, so don't be surprised of the incidental crash or disconnect because of loss of synchronisation.<br /> See [[#If you've found a bug]].<br /> <br /> ==If you've found a bug==<br /> Bugs should go to the project's Bugzilla [http://bugs.uqm.stack.nl/ bug database]. Be verbose.</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Netplay_howto&diff=14038 Netplay howto 2006-11-03T08:49:20Z

<p>Fossil: /* Firewall basics */</p> <hr /> <div>This page describes how to play [[SuperMelee]] in [[The Ur-Quan Masters]] over a network. Take your time and read it thoroughly; every word is there for a reason.<br /> <br /> __TOC__<br /> <br /> <br /> ==Installing a network-capable version of The Ur-Quan Masters==<br /> Netplay is still in the testing phase, and there hasn't been a release yet which includes netplay. So to play netplay, you need the more recent developer sources. If you know how to compile the game yourself, you can just download the [http://sourceforge.net/cvs/?group_id=59452 latest sources from CVS] and compile as usual.<br /> <br /> If you're a Windows user, there is an easier way to go:<br /> #First, install the [http://sc2.sourceforge.net/downloads.php 0.5.0 release] of the game as normally. Do not install any melee-altering add-on packs unless your opponent has them installed too. Otherwise the two parties would lose synchronisation and the game would be aborted. Audio packs should be ok though.<br /> #From the [http://uqm.stack.nl/files/snapshots/ CVS snapshots page] download the latest precompiled binary (either release or debug; the debug version may give more information to help the developers if a bug occurs; the release version will be faster), as well as the latest content update.<br /> #Unpack the downloaded file (you will need a program such as [http://www.winzip.com/ WinZip] for this). You will end up with an <code>uqm.exe</code> or <code>uqm-debug.exe</code> file.<br /> #Find the <code>uqm.exe</code> file that came with 0.5.0, and replace it by the extracted .exe file (if you have <code>uqm-debug.exe</code> rename it to <code>uqm.exe</code>). If you installed The Ur-Quan Masters in the default location, you'll find it in <code>C:\Program Files\The Ur-Quan Masters\</code>).<br /> #In the folder where you found the <code>uqm.exe</code> file, there's another folder named <code>packages</code>, which contains the file <code>uqm-0.5.0-content.uqm</code> (and possibly other .uqm files for alternative music). Put the downloaded content update .zip file in here. '''DO NOT UNPACK THIS FILE!'''. The game knows how to read the files from inside the archive.<br /> If you later want to upgrade, just remove the old content upgrade .zip file and redo steps 2 and onwards.<br /> <br /> ==Setting up the network==<br /> <br /> Network experts can skip to the section "Settings Summary". For the others, read on, everything will be explained.<br /> <br /> ===Introduction===<br /> ====Network basics====<br /> Every computer on the internet has an ''internet address'', consisting of 4 numbers seperated by periods, like <code>131.155.140.133</code>. Information sent over the internet is split up in ''packets'', each packet labeled with the destination address.<br /> <br /> A computer may also have a ''host name'', like <code>uqm.stack.nl</code>, to make refering to it a bit easier to read for humans. When information needs to be sent to a computer known only by host name, its address will first be looked up.<br /> <br /> A computer may run many programs simultaneously which want to receive information from over the network. To direct packets to the correct program, the address will include a number known as the ''port number'' or ''port'' for short. The Ur-Quan Masters accepts packets sent to port ''21837''.<br /> <br /> ====Router basics====<br /> The little box which comes with most modern internet subscriptions is a ''router''. A router is a device which passes packets to other computer.<br /> <br /> Several computer may be connected to a single router, but usually there's only one internet address for one router (the ''public address''). To be able to address the different computers connected to the router, the router gives them all a ''local address''. Special ranges of address are reserved for use like this (192.168.x.x, 10.x.x.x and 172.16.x.x through 172.31.x.x); these addresses are not accessible directly from the internet.<br /> <br /> When a local computer sends a packet over the internet to another computer, the router will replace the return address (which was the local address) with the public address, and send it along.<br /> And when a packet arrives from the internet, the router will change the destination address (which was the public address) to the address of the local computer for which it was destined.<br /> This relabeling is usually called ''NAT'' (for ''Network Address Translation'').<br /> <br /> And this is where the problems begin. How is a router to know for which local computer a packet is destined? The packet only comes with the public address and a port number.<br /> <br /> When a local computer sends packets first, the router can look at the originating address and port and remember them, so that when a reply comes to the same port, it knows for which computer it is meant.<br /> <br /> But if packets arrive from a computer over the internet out of the blue, the router does not know to which local computer it should direct them. (Even when there's only one local computer, most routers will just throw such packets away.) In this case, you need to tell your router explicitely where packets that match a specific pattern need to be sent to. For instance, you could tell it that packets that arrive for port 21837 should go to the computer with local address 192.168.0.2.<br /> <br /> ====Firewall basics====<br /> A firewall is a program which selectively blocks packets.<br /> <br /> Many programs will have some sort of network functionality, more than you're probably aware of, some which are part of Windows itself. When packets arrive these will happily respond to them. But while you may want to share your files with another local computer, you may not want your neighbours to see them. And every program that is accessible could also contain a bug that could compromise your system.<br /> <br /> This is where firewalls come in. They have rules which govern which packets are allowed to pass through unhindered, and which are blocked. And because it's better to be safe than sorry, firewalls usually block everything they don't know.<br /> <br /> So when you're running a program that needs to access the internet, you'll need to tell your firewall to allow it. A firewall may be running on your local computer (Windows XP has one built in), but your router may also have one. And frequently both will. Both may have to be instructed to allow your packets to get through.<br /> <br /> ===Finding out what your local address is===<br /> In Windows:<br /> *from the start menu, select "Run..."<br /> *type "cmd /K ipconfig" (on Windows 2000 and Windows XP), or "command /K ipconfig" (on older Windows versions)<br /> *the line saying "IP address" will contain your local address. You can ignore the rest.<br /> <br /> ===Finding out what your public address is===<br /> As your public address is sent as the return address everywhere you go on the internet, you just need to visit a web site that reports it back. [http://www.whatsmyip.org/ http://www.whatsmyip.org/] will do. You'll see your public internet address in big letters on the top of the page.<br /> <br /> Note that your ISP may give you a different public internet address each time your router asks for one (after a reboot of the router perhaps). Check, if you aren't sure.<br /> <br /> ===Finding out what your hostname is===<br /> [TODO]<br /> <br /> If you're logged in on IRC (see [#Finding someone to play against]), you can use the command <code>/whois</code> to find out what your hostname is. If your public internet address has no hostname, this will show your local address.<br /> <br /> ===Telling your router to forward UQM packets===<br /> There are many different routers, so this section will not contain specific instructions. You will need to find your router's manual, or find information on the internet. Typically, you use a web browser to connect to your router's own local internet address. Often [http://192.168.0.1/ http://192.168.0.1/], [http://192.168.1.1/ http://192.168.1.1/], or [http://10.0.0.1/ http://10.0.0.1/]. You'll probably need a password too.<br /> <br /> When you're logged in, look for a section with a name like "NAT", "IP masquerading" (another word for NAT), or "port forwarding".<br /> <br /> You'll need to tell it to forward packets addressed to port 21837 to port 21837 on your local address (see [[#Finding out what your local address is]]).<br /> <br /> If the router configuration doesn't work with single ports, but instead takes a range of addresses to forward, just use the range "21837-21837".<br /> <br /> If it wants to know a specific ''protocol'' (a class of packets) of packets to forward, use "TCP" (but The Ur-Quan Masters might use "UDP" in the future).<br /> <br /> The Ur-Quan Masters will probably also use port 21836 in the future, so you might as well forward it too.<br /> <br /> ===Telling your router's firewall not to block UQM packets===<br /> In the router's configuration menu (see [[#Telling your router to forward UQM packets|above]]), look for a section named something like "firewall" or "packet filtering".<br /> <br /> To allow incoming UQM packets, add a rule to pass packets from any address, from any port, to the public address, to port 21837. If it wants to know the protocol for the packets too, use "TCP" (but "UDP" may be used too in the future).<br /> <br /> Your router will likely allow any outgoing packets, so you probably won't have to add a rule for that, but if you do, it would look like this: pass packets from the public address, from port 21837, to any address, to any port.<br /> <br /> ===Telling your computer's firewall not to block UQM packets===<br /> This varies per firewall software.<br /> <br /> Using Windows XP's own firewall (be sure you have the latest Windows XP service pack installed), you will get a popup dialog when a program first tries to send packets, or begins to ''listen'' for incoming packets. Just start UQM, try to establish an incoming or outgoing connection as normal (see [[#Running the game|below]]), and when you get the popup, allow the incoming or outgoing connection attempt, and you'll be set.<br /> <br /> ===Network Summary===<br /> Ports used by The Ur-Quan Masters:<br /> *TCP port 21837<br /> *(reserved for the future) UDP port 21837 (not currently used)<br /> *(reserved for the future) TCP port 21836 (not currently used; for the meta-server)<br /> <br /> ==Alternative: Using Hamachi==<br /> Hamachi is a program which can usually obviate the need to do all the network settings above.<br /> <br /> The disadvantage is that you can only play against other Hamachi users.<br /> <br /> [TODO]<br /> <br /> <br /> ==Finding someone to play against==<br /> The IRC channel [irc://irc.freenode.net/#uqm-arena #uqm-arena] on irc.freenode.net is a good place to find people to eat your flaming plasma death.<br /> <br /> ==Running the game==<br /> ===Command-line switches===<br /> [TODO]<br /> See the [http://http://sc2.cvs.sourceforge.net/sc2/sc2/doc/users/netplay-howto.txt?view=markup netplay-howto.txt] file that came with the source for now.<br /> <br /> ===Starting a netplay game===<br /> [TODO]<br /> <br /> ==When it's not working==<br /> ===If you cannot establish a connection===<br /> This is usually caused by a routing of firewalling problem. See above.<br /> [TODO]<br /> <br /> ===If you can establish a connection, but are immediately disconnected===<br /> This will happen when the local and remote versions of The Ur-Quan Masters aren't compatible with eachother. Both players should upgrade to the latest version.<br /> Some time in the future, there will be a nicer error message.<br /> <br /> ===If the game aborts immediately after starting the battle===<br /> This usually happens if one player has installed some melee-affecting add-on, while the other player has not.<br /> <br /> It can also happen if one player isn't using the latest content upgrade to go with the UQM version he is using.<br /> <br /> ==Caveats==<br /> Netplay is still in the testing phase, so don't be surprised of the incidental crash or disconnect because of loss of synchronisation.<br /> See [[#If you've found a bug]].<br /> <br /> ==If you've found a bug==<br /> Bugs should go to the project's Bugzilla [http://bugs.uqm.stack.nl/ bug database]. Be verbose.</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Netplay_howto&diff=14037 Netplay howto 2006-11-03T08:46:04Z

<p>Fossil: /* Router basics */</p> <hr /> <div>This page describes how to play [[SuperMelee]] in [[The Ur-Quan Masters]] over a network. Take your time and read it thoroughly; every word is there for a reason.<br /> <br /> __TOC__<br /> <br /> <br /> ==Installing a network-capable version of The Ur-Quan Masters==<br /> Netplay is still in the testing phase, and there hasn't been a release yet which includes netplay. So to play netplay, you need the more recent developer sources. If you know how to compile the game yourself, you can just download the [http://sourceforge.net/cvs/?group_id=59452 latest sources from CVS] and compile as usual.<br /> <br /> If you're a Windows user, there is an easier way to go:<br /> #First, install the [http://sc2.sourceforge.net/downloads.php 0.5.0 release] of the game as normally. Do not install any melee-altering add-on packs unless your opponent has them installed too. Otherwise the two parties would lose synchronisation and the game would be aborted. Audio packs should be ok though.<br /> #From the [http://uqm.stack.nl/files/snapshots/ CVS snapshots page] download the latest precompiled binary (either release or debug; the debug version may give more information to help the developers if a bug occurs; the release version will be faster), as well as the latest content update.<br /> #Unpack the downloaded file (you will need a program such as [http://www.winzip.com/ WinZip] for this). You will end up with an <code>uqm.exe</code> or <code>uqm-debug.exe</code> file.<br /> #Find the <code>uqm.exe</code> file that came with 0.5.0, and replace it by the extracted .exe file (if you have <code>uqm-debug.exe</code> rename it to <code>uqm.exe</code>). If you installed The Ur-Quan Masters in the default location, you'll find it in <code>C:\Program Files\The Ur-Quan Masters\</code>).<br /> #In the folder where you found the <code>uqm.exe</code> file, there's another folder named <code>packages</code>, which contains the file <code>uqm-0.5.0-content.uqm</code> (and possibly other .uqm files for alternative music). Put the downloaded content update .zip file in here. '''DO NOT UNPACK THIS FILE!'''. The game knows how to read the files from inside the archive.<br /> If you later want to upgrade, just remove the old content upgrade .zip file and redo steps 2 and onwards.<br /> <br /> ==Setting up the network==<br /> <br /> Network experts can skip to the section "Settings Summary". For the others, read on, everything will be explained.<br /> <br /> ===Introduction===<br /> ====Network basics====<br /> Every computer on the internet has an ''internet address'', consisting of 4 numbers seperated by periods, like <code>131.155.140.133</code>. Information sent over the internet is split up in ''packets'', each packet labeled with the destination address.<br /> <br /> A computer may also have a ''host name'', like <code>uqm.stack.nl</code>, to make refering to it a bit easier to read for humans. When information needs to be sent to a computer known only by host name, its address will first be looked up.<br /> <br /> A computer may run many programs simultaneously which want to receive information from over the network. To direct packets to the correct program, the address will include a number known as the ''port number'' or ''port'' for short. The Ur-Quan Masters accepts packets sent to port ''21837''.<br /> <br /> ====Router basics====<br /> The little box which comes with most modern internet subscriptions is a ''router''. A router is a device which passes packets to other computer.<br /> <br /> Several computer may be connected to a single router, but usually there's only one internet address for one router (the ''public address''). To be able to address the different computers connected to the router, the router gives them all a ''local address''. Special ranges of address are reserved for use like this (192.168.x.x, 10.x.x.x and 172.16.x.x through 172.31.x.x); these addresses are not accessible directly from the internet.<br /> <br /> When a local computer sends a packet over the internet to another computer, the router will replace the return address (which was the local address) with the public address, and send it along.<br /> And when a packet arrives from the internet, the router will change the destination address (which was the public address) to the address of the local computer for which it was destined.<br /> This relabeling is usually called ''NAT'' (for ''Network Address Translation'').<br /> <br /> And this is where the problems begin. How is a router to know for which local computer a packet is destined? The packet only comes with the public address and a port number.<br /> <br /> When a local computer sends packets first, the router can look at the originating address and port and remember them, so that when a reply comes to the same port, it knows for which computer it is meant.<br /> <br /> But if packets arrive from a computer over the internet out of the blue, the router does not know to which local computer it should direct them. (Even when there's only one local computer, most routers will just throw such packets away.) In this case, you need to tell your router explicitely where packets that match a specific pattern need to be sent to. For instance, you could tell it that packets that arrive for port 21837 should go to the computer with local address 192.168.0.2.<br /> <br /> ====Firewall basics====<br /> A firewall is a program which selectively blocks packets.<br /> <br /> Many programs will have some sort of network functionality, more than you're probably aware of, some which are part of Windows itself. When packets arrive these<br /> y will happilly respond to them. But while you may want to share your files with another local computer, you may not want your neighbours to see them. And every program that is accessible could also contain a bug that could compromise your system.<br /> <br /> This is where firewalls come in. They have rules which govern which packets are allowed to pass through unhindered, and which are blocked. And because it's better to be safe than sorry, firewalls usually block everything they don't know.<br /> <br /> So when you're running a program that needs to access the internet, you'll need to tell your firewall to allow it. A firewall may be running on your local computer (Windows XP has one built in), but your router may also have one. Frequently, both will. Both may have to be instructed to allow your packets.<br /> <br /> ===Finding out what your local address is===<br /> In Windows:<br /> *from the start menu, select "Run..."<br /> *type "cmd /K ipconfig" (on Windows 2000 and Windows XP), or "command /K ipconfig" (on older Windows versions)<br /> *the line saying "IP address" will contain your local address. You can ignore the rest.<br /> <br /> ===Finding out what your public address is===<br /> As your public address is sent as the return address everywhere you go on the internet, you just need to visit a web site that reports it back. [http://www.whatsmyip.org/ http://www.whatsmyip.org/] will do. You'll see your public internet address in big letters on the top of the page.<br /> <br /> Note that your ISP may give you a different public internet address each time your router asks for one (after a reboot of the router perhaps). Check, if you aren't sure.<br /> <br /> ===Finding out what your hostname is===<br /> [TODO]<br /> <br /> If you're logged in on IRC (see [#Finding someone to play against]), you can use the command <code>/whois</code> to find out what your hostname is. If your public internet address has no hostname, this will show your local address.<br /> <br /> ===Telling your router to forward UQM packets===<br /> There are many different routers, so this section will not contain specific instructions. You will need to find your router's manual, or find information on the internet. Typically, you use a web browser to connect to your router's own local internet address. Often [http://192.168.0.1/ http://192.168.0.1/], [http://192.168.1.1/ http://192.168.1.1/], or [http://10.0.0.1/ http://10.0.0.1/]. You'll probably need a password too.<br /> <br /> When you're logged in, look for a section with a name like "NAT", "IP masquerading" (another word for NAT), or "port forwarding".<br /> <br /> You'll need to tell it to forward packets addressed to port 21837 to port 21837 on your local address (see [[#Finding out what your local address is]]).<br /> <br /> If the router configuration doesn't work with single ports, but instead takes a range of addresses to forward, just use the range "21837-21837".<br /> <br /> If it wants to know a specific ''protocol'' (a class of packets) of packets to forward, use "TCP" (but The Ur-Quan Masters might use "UDP" in the future).<br /> <br /> The Ur-Quan Masters will probably also use port 21836 in the future, so you might as well forward it too.<br /> <br /> ===Telling your router's firewall not to block UQM packets===<br /> In the router's configuration menu (see [[#Telling your router to forward UQM packets|above]]), look for a section named something like "firewall" or "packet filtering".<br /> <br /> To allow incoming UQM packets, add a rule to pass packets from any address, from any port, to the public address, to port 21837. If it wants to know the protocol for the packets too, use "TCP" (but "UDP" may be used too in the future).<br /> <br /> Your router will likely allow any outgoing packets, so you probably won't have to add a rule for that, but if you do, it would look like this: pass packets from the public address, from port 21837, to any address, to any port.<br /> <br /> ===Telling your computer's firewall not to block UQM packets===<br /> This varies per firewall software.<br /> <br /> Using Windows XP's own firewall (be sure you have the latest Windows XP service pack installed), you will get a popup dialog when a program first tries to send packets, or begins to ''listen'' for incoming packets. Just start UQM, try to establish an incoming or outgoing connection as normal (see [[#Running the game|below]]), and when you get the popup, allow the incoming or outgoing connection attempt, and you'll be set.<br /> <br /> ===Network Summary===<br /> Ports used by The Ur-Quan Masters:<br /> *TCP port 21837<br /> *(reserved for the future) UDP port 21837 (not currently used)<br /> *(reserved for the future) TCP port 21836 (not currently used; for the meta-server)<br /> <br /> ==Alternative: Using Hamachi==<br /> Hamachi is a program which can usually obviate the need to do all the network settings above.<br /> <br /> The disadvantage is that you can only play against other Hamachi users.<br /> <br /> [TODO]<br /> <br /> <br /> ==Finding someone to play against==<br /> The IRC channel [irc://irc.freenode.net/#uqm-arena #uqm-arena] on irc.freenode.net is a good place to find people to eat your flaming plasma death.<br /> <br /> ==Running the game==<br /> ===Command-line switches===<br /> [TODO]<br /> See the [http://http://sc2.cvs.sourceforge.net/sc2/sc2/doc/users/netplay-howto.txt?view=markup netplay-howto.txt] file that came with the source for now.<br /> <br /> ===Starting a netplay game===<br /> [TODO]<br /> <br /> ==When it's not working==<br /> ===If you cannot establish a connection===<br /> This is usually caused by a routing of firewalling problem. See above.<br /> [TODO]<br /> <br /> ===If you can establish a connection, but are immediately disconnected===<br /> This will happen when the local and remote versions of The Ur-Quan Masters aren't compatible with eachother. Both players should upgrade to the latest version.<br /> Some time in the future, there will be a nicer error message.<br /> <br /> ===If the game aborts immediately after starting the battle===<br /> This usually happens if one player has installed some melee-affecting add-on, while the other player has not.<br /> <br /> It can also happen if one player isn't using the latest content upgrade to go with the UQM version he is using.<br /> <br /> ==Caveats==<br /> Netplay is still in the testing phase, so don't be surprised of the incidental crash or disconnect because of loss of synchronisation.<br /> See [[#If you've found a bug]].<br /> <br /> ==If you've found a bug==<br /> Bugs should go to the project's Bugzilla [http://bugs.uqm.stack.nl/ bug database]. Be verbose.</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Netplay_howto&diff=14036 Netplay howto 2006-11-03T08:42:36Z

<p>Fossil: /* Installing a network-capable version of The Ur-Quan Masters */</p> <hr /> <div>This page describes how to play [[SuperMelee]] in [[The Ur-Quan Masters]] over a network. Take your time and read it thoroughly; every word is there for a reason.<br /> <br /> __TOC__<br /> <br /> <br /> ==Installing a network-capable version of The Ur-Quan Masters==<br /> Netplay is still in the testing phase, and there hasn't been a release yet which includes netplay. So to play netplay, you need the more recent developer sources. If you know how to compile the game yourself, you can just download the [http://sourceforge.net/cvs/?group_id=59452 latest sources from CVS] and compile as usual.<br /> <br /> If you're a Windows user, there is an easier way to go:<br /> #First, install the [http://sc2.sourceforge.net/downloads.php 0.5.0 release] of the game as normally. Do not install any melee-altering add-on packs unless your opponent has them installed too. Otherwise the two parties would lose synchronisation and the game would be aborted. Audio packs should be ok though.<br /> #From the [http://uqm.stack.nl/files/snapshots/ CVS snapshots page] download the latest precompiled binary (either release or debug; the debug version may give more information to help the developers if a bug occurs; the release version will be faster), as well as the latest content update.<br /> #Unpack the downloaded file (you will need a program such as [http://www.winzip.com/ WinZip] for this). You will end up with an <code>uqm.exe</code> or <code>uqm-debug.exe</code> file.<br /> #Find the <code>uqm.exe</code> file that came with 0.5.0, and replace it by the extracted .exe file (if you have <code>uqm-debug.exe</code> rename it to <code>uqm.exe</code>). If you installed The Ur-Quan Masters in the default location, you'll find it in <code>C:\Program Files\The Ur-Quan Masters\</code>).<br /> #In the folder where you found the <code>uqm.exe</code> file, there's another folder named <code>packages</code>, which contains the file <code>uqm-0.5.0-content.uqm</code> (and possibly other .uqm files for alternative music). Put the downloaded content update .zip file in here. '''DO NOT UNPACK THIS FILE!'''. The game knows how to read the files from inside the archive.<br /> If you later want to upgrade, just remove the old content upgrade .zip file and redo steps 2 and onwards.<br /> <br /> ==Setting up the network==<br /> <br /> Network experts can skip to the section "Settings Summary". For the others, read on, everything will be explained.<br /> <br /> ===Introduction===<br /> ====Network basics====<br /> Every computer on the internet has an ''internet address'', consisting of 4 numbers seperated by periods, like <code>131.155.140.133</code>. Information sent over the internet is split up in ''packets'', each packet labeled with the destination address.<br /> <br /> A computer may also have a ''host name'', like <code>uqm.stack.nl</code>, to make refering to it a bit easier to read for humans. When information needs to be sent to a computer known only by host name, its address will first be looked up.<br /> <br /> A computer may run many programs simultaneously which want to receive information from over the network. To direct packets to the correct program, the address will include a number known as the ''port number'' or ''port'' for short. The Ur-Quan Masters accepts packets sent to port ''21837''.<br /> <br /> ====Router basics====<br /> The little box which comes with most modern internet subscriptions is a ''router''. A router is a device which passes packets to other computer.<br /> <br /> Several computer may be connected to a single router, but usually there's only one internet address for one router (the ''public address''). To be able to address the different computers connected to the router, the router gives them all a ''local address''. Special ranges of address are reserved for use like this (192.168.x.x, 10.x.x.x and 172.16.x.x through 172.31.x.x); these addresses are not accessible directly from the internet.<br /> <br /> When a local computer sends a packet over the internet to another computer, the router will replace the return address (which was the local address) by the public address, and send it along.<br /> And when a packet arrives from over the internet, the router will change the destination address (which was the public address) by the address of the local computer for which it was destined.<br /> This relabeling is usually called ''NAT'' (for ''Network Address Translation'').<br /> <br /> And this is where the problems begin. How is a router to know for which local computer a packet is destined? The packet only comes with the public address and a port number.<br /> <br /> When a local computer sends packets first, the router can look at the originating address and port and remember them, so that when a reply comes to the same port, it knows for which computer it is meant.<br /> <br /> But if packets arrive from a computer over the internet out of the blue, the router does not know to which local computer it should direct them. (Even when there's only one local computer, most routers will just throw such packets away.) In this case, you need to tell your router explicitely where packets that match a specific pattern need to be sent to. For instance, you could tell it that packets that arrive for port 21837 should go to the computer with local address 192.168.0.2.<br /> <br /> ====Firewall basics====<br /> A firewall is a program which selectively blocks packets.<br /> <br /> Many programs will have some sort of network functionality, more than you're probably aware of, some which are part of Windows itself. When packets arrive these<br /> y will happilly respond to them. But while you may want to share your files with another local computer, you may not want your neighbours to see them. And every program that is accessible could also contain a bug that could compromise your system.<br /> <br /> This is where firewalls come in. They have rules which govern which packets are allowed to pass through unhindered, and which are blocked. And because it's better to be safe than sorry, firewalls usually block everything they don't know.<br /> <br /> So when you're running a program that needs to access the internet, you'll need to tell your firewall to allow it. A firewall may be running on your local computer (Windows XP has one built in), but your router may also have one. Frequently, both will. Both may have to be instructed to allow your packets.<br /> <br /> ===Finding out what your local address is===<br /> In Windows:<br /> *from the start menu, select "Run..."<br /> *type "cmd /K ipconfig" (on Windows 2000 and Windows XP), or "command /K ipconfig" (on older Windows versions)<br /> *the line saying "IP address" will contain your local address. You can ignore the rest.<br /> <br /> ===Finding out what your public address is===<br /> As your public address is sent as the return address everywhere you go on the internet, you just need to visit a web site that reports it back. [http://www.whatsmyip.org/ http://www.whatsmyip.org/] will do. You'll see your public internet address in big letters on the top of the page.<br /> <br /> Note that your ISP may give you a different public internet address each time your router asks for one (after a reboot of the router perhaps). Check, if you aren't sure.<br /> <br /> ===Finding out what your hostname is===<br /> [TODO]<br /> <br /> If you're logged in on IRC (see [#Finding someone to play against]), you can use the command <code>/whois</code> to find out what your hostname is. If your public internet address has no hostname, this will show your local address.<br /> <br /> ===Telling your router to forward UQM packets===<br /> There are many different routers, so this section will not contain specific instructions. You will need to find your router's manual, or find information on the internet. Typically, you use a web browser to connect to your router's own local internet address. Often [http://192.168.0.1/ http://192.168.0.1/], [http://192.168.1.1/ http://192.168.1.1/], or [http://10.0.0.1/ http://10.0.0.1/]. You'll probably need a password too.<br /> <br /> When you're logged in, look for a section with a name like "NAT", "IP masquerading" (another word for NAT), or "port forwarding".<br /> <br /> You'll need to tell it to forward packets addressed to port 21837 to port 21837 on your local address (see [[#Finding out what your local address is]]).<br /> <br /> If the router configuration doesn't work with single ports, but instead takes a range of addresses to forward, just use the range "21837-21837".<br /> <br /> If it wants to know a specific ''protocol'' (a class of packets) of packets to forward, use "TCP" (but The Ur-Quan Masters might use "UDP" in the future).<br /> <br /> The Ur-Quan Masters will probably also use port 21836 in the future, so you might as well forward it too.<br /> <br /> ===Telling your router's firewall not to block UQM packets===<br /> In the router's configuration menu (see [[#Telling your router to forward UQM packets|above]]), look for a section named something like "firewall" or "packet filtering".<br /> <br /> To allow incoming UQM packets, add a rule to pass packets from any address, from any port, to the public address, to port 21837. If it wants to know the protocol for the packets too, use "TCP" (but "UDP" may be used too in the future).<br /> <br /> Your router will likely allow any outgoing packets, so you probably won't have to add a rule for that, but if you do, it would look like this: pass packets from the public address, from port 21837, to any address, to any port.<br /> <br /> ===Telling your computer's firewall not to block UQM packets===<br /> This varies per firewall software.<br /> <br /> Using Windows XP's own firewall (be sure you have the latest Windows XP service pack installed), you will get a popup dialog when a program first tries to send packets, or begins to ''listen'' for incoming packets. Just start UQM, try to establish an incoming or outgoing connection as normal (see [[#Running the game|below]]), and when you get the popup, allow the incoming or outgoing connection attempt, and you'll be set.<br /> <br /> ===Network Summary===<br /> Ports used by The Ur-Quan Masters:<br /> *TCP port 21837<br /> *(reserved for the future) UDP port 21837 (not currently used)<br /> *(reserved for the future) TCP port 21836 (not currently used; for the meta-server)<br /> <br /> ==Alternative: Using Hamachi==<br /> Hamachi is a program which can usually obviate the need to do all the network settings above.<br /> <br /> The disadvantage is that you can only play against other Hamachi users.<br /> <br /> [TODO]<br /> <br /> <br /> ==Finding someone to play against==<br /> The IRC channel [irc://irc.freenode.net/#uqm-arena #uqm-arena] on irc.freenode.net is a good place to find people to eat your flaming plasma death.<br /> <br /> ==Running the game==<br /> ===Command-line switches===<br /> [TODO]<br /> See the [http://http://sc2.cvs.sourceforge.net/sc2/sc2/doc/users/netplay-howto.txt?view=markup netplay-howto.txt] file that came with the source for now.<br /> <br /> ===Starting a netplay game===<br /> [TODO]<br /> <br /> ==When it's not working==<br /> ===If you cannot establish a connection===<br /> This is usually caused by a routing of firewalling problem. See above.<br /> [TODO]<br /> <br /> ===If you can establish a connection, but are immediately disconnected===<br /> This will happen when the local and remote versions of The Ur-Quan Masters aren't compatible with eachother. Both players should upgrade to the latest version.<br /> Some time in the future, there will be a nicer error message.<br /> <br /> ===If the game aborts immediately after starting the battle===<br /> This usually happens if one player has installed some melee-affecting add-on, while the other player has not.<br /> <br /> It can also happen if one player isn't using the latest content upgrade to go with the UQM version he is using.<br /> <br /> ==Caveats==<br /> Netplay is still in the testing phase, so don't be surprised of the incidental crash or disconnect because of loss of synchronisation.<br /> See [[#If you've found a bug]].<br /> <br /> ==If you've found a bug==<br /> Bugs should go to the project's Bugzilla [http://bugs.uqm.stack.nl/ bug database]. Be verbose.</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Gameplay_Challenges&diff=4392 Gameplay Challenges 2005-04-12T04:53:12Z

<p>Fossil: /* Don't visit the Starbase */</p> <hr /> <div>Once you first finished the [[Star Control II]] game, you may like to play the game in another way.<br /> This page will describes various challenges that may make it interesting to replay the game.<br /> <br /> __TOC__<br /> <br /> ==The Challenges==<br /> <br /> ===Complete the optional quests===<br /> Some quests are optional. You may already have solved these quests when you first finished the games, but if you haven't, it's worth another play. Things you may want to do:<br /> *Start the [[Yehat]] civil war<br /> *Take care of the [[Slylandro]] [[Probe]] plague<br /> *Rescue the [[Zoq-Fot-Pik]]<br /> *Get all items you don't necessarilly need ([[Portal Spawner]], both [[HyperWave Broadcaster]]s)<br /> *Ally with everyone you can ([[Orz]], [[Pkunk]], [[Shofixti]], [[Syreen]], [[Supox]], [[Thraddash]], [[Utwig]], [[Yehat]] (rebels), Zoq-Fot-Pik)<br /> <br /> <br /> ===Time trial===<br /> Try to finish the game in as little time as possible. The best reported time so far is October 5 2155, without any optional quests.<br /> <br /> <br /> ===Don't mine===<br /> Never mine anything, or sell fuel you bought from the [[Melnorme]]. Your money will have to come from fighting.<br /> <br /> <br /> ===Be the bad guy===<br /> The game gets significantly more difficult without your friends (particularly the [[Melnorme]]). Piss off everyone you meet, or attack at sight. To stay into character, name your "alliance" "The Empire of ...", and sell your crew to the Druuge.<br /> <br /> ===Don't visit the [[Starbase]]===<br /> A very difficult challenge, and it requires a lot of patience. Until you have access to the StarBase, every day in [[HyperSpace]] a [[Slylandro]] [[Probe]] will show up (even after you've acquired the self-destruct code). As you've got no way of upgrading your engines you can't outrun them, so be prepared to fight a lot, at least until you can get them to self-destruct. You will end up with mountains of money, but you've got nowhere to spend it.<br /> Among other problems are: you can't replenish your crew, so you're dependant on your good fighting skills and gifts of other races; you have no Emergency [[Warp Escape Unit]], so you cannot run away from a fight in progress; and no slave trading.<br /> <br /> ==See Also==<br /> *[[Supermelee Challenges]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Gameplay_Challenges&diff=4391 Gameplay Challenges 2005-04-12T04:51:31Z

<p>Fossil: /* Don't visit the Starbase */</p> <hr /> <div>Once you first finished the [[Star Control II]] game, you may like to play the game in another way.<br /> This page will describes various challenges that may make it interesting to replay the game.<br /> <br /> __TOC__<br /> <br /> ==The Challenges==<br /> <br /> ===Complete the optional quests===<br /> Some quests are optional. You may already have solved these quests when you first finished the games, but if you haven't, it's worth another play. Things you may want to do:<br /> *Start the [[Yehat]] civil war<br /> *Take care of the [[Slylandro]] [[Probe]] plague<br /> *Rescue the [[Zoq-Fot-Pik]]<br /> *Get all items you don't necessarilly need ([[Portal Spawner]], both [[HyperWave Broadcaster]]s)<br /> *Ally with everyone you can ([[Orz]], [[Pkunk]], [[Shofixti]], [[Syreen]], [[Supox]], [[Thraddash]], [[Utwig]], [[Yehat]] (rebels), Zoq-Fot-Pik)<br /> <br /> <br /> ===Time trial===<br /> Try to finish the game in as little time as possible. The best reported time so far is October 5 2155, without any optional quests.<br /> <br /> <br /> ===Don't mine===<br /> Never mine anything, or sell fuel you bought from the [[Melnorme]]. Your money will have to come from fighting.<br /> <br /> <br /> ===Be the bad guy===<br /> The game gets significantly more difficult without your friends (particularly the [[Melnorme]]). Piss off everyone you meet, or attack at sight. To stay into character, name your "alliance" "The Empire of ...", and sell your crew to the Druuge.<br /> <br /> ===Don't visit the [[Starbase]]===<br /> A very difficult challenge, and it requires a lot of patience. Until you have access to the StarBase, every day in [[HyperSpace]] a [[Slylandro]] [[Probe]] will show up (even after you've acquired the self-destruct code). As you've got no way of upgrading your engines you can't outrun them, so be prepared to fight a lot, at least until you can get them to self-destruct. You will end up with mountains of money, but you've got nowhere to spend it.<br /> Among other problems are: you can't replenish your crew, so you're dependant on your good fighting skills and gifts of other races; you have no Emergency [[Warp Escape]] unit, so you cannot run away from a fight in progress; and no slave trading.<br /> <br /> ==See Also==<br /> *[[Supermelee Challenges]]</div>

Fossil https://wiki.uqm.stack.nl/index.php?title=Gameplay_Challenges&diff=4390 Gameplay Challenges 2005-04-12T04:50:05Z

<p>Fossil: /* Don't visit the Starbase */</p> <hr /> <div>Once you first finished the [[Star Control II]] game, you may like to play the game in another way.<br /> This page will describes various challenges that may make it interesting to replay the game.<br /> <br /> __TOC__<br /> <br /> ==The Challenges==<br /> <br /> ===Complete the optional quests===<br /> Some quests are optional. You may already have solved these quests when you first finished the games, but if you haven't, it's worth another play. Things you may want to do:<br /> *Start the [[Yehat]] civil war<br /> *Take care of the [[Slylandro]] [[Probe]] plague<br /> *Rescue the [[Zoq-Fot-Pik]]<br /> *Get all items you don't necessarilly need ([[Portal Spawner]], both [[HyperWave Broadcaster]]s)<br /> *Ally with everyone you can ([[Orz]], [[Pkunk]], [[Shofixti]], [[Syreen]], [[Supox]], [[Thraddash]], [[Utwig]], [[Yehat]] (rebels), Zoq-Fot-Pik)<br /> <br /> <br /> ===Time trial===<br /> Try to finish the game in as little time as possible. The best reported time so far is October 5 2155, without any optional quests.<br /> <br /> <br /> ===Don't mine===<br /> Never mine anything, or sell fuel you bought from the [[Melnorme]]. Your money will have to come from fighting.<br /> <br /> <br /> ===Be the bad guy===<br /> The game gets significantly more difficult without your friends (particularly the [[Melnorme]]). Piss off everyone you meet, or attack at sight. To stay into character, name your "alliance" "The Empire of ...", and sell your crew to the Druuge.<br /> <br /> ===Don't visit the [[Starbase]]===<br /> A very difficult challenge, and it requires a lot of patience. Until you have access to the StarBase, every day in [[HyperSpace]] a [[Slylandro]] [[Probe]] will show up (even after you've acquired the self-destruct code). As you've got no way of upgrading your engines you can't outrun them, so be prepared to fight a lot, at least until you can get them to self-destruct. You will end up with mountains of money, but you've got nowhere to spend it.<br /> Among other problems are: you can't replenish your crew, so you're dependant on your good fighting skills and gifts of other races; you have no Emergency [[Warp Escape]] unit; no slave trading.<br /> <br /> ==See Also==<br /> *[[Supermelee Challenges]]</div>

Fossil