CSQC Standards: Lets bridge the Great Divide

[avirox]

[Spike]

Raw polygons:
void(string shadername) BeginPolygon = #306; (FTE)
void(string texturename, float flags [, float draw2d]) BeginPolygon = #306; (DP)
DP doesn't support shaders in polygons. FTE requires them if you want to disable mipmapping or enable blending. 2d stuff is an extra extension supported only by DP that I only just discovered. Other stuff is the same.
Side note: This also applies for drawpic and the extra argument that DP mandates, although FTE does attempt to honour that flags argument.

Querying scene/view settings:
vector/float(float property) getview = #309; (FTE)
vector/float(float property) getview = #303; (DP)
(original spec had no query as an aid to cheat prevention - no aimbots if you don't know where the player is).

Stats:
Using ev_integer for floats is suboptimal in FTE, but the only way in DP.
Using strings, DP is limited to 15 chars. FTE permits much longer strings. Also, FTE string stats use a different namespace.
DP uses stats 2??-255 for various movement cvars on the server (eg: sv_maxspeed). FTE provides such cvars only through the serverkey builtin.
Meant to be otherwise compatible.

Temp ents:
Just.... just don't go there. Use stats, serverinfo, ents, or stuffcmds. Using tempents is an almost guarenteed way to break both saved games and protocol agnosticism. FTE servers will generate lots of warnings if you try, due to the whole protocol thing.

[mh]

While we're at it, could we have better failure behaviour? FTE appears to be pretty promiscuous with it's csprogs, and will accept almost anything. You could probably feed it a two-week-old bit of toast and it would find a way of working with it. DP - not so. OK, I get the reason why DP might be more strict, but last time I checked it threw a Great Big Dirty Sys_Error. How about just not using the csprogs instead? With maybe a console message for developers?

[TimeServ]

[goldenboy]

[LordHavoc]

implemented CSQC_InputEvent(2,x,y) and a cvar to enable it (which defaults to 1), this broke GAME_STEELSTORM, GAME_XONOTIC and possibly GAME_NEXUIZ, but the xonotic team have promptly fixed their code, the cvar defaults to 0 in GAME_STEELSTORM to avoid bugs for now.

Added CSQC_InputEvent(3,x,y) for moves with setcursormode(TRUE) where only absolute mouse position is known, not relative movement.

For now I recommend continuing to use getcursorpos() instead as the posted stable version of darkplaces does not have this fix obviously.

[LordHavoc]

added getproperty builtin #309 (same code as R_SetView).

Not sure why setproperty/getproperty are called that, the DP one was always called R_SetView...

[LordHavoc]

Now allowing drawpic and drawstring without flag parameter.

[Spike]

[LordHavoc]