Tremulous Forum

Media => Map Releases => Topic started by: newsource on June 14, 2014, 09:44:55 am

Title: South Park Map for Tremulous By New Source
Post by: newsource on June 14, 2014, 09:44:55 am
hi guys:)))

i maded in gtkradiant map for Tremulous, SouthPark. this map is very  copy city of South park=))

P.S Him my  first  map...



Download - https://yadi.sk/d/Z1sNMPdSTMRQR
Download (mirror#1) - http://www.mediafire.com/download/gyqbscmdibk4hvz/map-southpark-b1.pk3
Download (mirror#2) - https://www.dropbox.com/s/g1xe8mkaaqtizb3/map-southpark-b1.pk3?m=
Title: Re: South Park Map for Tremulous By New Source
Post by: /dev/humancontroller on June 14, 2014, 04:10:39 pm
some comments:
Title: Re: South Park Map for Tremulous By New Source
Post by: /dev/humancontroller on June 14, 2014, 09:44:16 pm
This map was created mostly for cartoon South Park fans and the game itself Tremulous she comes not.

I did and good maps, soon I'll post them, and This map is essentially a joke =)
i don't understand your (non-)english.
btw, joke maps are good for creating alternative (not so boring) chat rooms.
Title: Re: South Park Map for Tremulous By New Source
Post by: Celestial_Rage on June 19, 2014, 06:39:54 am
Actually, storing the .map file is recommended so new mappers can learn from and build off your work.
Title: Re: South Park Map for Tremulous By New Source
Post by: /dev/humancontroller on June 19, 2014, 06:06:00 pm
Actually, storing the .map file is recommended so new mappers can learn from and build off your work.
storing the .map inside the pk3 file should not be done, simply because the .map file does not belong there, period. only include final, compiled content (to the extent possible). do not include .psd (Photoshop project file), .flp (FL Studio project file), .c/.h (source code), .map (*radiant source map), etc.; these files should be published separately, elsewhere, without bloating the "binary engine-cartridges" (pk3 files).
Title: Re: South Park Map for Tremulous By New Source
Post by: Ingar on September 28, 2015, 06:25:43 pm
Actually, storing the .map file is recommended so new mappers can learn from and build off your work.
storing the .map inside the pk3 file should not be done, simply because the .map file does not belong there, period. only include final, compiled content (to the extent possible). do not include .psd (Photoshop project file), .flp (FL Studio project file), .c/.h (source code), .map (*radiant source map), etc.; these files should be published separately, elsewhere, without bloating the "binary engine-cartridges" (pk3 files).

I disagree. .map files tend to get lost. The pk3 should contain the files required to recompile it with q3map2. This includes
.map files and stuff like .obj and .ase models. Stuff like blender files, photoshop files etc should not be included because
they're not required to compile that map.

So, in theory, you're right. In practice, you're wrong.