diff -r 516f138027e8 -r 9a743aab6b3d doc/html/newapi_notes.html --- a/doc/html/newapi_notes.html Tue Dec 20 15:39:24 2005 +0000 +++ b/doc/html/newapi_notes.html Tue Dec 20 15:43:08 2005 +0000 @@ -16,6 +16,7 @@
  • GameShutdown
  • ShouldCollide
  • CvarValue +
  • CvarValue2 NOTE: No examples of these found in SDK... @@ -65,9 +66,31 @@

    comments:

    - This API can lead to conflicts when you query more than one cvar from a player - at a time. Use IS_QUERYING_CLIENT_CVAR to check if another plugin is querying before - you do so. + Added 2005-08-11, no SDK update. (Available in patched SDK as of hlsdk-2.3-p2.) +
    +
    + Use of this function is DEPRECATED. It has been obsoleted by the + pfnCvarValue2() function. See below. +
    + +

    CvarValue2

    +
    void (*pfnCvarValue2)( const edict_t *pEnt, int requestID, const char *cvarName, const char *value );

    +from alfred@valvesoftware.com, via HLCoders:
    +

    + When the pfnQueryClientCvarValue2() completes it will call + pfnCvarValue2() with the request ID you supplied earlier, the name + of the cvar you requested and the value of that cvar. On failure (i.e + that user is not connected or the cvar does not exist) the value of the + returned cvar will be "Bad CVAR request". If you specify an invalid + player edict you will get "Bad Player" as the value response.
    + If a client has a cvar value set to "Bad CVAR request" it cannot be + differentiated from a bad request for a cvar. This is considered + okay because that value is not considered to be useful as a valid + cvar value. +
    +

    comments:
    +

    + Added 2005-11-22, no SDK update. (Available in patched SDK as of hlsdk-2.3-p3.)