q3 compatibility with q1 and q2 maps?

Article View: alt.games.quake3

Article #287198

#287198

From: Todd
Date: Sun, 26 Apr 2009 04:18

9 lines
1590 bytes

I downloaded a bunch of maps from FileFront and have finally gotten
around to playing them.  As always happens with these guys,
occasionally, maps show up under the wrong games.  Most Quake 3 maps
are in pk3 files, but there are a few that aren't.  Apparently, some
of these are Quake 2 or Quake 1.  Since the map file for Quake games
has always ended in bsp, there's no way to tell just by looking if
these maps belong to the older games.

What will happen if I try to run a Q1 or Q2 map under Quake 3?

Technical Details

Message-ID: <oon7v4dl23h0d9ettpcmteg7atfmtqvl4a@4ax.com>

Path:

mbox-mo1.pugleaf.net!border1.nntp.ams.giganews.com!nntp.giganews.com!feeder.news-service.com!newshub.sdsu.edu!flph200.ffdc.sbc.com!prodigy.net!flph199.ffdc.sbc.com!prodigy.com!flpi107.ffdc.sbc.com!nlpi067.nbdc.sbc.com.POSTED!2bdf0420!not-for-mail

Show Full Headers

Complete Article Headers

Path: mbox-mo1.pugleaf.net!border1.nntp.ams.giganews.com!nntp.giganews.com!feeder.news-service.com!newshub.sdsu.edu!flph200.ffdc.sbc.com!prodigy.net!flph199.ffdc.sbc.com!prodigy.com!flpi107.ffdc.sbc.com!nlpi067.nbdc.sbc.com.POSTED!2bdf0420!not-for-mail
From: Todd <noone@nowhere.com>
Newsgroups: alt.games.quake3
Subject: q3 compatibility with q1 and q2 maps?
Message-ID: <oon7v4dl23h0d9ettpcmteg7atfmtqvl4a@4ax.com>
X-Newsreader: Forte Agent 1.93/32.576 English (American)
MIME-Version: 1.0
Lines: 11
NNTP-Posting-Host: 67.181.194.72
X-Complaints-To: abuse@prodigy.net
X-Trace: nlpi067.nbdc.sbc.com 1240719521 ST000 67.181.194.72 (Sun, 26 Apr 2009 00:18:41 EDT)
NNTP-Posting-Date: Sun, 26 Apr 2009 00:18:41 EDT
Organization: at&t http://my.att.net/
X-UserInfo1: FKPO@MC@@S@[SQXYJRIVNFXBWR\HPCTL@XT^OBPLAH[\RYIBK^RAQFW[ML\THRCKV^GGZKJMGV^^_JSCFFUA_QXFGVSCYRPILH]TRVKC^LSN@DX_HCAFX__@J\DAJBVMY\ZWZCZLPA^MVH_P@\\EOMW\YSXHG__IJQY_@M[A[[AXQ_XDSTAR]\PG]NVAQUVM
Date: Sat, 25 Apr 2009 21:18:38 -0700
Bytes: 1582
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit