|
Challenge:
News
Forums
Coverage
Features
Interviews
Maps
People
Smackdown
Columns:
dethkultur 09 Aug
Wiebo de Wit 08 Aug
Mr.CleaN 08 Aug
Hoony 06 Aug
Khaile 05 Aug
RooS 31 Jul
PhaNToM 10 Jul
jude 19 Jun
Jjonez 19 May
Hosted
3.A.C
Interface
QWF
QW Projects:
Introduction
Summary Table
The Projects
QW Opinions
Pro Mode:
Introduction
Download
Changes
Servers
Maps
Demos
Project Team
README
Pundits
Pro Mode Forum
Old MB
Affiliates:
Cached
Gamershome
Methos
The CPL
|
QW Projects
Personal Wishlist
Here I just want to list the things I would like to see happen to the QW source. Maybe I'll turn this into a formal 'ToDo' list in the future...The sources of these ideas are diverse:
- some were derived from the functionality of existing proxies
- some originated in my own inspiration
- some are suggestions picked up from messageboards
- and last (and possibly least in this case) come from q3
I've put my rating for desirability (sometimes urgency) and difficulty of the feature in too. The importance and expected implementation problems go up with the number of *. [***/**] is a feature that would be very welcome and moderately difficult to implement. Again, this is my current list and I expect it to change soon.
Compatibility and Optimisation
- maintain compatibility with existing data formats of the Q(W) engine: BSP's, MDL's etc. [***/*]
- preferably maintain compatibility with existing QuakeC code such that MOD's don't need extra work to still run (the original programming/design team has disolved or stopped working on the project in most of the cases) [***/*]
- new functions can be added to the QuakeC library to allow new MOD-releases to take advantage of the new possibilities offered by the engine [**/**]
- compatibility of the networking code/demo format should probably be broken to reduce the impact of currently existing cheats [*/*]
- optimise network-traffic [**/***]
- new maps should be added to the download; some great custom maps have been produced but were never played very much [***/*]
Cheat prevention
- network code cheat protection: proxies shouldn't be needed for their teamplay features anymore; the network traffic shouldn't be allowed to be altered between te client and the server (I don't see a problem with forwarding proxies though) [***/***]
- client cheat protection through some sort of checksumming [***/***]
- pure-server option to check for altered pak-files [**/**]
- possibility to send screenshots to the server or match admins [*/***]
-
removal of fullbright colors from software renderer and server-settable value of r_wateralpha (remove transparant teleporters) [**/**]
Teamplay
- teammate report of status and position, possibly seperated from regular chat [***/*]
- in-game voice communication [*/***]
- spectator mode with delayed connection to discourage spectator cheating (delay should be made server-side changeable; for FFA games or pickup teammatches it's not much of a problem and more fun to see the comments) [*/***]
- in game map of the level with position of teammates indicated, maybe including color shading (green/red) of areas reported to be safe/unsafe [*/***]
-
identifieable teamskins, e.g. adding the name of the player (or even just a number) [*/*]
I am sure more great ideas will pop up over time.
|
