How it works

The intended purpose of this plugin is primarily for plugin devs to see, what signatures have already been found, and for server owners to be able to update gamedata files for maybe old or unmaintained plugins. It is less so to have a magic or automatic way to get signatures to be always up-to-date. As to how it is used is up to the user base. If you have suggestions or feeback, please create an Issue on GitHub, linked in the page footer.

The data on this website is user provided. In order to upload data or post comments you have to sign in through steam. You can then drag-drop gamedata files on the browser to add them to the database. Signed in users can also post comments, please be civil as I don't want to have to moderate this and will rather turn off that feature. Move off-topic discussions to DMs.

All data and comments you post on the database are transparent and visible through your user control panel. If you wish to remove your data from the database, go to your user control panel and delete it from there. Deleting your data can not be undone.

GameData is not linked to your account by a direct ownership relation but instead there is a list of references from values to users. If someone uploads the same signature or value this wont create a whole new entry, but create a new reference from the data to the other user. Users can also create and break these references directly using the "(De-)Duplicate" button on Signatures and Values.

If an entry on the database has no remaining duplicates (all users deleted their reference for an entry), the entry will be removed from the database as well.

Duplicates VS Score: Duplicates are supposed to be indicators, that other people found the same value to be working for them. The score or rating is intended as a measure of quality and redundancy. For example if a value is unnecessarily long, users can down vote it and suggest/upload a better value.

Search

Filter terms by default search namespace and symbol name. If you want to only search a namespace name, suffix a scope operator (::). If you want to search a label in all namespaces, use the any namespace prefix (*::). Some symbols do not belong to any namespace or the global namespace. These can be search with a plain scope operator (::) prefix.

There are also meta filters in the form key=value to give a more precise result:

Key and value are separated by one comparator (<, > or =) followed by an integer value. If no comparator was specified the exact version will be searched. Additionally you can specify the keyword asc or desc to include this key when sorting results. Both parts are optional but you have to specify at least one. If you use both, use a comma to separate both values. If you dont specify a value, the comparator doesn't matter, but the order has to be last.

For daterange, the value has to be formatted as ISO-date (yyyy-MM-dd). Other formats are not supported.

The key=value option can not contain any spaces. If they are malformed, they will be interpreted as symbol name.

Examples for search queries:

• CTFPlayer:: user=76561198023105849 score=desc
• score>100
• *::Regen version>7695203 - This searches symbols for game version 7695204 and newer
• date>2022-12-01,asc - Show everything after the december update in ascending order

API

The API is currently experimental and intended purely for fetching signatures. Simply set the Accept header to one of application/xml, application/json or application/vdf to get the response data in the specified format.

Please keep in mind that this API, as most APIs, requires you to send a User-Agent. You should never copy the User-Agent string of a web browser for the purpse of querying APIs. A User-Agent is really just an arbitrary string, identifying your application name and version. You can read more on the MDN here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent.

The following rate limits are currently in place:

To generate an API token, go to your user page after logging in. You can use the token from there for the Basic Authorization header like this:
Authorization: Basic YOUR_TOKEN_HERE

Note on application/vdf queries: You will not magically get a GameData-file out of this (yet). Escape sequences are enabled with vdf rendering; this means that backslashes, quotes and linebreaks are escaped to make the output a bit more robust. Arrays are rendered using duplicate keys, as with vmf files.

For the endpoints, just watch the network monitor in your browser. Most are not filtered and will just output with your specified renderer.