Releases: CS-NextClient/NextClientServerApi
Releases · CS-NextClient/NextClientServerApi
v1.5.0-beta.3 Linux & Windows
NextClient 2.4.0 support
UPD:
Please be careful, there are critical issues found in this version, it is highly not recommended to use this version for production.
v1.4.0 Linux & Windows
This version introduces support for NextClient 2.3.0 with brand new features:
- Added reliable cryptographic verification of NextClient from the module which provides a high level of guarantees. Now it is safe to trust and grant privileges to players with NextClient
2.3.0and higher. - Added
ncl_is_using_nextclientnative instead ofncl_is_next_clientwhich allows you to check the verification status of the player. This is an example of how you can grant a vip flag for a player who has verified with NextClient:
#include <amxmodx>
#include <next_client_api>
new const VIP_FLAGS[] = "f"; // the vip flags we are providing
public ncl_client_api_ready(id) {
// Check that the player has verified nextclient
if(ncl_is_using_nextclient(id) == NCL_USING_VERIFICATED)
set_user_flags(id, read_flags(VIP_FLAGS));
}ncl_is_next_clientis deprecated in favor ofncl_is_using_nextclientand will be removed inv2- Added
ncl_get_nextclient_versionnative to obtain each version part in a granular manner - Added
ncl_get_supported_featuresnative to check the client for support of a particular feature abstracting from the client version - Added
ncl_set_wpn_icon_for_next_deathmsgnative to override weapon icons in killfeed lines with custom sprites (since NextClient2.3.0) - Added support for rendering of HP values more than 999 (since NextClient
2.3.0) - Added
nclapi_versionpublic cvar
Requirements for linux:
- GLIBC 2.19