Spirit requested at least some minimal docs. Here's a brief quick-start guide.

git-svn-id: https://svn.code.sf.net/p/fteqw/code/trunk@4107 fc73d0e0-1445-4013-8a0c-d673dee63da5

README.txt

@@ -0,0 +1,84 @@
+Yay, you found out the secrit location to download the sauce code from!
+
+Right, urm, now what?
+Yeah, good question.
+
+Urm.
+
+
+
+Quick start guide:
+cd engine
+make sv-rel -j4
+make gl-rel -j4
+cd  ..
+engine/release/fteqw.sv -nohome -basedir ~/quake
+engine/release/fteqw.gl -nohome -basedir ~/quake
+
+You do not need to configure. The makefile will automatically do that depending on the target build/system.
+
+
+
+To compile the FTEDroid port with cygwin:
+make droid-rel PATH=C:\Cygwin\bin\ DROID_SDK_PATH=/cygdrive/c/Games/tools/android-sdk DROID_NDK_PATH=/cygdrive/c/Games/tools/android-ndk-r7 ANT=/cygdrive/c/Games/tools/apache-ant-1.8.2/bin/ant JAVATOOL="/cygdrive/c/Program\ Files/Java/jdk1.7.0_02/bin/" DROID_ARCH="armeabi x86" -j4 DROID_PACKSU=/cygdrive/c/games/quake/id1/pak0.pak
+On linux you can omit the PATH, ANT, and JAVATOOL parts as they should already be in the path (yes I copied the above out of a batch file).
+Then install the release/FTEDroid.apk file on your android device.
+The DROID_PACKSU part is used to include the pak file within the android package. Ideally you would use a pk3 file instead. Also you would use something that will not violate iD software's copyright. THIS IS AN EXAMPLE ONLY. You can omit the setting entirely if you require the user to provide their own packages.
+Note that there is no way to install the package with a different name at this time.
+
+
+
+This stuff has separate directories
+engine: FTEQW game engine itself. Both client and dedicated server.
+engine/ftequake: location of old msvc6 project file. Might not work.
+engine/dotnet2005: location of microsoft visual c 2005 project file. Most likely to be up to date, but also most likely to be specific to Spike's config.
+engine/dotnet2010: location of microsoft visual c 2010 (express) project file. Might not work.
+engine/release: the makefile writes its release-build binaries here. Intermediate files are contained within a sub-directory.
+engine/debug: the makefile writes its debug-build binaries here. Intermediate files are contained within a sub-directory.
+fteqtv: the qtv proxy server program.
+plugins: several optional plugins that do various interesting things, though not so interesting
+q3asm2: my quick hack at a qvm assembler which is not horribly slow. ignore it.
+quakec: Various quakec mods. Some interesting, some not.
+quakec/basemod: TimeServ's attempt to bugfix and modify vanilla quake
+quakec/csaddon: ingame csqc-controlled editors. Currently contains the camquake featureset (thanks Jogi), rtlights editor, terrain editor ui, particle editor.
+quakec/csqctest: my csqc sample mod. Originally created as a feature testbed for the csqc api. Useful as a reference/sample, but you perhaps don't want to use it as a base.
+specs: modder/advanced documentation and samples.
+
+
+
+Interesting commandline arguments:
+-nohome         disables the use of home directories. all file access will occur within the gamedir.
+-basedir $FOO   tells the engine where to find the game.
+-game $FOO      traditional NQ way to specify a mod.
+-mem $FOO       may still be needed on linux, at least for now. Not required on windows. Value is in MB.
++sv_public 0    stop the server from reporting to master servers.
+-window         override config files to force fte into windowed mode at startup. Can still be made fullscreen via the menus or console.
+
+
+
+NQ compat cvars:
+sv_port 26000 (fte listens on port 27500 by default, as its derived from quakeworld).
+cl_defaultport 26000 (see above. you can always specify the port in the connect command).
+sv_nomsec 1 (disables player prediction, giving authentic nq player physics).
+sv_listen_nq 1 (if 0, disables NQ clients. if 1, allows qsmurfing. if 2(default), blocks qsmurfing but may have compat issues with some clients).
+
+
+
+Limit breaking stuff:
+pr_maxedicts 32767 (max ent limit)
+sv_bigcoords 1	(expands coord sizes, but has compat issues)
+
+
+
+Hexen2 / Quake2 / Quake3:
+Copy the engine to your h2/q2/q3 dir, and run from there.
+Alternatively, specify the h2/q2/q3 dir via -basedir.
+The engine will autodetect the game from its basedir, and reconfigure as appropriate if appropriate.
+
+
+Problems?
+You can report problems on IRC.
+Join irc.quakenet.org #fte
+
+If you refuse to use IRC, you can instead report issues to Spike via the inside3d.com forums, or the quakeone.com forums, depending on where you're able to create an account.
+Bug reports are (generally) always apreciated! :)