2020-03-06, 17:18
Latest version: v1.18
1. What is it?
TC Binds is a local insim application for LFS. The main purpose of it is to give you some easily-accessible binds slots. More detailed description of features you can find below. The program has been made using InSimDotNet by Alex McBride (github link).
2. Features
- Binds in form of on-screen buttons. There are five different sets of them, each set will be displayed accordingly when you are:
- civilian
- COP
- COP in chase
- MED / RES / TOW
- responding
- Binds triggered by numpad buttons.
- Customizable automatic messages sent upon specific action, such as starting a chase or arriving on scene.
- Commands:
- /o chasewarning - /o cw - Send chase warning to car behind you when you are cop in chase (you can change the message in settings file).
- /o mousemode - /o mm - Enable/disable mouse mode (buttons visible but not clickable).
- /o nextbind - /o nb - Select next on-screen bind (alternative to scrolling down).
- /o prevbind - /o pb - Select previous on-screen bind (alternative to scrolling up).
- /o sendbind - /o sb - Send selected on-screen bind (alternative to clicking scroll).
3. [TC] Supporter benefits
If you are [TC] Supporter (regular or Premium), there are a few benefits you can make use of:
- Each set of on-screen binds can contain up to 32 binds.
- Five different sets of numpad binds.
- Automatically sending chase warning if car behind gets too close (can be disabled in settings file).
- Additional command: /o custommessage [message] - /o cm [message] - Send message that includes markers, which you can use in binds of this application (i.e. "{MYCAR}").
- Additional markers, which can be used in any bind and in /o custommessage [message] command. Those markers are getting informations using [TC] API. You can receive any information that API provides within "/citydriving/profile" endpoint and with "stats" parameter. You can get that informations either about yourself, your suspect or person you are responding to. Examples of such markers available in settings file. Read more here: https://apidocs.tc-gaming.co.uk/apis/cit...rofile-api
4. Enabling Supporter mode
If you already are [TC] Supporter (regular or Premium) and would like to enable Supporter mode in [TC] Binds, there are a few steps you need to take:
- Make sure you received appropriate badge on your [TC] World profile - you can check it here. Please bear in mind that it may take up to a few days before you receive your badge after making donation. If your badge is still missing after a few days, please email us about it: [email protected]
- Log in to [TC] World and go to "My account" tab (link).
- If you don't have your own API key yet, take it by clicking on "Request API key" button.
- Copy your API key and paste it into settings file, right after "api_key=". Don't leave a space between '=' and your key!
- Save settings file. If [TC] Binds application is running already, click "Reload settings" button or restart it.
5. Download & Installation
Download: Click here
Unpack the .zip (preferably into LFS folder). Run the TC Binds.exe. When running it for the first time, you will be asked if you want to create new settings file. After you agree, edit settings.txt file to your own preferences.
6. Example settings
If you don't want to make settings file on your own, feel free to use (and edit if you wish) example settings. If you made different settings file, which you want to share with others, send it to me (preferably through forum PM) and I will add it to the list below.
Example settings (Click to View)
7. Changelog
v1.18 (19.02.2023)
- [FIX] Adapted application to TC API changes.
v1.17 (14.03.2021)
- [FIX] In test versions, sometimes debug log couldn't be created due to wrong file name.
- [CHANGE] Automatic checking for new version should be more accurate now. Additionally, now it will work in test versions as well.
- [FIX] Sometimes button names or functions couldn't be read properly from settings.
- [CHANGE] Slightly changed the way application looks for errors in settings file. Now if errors are found, reason of the error will be displayed in application log as well.
- [CHANGE] If settings file can't be read at all, the reason will be displayed in pop-up window.
v1.16 (23.02.2021)
- [FIX] Hopefully the random crash problem has been fixed.
- [CHANGE] Internal change: packets are not sent via seperate thread.
- [NEW] Test versions of application are possible and easy to make now.
- [CHANGE] Internal change: slightly changed way of registering and handling mouse hook.
v1.15 (21.01.2021)
- [FIX] Getting informations from API for binds containted an error.
v1.14 (19.01.2021)
- [CHANGE] The way application checks whether you are [TC] Supporter or not has been changed significantly. Check original post for instruction about how to enable Supporter mode now.
- [NEW] [TC] Supporters feature only! New markers available for binds - those markers take informations using [TC] API. Read more about it in settings file in comment about binds markers.
- [FIX] Application sometimes used to stay in responding mode when call was cancelled. This time it really should be fixed.
- [CHANGE] Once the Supporter mode is enabled, information about it will also be shown in log.
- [CHANGE] Some minor internal changes, which should make application more reliable.
v1.13 (11.08.2020)
- [FIX] Application used to stay in responding mode when call was cancelled.
- [FIX] Locations containing ' were not displayed correctly.
- [FIX] It was impossible to run application with changed name of executable file.
v1.12 (23.06.2020)
- [CHANGE] Multiple messages separator has been changed from "+" to "{+}", because with the old separator it was not possible to use commands containing "+" (such as "!ramp+").
- [FIX] If any errors were found in settings file, application tried to send information through LFS while InSim was not connected yet.
v1.11 (27.04.2020)
- [CHANGE] Changed frequency of sending messages by application, it used to be slightly too high and sometimes not all messages were sent due to spam protection.
- [FIX] Fixed bug causing application to crash (reported in post #25).
- [CHANGE] Messages sent by application can now have assigned reqirements (for example being in chase), if those requirements are not met, message will not be sent.
- [NEW] New customizable automatic messages sent upon certain events (such as starting chase or arriving on scene), check settings file for more details.
v1.1 (13.03.2020)
- [NEW] "Reload settings" button has been added.
- [NEW] New commands: "/o nextbind" - "/o nb", "/o prevbind" - "/o pb", "/o sendbind" - "/o sb" as an alternative to using scroll.
- [NEW] Each time you run application, it will check if new version is available. If so, you will be informed with a pop-up window.
- [NEW] If another instance of TC Binds is already running on your computer, you won't be able to run new one.
- [CHANGE] Command "/o showbuttons" - "/o sb" has been removed - buttons can be shown back using either "/o nextbind" - "/o nb" or "/o prevbind" - "/o pb" command now.
- [CHANGE] "Unable to get response from server" message will be no longer displayed in log - it was causing unnecessary confusion and was quite useless.
- [CHANGE] Readme file has been updated with necessary links.
- [FIX] Information in log that chase warning message has been sent contained nickname with LFS colour markers - now it will be nickname without those markers.
v1.0 (06.03.2020)
- First public version.
- [FIX] Adapted application to TC API changes.
v1.17 (14.03.2021)
- [FIX] In test versions, sometimes debug log couldn't be created due to wrong file name.
- [CHANGE] Automatic checking for new version should be more accurate now. Additionally, now it will work in test versions as well.
- [FIX] Sometimes button names or functions couldn't be read properly from settings.
- [CHANGE] Slightly changed the way application looks for errors in settings file. Now if errors are found, reason of the error will be displayed in application log as well.
- [CHANGE] If settings file can't be read at all, the reason will be displayed in pop-up window.
v1.16 (23.02.2021)
- [FIX] Hopefully the random crash problem has been fixed.
- [CHANGE] Internal change: packets are not sent via seperate thread.
- [NEW] Test versions of application are possible and easy to make now.
- [CHANGE] Internal change: slightly changed way of registering and handling mouse hook.
v1.15 (21.01.2021)
- [FIX] Getting informations from API for binds containted an error.
v1.14 (19.01.2021)
- [CHANGE] The way application checks whether you are [TC] Supporter or not has been changed significantly. Check original post for instruction about how to enable Supporter mode now.
- [NEW] [TC] Supporters feature only! New markers available for binds - those markers take informations using [TC] API. Read more about it in settings file in comment about binds markers.
- [FIX] Application sometimes used to stay in responding mode when call was cancelled. This time it really should be fixed.
- [CHANGE] Once the Supporter mode is enabled, information about it will also be shown in log.
- [CHANGE] Some minor internal changes, which should make application more reliable.
v1.13 (11.08.2020)
- [FIX] Application used to stay in responding mode when call was cancelled.
- [FIX] Locations containing ' were not displayed correctly.
- [FIX] It was impossible to run application with changed name of executable file.
v1.12 (23.06.2020)
- [CHANGE] Multiple messages separator has been changed from "+" to "{+}", because with the old separator it was not possible to use commands containing "+" (such as "!ramp+").
- [FIX] If any errors were found in settings file, application tried to send information through LFS while InSim was not connected yet.
v1.11 (27.04.2020)
- [CHANGE] Changed frequency of sending messages by application, it used to be slightly too high and sometimes not all messages were sent due to spam protection.
- [FIX] Fixed bug causing application to crash (reported in post #25).
- [CHANGE] Messages sent by application can now have assigned reqirements (for example being in chase), if those requirements are not met, message will not be sent.
- [NEW] New customizable automatic messages sent upon certain events (such as starting chase or arriving on scene), check settings file for more details.
v1.1 (13.03.2020)
- [NEW] "Reload settings" button has been added.
- [NEW] New commands: "/o nextbind" - "/o nb", "/o prevbind" - "/o pb", "/o sendbind" - "/o sb" as an alternative to using scroll.
- [NEW] Each time you run application, it will check if new version is available. If so, you will be informed with a pop-up window.
- [NEW] If another instance of TC Binds is already running on your computer, you won't be able to run new one.
- [CHANGE] Command "/o showbuttons" - "/o sb" has been removed - buttons can be shown back using either "/o nextbind" - "/o nb" or "/o prevbind" - "/o pb" command now.
- [CHANGE] "Unable to get response from server" message will be no longer displayed in log - it was causing unnecessary confusion and was quite useless.
- [CHANGE] Readme file has been updated with necessary links.
- [FIX] Information in log that chase warning message has been sent contained nickname with LFS colour markers - now it will be nickname without those markers.
v1.0 (06.03.2020)
- First public version.
8. Other
If you spot any bugs, please reply to this thread with as detailed description as you can (i.e. when did it happen, what could have triggered it, what exactly is happening, include screenshots/video if needed).
If you have any suggestions, don't hesitate to post it in this thread.