You know what would be cool? If there was a game mode where all players were paired up and one of them had a RL and the other a railgun. Each pair of players should really work together to have the player with the railgun pick off other players from a distance while the RL player fends off enemies that creep up too close

You could even split that up in two modes where in one mode, there's multiple 2-player teams and another mode where it's a sort of tournament mode idea where it's always 2v2 and the losing team is swapped out for another 2 player team (or random selection of two other players, that would be cool too).

But You seem to have hacked a little bit the menus, and for this I admire you, I'm scared of the moment I'll have to do that

I think I could help, though I'm not much sure.

For now I've already done my first try. I think that the first to be done it's that you could choose the weapon when selecting the team and limit the teams to 2 players. For now I've been doing this and I haven't finished yet because there's a bug that I can't understand but I think I'll fix it soon.

You should load up the source on GitHub. I've got tons of fixes, refinements, etc. that I can contribute.

Yeah RL/RG is pretty imbalanced. I know how you like minimalism, but I really think the idea needs expanding. I'd take Eraser's ideas there and go a little further with something like GL, RL, PG for team mates 1 and MG, SG, RG for team mate 2. In this way you still have emphasis on RL+RG but you cover major holes in the gameplay with the extra 4 weapons. The first teammate would have PG to lay cover from long distance enemy RG, and GL to reach where the RL can't. Second teammate have MG to finish off weakened enemies and SG to provide some defense in close range.

If you really want simplicity then instagib RG is the only way to go. As soon as you add one more weapon you'll quickly realize how broken the gameplay can be in situations where one weapon completely dominates another.

I can contribute the following:
- multi-team support for up to 6 teams, which means rewriting the team code entirely
- full widescreen support for HUD and loading screen
- railgun beam fixes, QL-style beam and 25 colors, correct railgun weapon colorization

6 teams... I can use photoshop to colorize the id-models-team skins for the other four teams.
(Green, yellow, cyan and magenta)

There's no need... it's both easier and more efficient on memory to just use bright skins which can share the same shaders but can have any color applied to them. I should probably do team-colored grenades too.

There's no need... it's both easier and more efficient on memory to just use bright skins which can share the same shaders but can have any color applied to them. I should probably do team-colored grenades too.

Well, you'll have to modify the base skins to add an alpha challel that will "stencil" out the coloured parts In the original quake 3 (I don't know about team Arena) each team skin is a separate TGA (this allows to add more that colour difference between characters, changing some details for example).

Hi, I like your work, it's nice.

Though I have two suggestions:

1. If you plan to start from scratch, I highly recommend to use 'Spearmint' engine. It is an enhanced ioquake3 engine.
'Spearmint' already has widscreen support, even HUD is always aspect correct (16:9, 16:10. 4:3, etc.)
Don't get me wrong, I like ioquake3 as well but 'Spearmint' has tons of enhancements (e.g.: 4 player splitscreen) and it is GPLv3.
'Spearmint' also merged cgame and ui module, which makes coding a lot easier.
https://github.com/zturtleman/spearmint/wiki

2. There is no need to remove the code you do not need for 'SlugRock'. If you don't need bots to camp for example, than create a gametype and
exclude your mod from using a function. This way you don't destroy existing gametypes.

Only to make it clear, I don't say something is wrong. Your work is really cool! Just a few thoughts...

Well, you'll have to modify the base skins to add an alpha challel that will "stencil" out the coloured parts In the original quake 3 (I don't know about team Arena) each team skin is a separate TGA (this allows to add more that colour difference between characters, changing some details for example).

Spearmint

Is that what they did to the CPMA player skins?

I should probably do team-colored grenades too.

Especially because he is using code from Jürgen Hoffman (JUHOX).
JUHOX mod(s) inspired many people to make awesome mods, mods that became bigger and bigger... after some time switching to a GPLv3 engine should be considered.

For the UI:
Done - Change the main menu
Done - Change map selection menu
Done - Disable obsolete weapon keys
- Change Playermodel machinegun in RL or RG
- Perhaps add a SlugRock-settings page (in wich you set the cvar's)

For the in-game graphics:
Done - Change HUD, disable ammo and armor counter etc.
Done - Smaller ''You fragged ... for ... place" signal.
- Railcolor tag correction / misslehitwall

For the bot-code:
- Make the bots work without items in the map
- Bot aggression depending on HealthRegen
- Better bots (?)

For the gameplay code:
Done - Only RL and/or RG
Done - healthRegen
- Killable Rockets

I've been these days reading and getting used to git. I think this is a good place to get started:
https://www.atlassian.com/git/tutorial

In addition, is useful to know how to ignore some files like the project or bat files. In this page it's well explained:
https://help.github.com/articles/ignoring-files

The exclude file is very useful because it allows you to ignore locally and don't force the others to do the same. I've used it to ignore all files that aren't code. If you want to do the same, add these lines:
Code:
*
!*/
!*.c
!*.cpp
!*.h

However, the files that are already tracked won't be ignored. There are at least two ways to ignore those files, one way is using --assume-unchanged and another is untracking them, like in this case:
http://stackoverflow.com/questions/1139 ... t-ignoring

The first is useful for files you want to keep in the rep like project files, the second for files you want to keep in the rep but you don't want to share because there's no need, like bat files.

Also I did part of the list (not much):
Quote:
For the UI:
Done - Change the main menu
Done - Change map selection menu
Done - Disable obsolete weapon keys
- Change Playermodel machinegun in RL or RG
- Perhaps add a SlugRock-settings page (in wich you set the cvar's)

For the in-game graphics:
Done - Change HUD, disable ammo and armor counter etc.
Done - Smaller ''You fragged ... for ... place" signal.
- Railcolor tag correction / misslehitwall

For the bot-code:
- Make the bots work without items in the map
- Bot aggression depending on HealthRegen
- Better bots (?)

For the gameplay code:
Done - Only RL and/or RG
Done - healthRegen
- Killable Rockets

and I added some changes:
- Added g_allowGauntlet (default 0)
- Changed g_forceSlugs/Rockets into cg_forceWeapon with "RL", "RG" or "" (default) (it isn't case sensitive)
- Added cg_ffaWeaponMode with "random" or "alternate" (default)

As I did this in q3a code it will take some time to move the changes to ioq3.

@themuffinman what's your nick on github?