Split-screen play - Githubissues

leilei- commented 8 years ago

One computer, via gamepads

would need special cgame tricks as well, like configurable model and handicap. Name probably won't matter
maybe bind2 commands and joy2_ cvars to handle controls for the second player
up to 4 I am not sure.
4 keyboards and 4 mice are not plain feasible for this so don't even think about it
could lead to something special, like a libretro core to bring OA3 to the very barren PC couch shooter world

Spearmint allegedly does it (haven't tried) but that's GPLv3 which is venturing into license toxicity. I'd like to keep GPLv2+ as much as I can

LavenderMoon commented 8 years ago

Why would GPLv3 be license toxicity? Are you worried about not being able to pull in GPLv2-only code, or that GPLv2+ code would have a higher bar to use any of your code?

leilei- commented 6 years ago

I just had an brainfart for the binding part

Configs per controller device would be stored in separate cfgs (i.e. oaconfig-2.cfg) A new cvar called bindfor would specify which device to bind a key for, instead of multiple bind commands engine would set bindfor to 0 for q3config/oaconfig.cfg, then bindfor 1 to oaconfig-1.cfg, etc. at startup bindfor would be the backwards compatible way to handle cfg files and allow controller-specific preset configs to be set if desired (dunno about auto-detection for those however)

OpenArena / engine

Split-screen play #3