posted 10-29-2000 12:07 PM                  

Most important: All work is to be finished and submitted by December 3rd at the latest

First, since I'm anything but a micromanager, I'm not going to tell you how to do jack squat, as long as you get your shit done on time. I'd like each of the following groups to choose a contact person to keep track of that group and keep me notified of progress and problems. The groups (and definite members) are:

coders
- AgtOrange, LtHawkins, Blaze, Tsunami

modellers/animators
- Cloud, Birdman, Sonic128?

skinners/graphic design
- Infadel, Glok, C00T

mapping [conversion and original]
- Hexydes, Provoker, End

sounds
- Jodo and whoever's helping him

documentation team (manuals and sample configs)
- OzFactor, Zilden, anyone else who put "whatever"

All contact info is currently at http://www.jhereg.net/port/

Second, here's what is absolutely needed for beta1 (after much discussion and research, this is what is doable and needed). Remember, beta1 is deathmatch only.

- Code: Server and client code stable with all core gameplay elements in place
- Weapons: All weapons finished and skinned. Hand animations will have to wait until beta2, just because of the inherent difficulty in properly coding the hands to not show in world view.
- Player models: About 8-10 skins for at least one good model, a base model is ok, but we need our own skins.
- Sounds: weapon sounds are key, radio sounds are not needed until at least beta2 since that's the earliest that teamplay will be implemented
- Graphics: all menu and HUD graphics MUST be done.
- Maps: Since I don't expect any new maps to be finished, the beta1 release will contain 8-10 converted AQ2 maps, with author permissions for ALL maps. No exceptions, we will not be shut down due to theft of intellectual property. (I'd love to see an armyterr port with original, legal textures, but that's just me.)
- Documents: a few really good sample configs will be needed, along with an easily understood readme (HTML will most likely be the method of distribution, both in the package and online).

Seems like a lot, but there's lots of people who are working on this, and its five weeks from today. Get it done and submitted, we'll have an upload ftp set up in the next week for work, and the website will be online and active in the next week.

Good luck and keep us posted.

posted 10-29-2000 02:38 PM               

quote:

---

Originally posted by eLDeR_MMHS:
BTW, I never asked yet, though I've already done some stuff for the project, but am I on the team somewhere?

---

You're now on the contact list.

"The Team" is anyone who makes a significant contribution.

posted 10-29-2000 02:59 PM            

FunOne: Source for AQ2 is at aq2.action-web.net I believe. Source for Q3 is available on FilePlanet or id's FTP.

e-mail: [email protected]
ICQ: 3302949 (Elder_MMHS)

------------------
-Victor Chow (eLDeR_MMHS)
Don't let the last name fool you-
I'm as white as you are. :)

posted 10-29-2000 03:36 PM            

If you 2 think that's good, bad, possibly ugly, let me know. ICQ is 8027433 FYI.

posted 10-29-2000 06:26 PM                  

are we using the same weapon names so i can know what to call each sound

posted 10-29-2000 07:17 PM                  

quote:

---

Originally posted by ScaryMalcolm:
The names don't make a difference, you could name them 1.wav, 2.wav, 3.wav etc and it'd still be fine

---

Technically, no, they don't matter. But you could also, technically, give a random ten digit number to every non-system file on your hard disk as its filename.

posted 10-29-2000 07:33 PM               

-Gameplay modes: Deathmatch
-Weapons: MP5/10 Submachinegun, M4 Assault Rifle, MK23 Pistol, SSG 3000 Sniper Rifle, Handcannon, a shotgun (SPAS 12 or Super 90), combat knives)
-Sounds: Basic AQ2 Weapon/effect sounds for now...
-Major Code items: Door code (press a key to open and to close, unless the door swings automatically), Ladders (I think this will be a map entity), Locational Damage, Falling Damage, Bleeding from wounds, Accuracy/spread modifiers (weapon specific).
-Items: Laser sight, silencer, kevlar vest, bandolier, stealth slippers.
-Maps: Hostage, Office3, Subway2, Basev28, bldg17, ruins, sludge1. (this isn't the official list, but it would be nice to see some of these as they are good for DM).

Let me know if this looks wrong, or if you have anything to add that I missed.

-SpecOps

EDIT: forgot to put in items...

posted 10-30-2000 06:41 AM               

End

------------------
Endz0r's Page!

- Porn, Sports, Games, News! wh33

posted 10-30-2000 11:42 AM               

I'm assuming binding keys works the same way as it does in Q2...? (bind )

posted 11-02-2000 06:13 PM                  

How many damn times have I stated I'll help with mapping?

posted 11-02-2000 07:46 PM                  

do this to add ladders to your maps:

6. PUTTING LADDERS IN MAPS
There we go, the Ladder code is done. But, we still have a problem. Ladders don't seem to work in your maps, even if you did a direct .BSP conversion! Oh no! Easy fix. Have your map designers [or for the versitile, do it yourself] make a box around your ladders. This box should be given a texture of "common/ladderclip". Edit your "quake3\baseq3\scripts\common.shader" file, and insert the lines:
textures/common/ladderclip
{
qer_trans 0.40
surfaceparm nolightmap
surfaceparm nomarks
surfaceparm nodraw
surfaceparm nonsolid
surfaceparm playerclip
surfaceparm noimpact
surfaceparm ladder
}

Before you leave, I'd like to remind you to rebuild BOTH the "game" and "cgame" module. This will the client side prediction work properly with ladders [ aka no shaking like a mofo ]. Compile your map, and there we have it. Working ladders. =)

posted 11-04-2000 01:59 AM                  

but, im ready to rock n roll!

------------------
Sonic128[AISA]

i'm l33t!! and you got kn0x0r3d!!

Weapons Guild