This repository presents the DEV TOOLKIT profile I use to build my precompiled VoiceAttack inline functions used within my AVCS profiles, which are updated and maintained by AVCS CORE, as well as an open source reference to them given that inline functions cannot be reviewed once compiled.

The AVCS CORE VoiceAttack Profile is my framework for the game profiles I create, such as my Falcon BMS Radio Commands profile and my Ready or Not Radio Commands profile. It provides common operations relatively executed in the active game profile such as handling profile initialization, save file management, updates to required configuration and resource files, and much more.

As a centralized hub profile utilizing external config files and resources not baked into the actual profile(s), CORE allows me to more easily maintain my family of AVCS profiles for either VoiceAttack V1 or V2 users. The CORE updater systems reduce the need for a new profile download/import into VoiceAttack for most updates or patches to my voice commands and systems, adding to QoL and ease of use for end users as well as the developer (me).

Say, "Open the Command Reference", to view complete list of voice commands in AVCS CORE Framework profile and available to the included Template Profile.

Say, "Open the Help Menu", to view a list of common help actions, including a direct link to Discord help and support channel for AVCS profiles.

The AVCS CORE Profile for VoiceAttack can work as a standalone profile, but is required by any AVCS4 profile I release including AVCS4 BMS Radios and AVCS4 Ready or Not profiles. AVCS CORE will operate in any version of VoiceAttack (at least v1.16 or higher), including VoiceAttack V2. Check the 'extras' folder in the extracted download package for an optional template profile you can modify for yourself to use an "AVCS CORE" powered profile all of your own. This is the profile which I modify for personal day-to-day use in Windows when not playing games. The included readme file alongside it provides details and instructions for using this optional template profile.

First, download the AVCS CORE (2.0).zip package from the link below - never download this file from anywhere else, or from others, as it should exactly match the checksum below for safety, security, and peace of mind. Extract the contents of this .zip package somewhere, and open the folder "AVCS CORE (2.0)" - inside you will find the AVCS CORE (v2.0) Profile (IMPORT THIS).vax profile package. As the name suggests, you import this into VoiceAttack.

AVCS CORE Profile Package - VoiceAttack Import Method: AVCS CORE (2.0).zip

    Extract the contents of the .zip file and import the .vax Profile Package inside

(the sample image above is from private .vax beta build and may not match the latest checksum below)

================================================
Checksum Date/Time: 9/1/2025 7:19:54 PM
Package Version: 2.0.0.0
Package Name: AVCS CORE (2.0).zip
Package Size: 1112998 (bytes) (1.06 MB)

SHA1:   8992236017ae8860737325d1209069cbb521a5f4
SHA256: 5b10d0dd547aac10245e5e64358783c31464f63cd4f734f2bda74fb8415b62d1
SHA384: c9322f40c79655ccbefda0a58d863bf18393d92808c9f22a58c0cbcb0f1505365072d27abe3f7f9dac942f5b49e2da89
SHA512: 7520de5ea74cd2271f3f0bf223551705d84e246efd65d30b7b6a5c2c4c8467f6952a0b078fb209cf109c5b2974814a2dcba4cc01c17d103fd31860a3524858bb
================================================

================================================
Checksum Date/Time: 9/1/2025 7:19:54 PM
File Version: 2.0.0.0
File Name: AVCS CORE (v2.0) Profile (IMPORT THIS).vax
File Size: 982029 (bytes) (0.94 MB)

SHA1:   4bd71e2f3db2ca760018ec1fb5516dff78d6a003
SHA256: f349d48fa2158e311e81f40608f6ff26de0f08a44d365e6dbb7d0b0373ae4f36
SHA384: 09a56b421807049380ffed6452f7ccc8763123dbaf5df89d5850843cce443b1da0cfc930807116166c486846154fdb5d
SHA512: a2fae5e0201cfa384b62a5e01ecaf7f65f0dca8216b25b342f45abf50ba4858fd8ce6d93e2e77dc90dd58e8a465741ec0cef69361aac1abd5ad783671beecfa5
================================================

This repository includes a tool that provides a simple application for testing parts of my inlines in Visual Studio, which is where I do most of my development and proof of concept testing before bringing them into VoiceAttack. The included profile AVCS CORE DEV TOOLKIT (v2.0)-Profile.vap is the same tool I use to build all precompiled inline functions, and prepare updates to AVCS CORE. This app also provides a means for end users to validate my compiled inline functions against the hashtable which is downloaded alongside them.

In time, this repository may expand to include a larger guide not only for AVCS CORE, but use of this ToolKit profile, app, and even AVCS4 game profiles which require AVCS CORE. The Wiki pages in this repo will be linked to from this readme if/when documentation is produced on a larger scale. For now, this will simply serve as an open source reference for users of my AVCS CORE powered VoiceAttack profiles.

! USER NOTICE !
-This is a major profile update, users of v1.11 should download the new v2.0 profile:
	-If you plan to use AVCS4 BMS v2.x+, AVCS CORE v2.0 is required
	-If you have VoiceAttack V2 and would like to use AVCS, you must use AVCS CORE v2.0
	-If you wanna stop running VoiceAttack as Admin just to run AVCS CORE, get v2.0
	-(AVCS CORE profile version 1.11 will NOT be retired, but may no longer be maintained)
	
	-BUT you can continue to use AVCS CORE v1.11 independently, just not in VoiceAttack V2

-Updated minimum required version of VoiceAttack to 1.16
-Added full support for both VoiceAttack V2 and VoiceAttack v1.16+ (can use either version)
-Added secure update system on top of refactored existing config files update system for all AVCS resource files
-Added open source repository on my GitHub including the dev tools app and profile I use myself to build my inline functions
-Added check for Event Log 'New entries at bottom' for single print of instructions to include CORE in AVCS4
-Added system to move all AVCS config folders to AppData\Roaming with rules to only overwrite when source is newer
-Fixed Save File System (SFS) issue with similar variable names/values being treated as the same on delete/edit
-Removed requirement to run VoiceAttack as Administrator for AVCS CORE and AVCS4 profiles using it
-Removed any Joystick button press checks in Push-To-Talk Mode "Set" for Joystick when none are enabled
-Refactored Push to Talk press monitor as persistent singleton style background script that only runs when PTT is enabled
-Refactored several heavy lifting inlines into precompiled inline functions so they can be maintained more easily
-Refactored a few small repeated inlines into precompiled inline functions so they can be maintained in a single location

//- AVCS CORE Required Resources List -//

// AVCS CORE Compiled Inline Functions
AVCS_CORE_QccPttGetButton.dll
AVCS_CORE_QccPttKeyDownCheck.dll
AVCS_CORE_QccPttVirtualKeyCodeToChar.dll
AVCS_CORE_ResourcesUpdater.dll

// AVCS4 BMS Compiled Inline Functions
AVCS4_BMS_CheckEditedAliases.dll
AVCS4_BMS_CheckExistingAliases.dll
AVCS4_BMS_CheckFalconUpdates.dll
AVCS4_BMS_DeleteAliasCommands.dll
AVCS4_BMS_DeleteAliasKeys.dll
AVCS4_BMS_GetAliasesFilePath.dll
AVCS4_BMS_GetMenuData.dll
AVCS4_BMS_LocalizeDecimalsText.dll
AVCS4_BMS_RadioCommandsGenerator.dll
AVCS4_BMS_SaveAliasCommands.dll
AVCS4_BMS_SaveAliasKeys.dll
AVCS4_BMS_SplitAliasCommand.dll
AVCS4_BMS_SplitWildcardAliases.dll

// AVCS4 BMS Global Command Aliases File
aliases.txt

// Sound Effects Files
AVCS_Feedback_CENTER.wav
AVCS_Feedback_LEFT.wav
AVCS_Feedback_RIGHT.wav

// AVCS4 BMS HTML Game Command Reference Templates
commref_bms_agency_block_template.html
commref_bms_agency_page_template.html
commref_bms_command_item_template.html
commref_bms_master_template.html

// ----README ETC.----
README.txt

Every command and function has been thoroughly tested, and most any exceptions or errors have been discovered and accounted for, with a profile command or inline function call gracefully ending and informing us of the error(s) through the VoiceAttack Event Log. If something goes wrong, the AVCS_ERROR boolean variable will become True, and an error message will be printed to the event log. When the debugging boolean variable has been set to True, depending on the debugging level set, errors may also be written to the errors log. I have included a utility voice command to end any running commands including any profile commands currently active, just say "Stop all commands".

When all else fails, just restart VoiceAttack. This will reset any Global VoiceAttack Variables used by the profile, and of course any internal variables the profile has set from those values. I have included a utility command I've used for a long time which can be helpful to check the current value of any VoiceAttack variable and print it out to the Event Log. Say, "Check a Variable Value" to open a Get Choice window which will let you select a variable type to check, and then another to enter the name of the variable. You may also say the variable type in this utility command name such as, "Check an Integer Variable Value". Truly if something goes wrong, you can always just restart VoiceAttack and the AVCS CORE profile (and any AVCS4 game profile), and things should return to normal. If not, you can delete the profile(s) from VoiceAttack, and re-import them - and if all else fails, delete the entire AVCS folder (backing it up first would be highly encouraged):

AVCS Data Path: %AppData%\VoiceAttack-AVCS Profiles

Log Path: %AppData%\VoiceAttack-AVCS Profiles\AVCS\core_errors.log

By default, error log entries are not written unless a debug mode of level 2 or 3 is enabled. Each error will be preceded by a timestamp and a debug line entry from the action list where it originated. There may be some complex information about the command which executed, any sub-command chains, and all sorts of data I would not expect anyone to understand. You can present error logs to me and I'll be happy to find where the issue has occurred. Just say, "Create a Bug Report", and follow the prompts to use the command which caused an issue, and then say, "Ready", or "Done", when it is complete (or errored out) to save the report. A browser will open where you can paste this report - feel free to review before posting, there should never be any identifying or sensitive information included.

You may also enable debugging mode, if desired, such as saying, "Enable Debug Mode Level 4", for message printing without writing to file. By enabling debugging, a larger amount of data will be printed to the VoiceAttack Event Log, which will be the same as what is printed in the errors log file. If it is not apparent what went wrong, you can always contact me and I'll do my best to help out.

I am happy to support this profile and folks using it, contact me wherever is most convenient! I have a support channel at VG Discord, and you can also message me on the Veterans-Gaming website, the VoiceAttack forums, or anywhere you see me lurking. If I'm not super busy, I'll work with you to help or point you in the right direction at the very least.