Search the Community

Advanced Developer Tools by Leopard20 Short description: An addon that adds completely new and revamped developer tools to the game, including a Debug Console with syntax highlighting, Config Viewer with many new features, etc. Long description: If you're a mod/mission maker, then you definitely must've used the Debug Console, the Config Viewer, as well as other in-game tools that can help you test and verify your codes and configs. But when you use those tools, the first thing that strikes you is their clunkiness and a rather user-unfriendly design. For instance, lack of syntax highlighting in Debug Console means that you'll have to actually read every single word of your code in order to make sure you haven't made a typo, etc. That's why most of us use third party code editors such as Visual Studio Code and Notepad++. But this means that you'll have to switch out of the game every time you want to write and test some code. Or let's take a look at the Config Viewer: every time you want to go one level deeper into the config, the whole config viewer must be reloaded! And if you have hundreds of mods loaded, this means you have to spend more time waiting for the Config Viewer to load than actually viewing the config! This is exactly why I made this mod: to make the Arma environment more user friendly to the mod/mission makers. So without further ado, let's take a look at the features! Screenshots: Review Video (Thanks to Instant Arma): Documentation: The documentation is available in the mod folder. You can find the online version here. ⚠ If your input method is set to anything other than English in Windows, some input related features (shortcuts, auto-completion of brackets, etc.) might be broken. I'll try to address this issue in future updates. Download: Steam Workshop Note: This is a preview release. Please provide feedback regarding the mod features, such as design, what you'd like to see, etc. Thank you! Localization: Interested in translating the mod to your language? Or maybe the translation is not good and you'd like to improve it? Please visit the localization repository on GitHub. Known issues: FAQ: Requirements: None (Arma 3 v2.06+)

Visual Studio Code SQF Language v1.0.6 Lastest update: 22.10.2018 Microsoft Visual Studio Code is a new, but already very known Code Editor. Works on Linux, OS X and Windows. Now in the Visual Studio Marketplace -> Report bugs, ask questions or make suggestions <- Supported Products: Operation Flashpoint [OFP], Operation Flashpoint: Resistance ArmA, ArmA 2, ArmA 3 (DLCs & Extensions included) Take On Helicopters [ToH] Community Based Addons [CBA], ACE Easy Installation (Recommended) Download Visual Studio Code. Open the Editor and click on the extension icon to your left ( ) Enter "SQF" and hit enter Select "SQF Language" and click on "Install" Enjoy Manual Installation Only use this guide if the installation over the extension manager and/or marketplace isn't working! Download VS Code Download the latest release from GitHub ( https://github.com/Armitxes/VSCode_SQF/releases ) Install Visual Studio Code Navigate to your VS Code extension Folder. Windows: %USERPROFILE%\.vscode\extensions Mac/Linux: $HOME/.vscode/extensions In the plugins folder, you create a folder called Armitxes.SQF, if you have it already delete all files inside! Inside the Armitxes.SQF folder you then unzip the sources you obtained from GitHub That's it, now simply (re-)start Visual Studio Code (or just "Code") and it's done :) With VS Code, every folder is a project! To open your SQF Project simply go on File->Open Folder and choose your mission/mod folder. Feel free to ask any questions, aswell the Code of the GitHub Project was now simplified several times by me and is open for everyone for contribution! Cheers, Armitxes

Lint Summary SQFLint is command line tool, that checks specified files for syntax errors. It can output those errors in human readable format, or JSON for some futher processing. Homepage: http://sqflint.zipek.cz/ Releases: https://github.com/SkaceKamen/sqflint/releases Github: https://github.com/SkaceKamen/sqflint (extension moved to separate thread) Changelog You can find changelog at releases page Features Syntax error checking Undefined variable warnings Exports some info about file for futher processing by external tools

Arma Dev for Visual Studio Code Version 0.0.12 - DOWNLOAD | CHANGELOG Building Arma 3 mod made easier using the Arma Dev tooling extension This Visual Studio Code extensions will optimize your workflow on building and signing pbo's, preview dialog controls and automate execution and installation. Features Build your extension or add existing into the Arma-Dev configuration Pack server and client pbo files (incl. signing) with a single command Preview Dialog control files (*.hpp) Generate private keys Install the client mod into the correct game directory Run and debug (using *.RPT file) on the fly Usage Before using the Arma Dev extension, please make sure you have properly installed the Arma 3 Tools from Steam. Open your existing Arma (server / client) and run the Arma 3: Configure command to setup the project. Please refer to the Configuration section for further details Below you can find all available commands Arma 3: Configure: to setup the project Arma 3: Pack: to pack pbos defined in your configuration file Arma 3: Binarize: binarize cpp files from explorer context menu Arma 3: UnBinarize: Unbinarize bin files from explorer context menu Arma 3: Run Server: start the arma3server with server mod path included Arma 3: Run Client: to start the game from your local computer Arma 3: Run Client (With Logging): to start the game and display the logfile Arma 3: Generate Key: generate a private key to sign the client pbo's Arma 3: Transfer Files: transfer server pbos to destination server using SFTP Arma 3: Toggle Code Live: please read the below "Toggle Code Live" section for further details Configuration The configuration file is located in .vscode/arma-dev.json and contains the following options. title: The title of your project (no used yet) name: The short name of the addon (this name is used as output folder) author: author name buildPath: destination folder of all pbo files being generated privateKey: the private key path being used to sign the client addon serverDir: all server directories a pbo files should be created for (E.g. core and core_config) serverUse32bit: use legacy 32bit version of arma3server.exe serverMods: additional server mods being loaded when running arma3server clientDirs: all client directories a pbo files should be created for (ussualy its one or none) clientMods: additional client mods being loaded when running arma 3 version: a version number to track possible changes (not immplemented) ftpConnection: setup SFTP connection using host, username and password (optionally path) ftpConnectionFile: setup SFTP connection by using a separate file postProcess: run some additional scripts once a command has been successfully executed - see "Post Processing" Toggle Code Live PLEASE READ THIS CAREFULLY With "Code live" you can edit *.sqf files while Arma is running. It uses symlinks (refering to its workspace source) and the -filePatching startup parameter. A proper configured $PBOPREFIX$ for every addon file is required So, how to use it Run the command Arma 3: Toggle Code Live to create all necessary symlinks into "Arma 3\x" directory use Arma 3: Run Client to start Arma with all necessary parameters (-filePatching) use Arma 3: Run Server to prepare a server configuration and run it Customize the files defined in your workspace source folder. Open the in-game debug console and either use execVM or preprocessFile* to "reload" the changes. If you use a preInit script (which DOES NOT use compileFinal) you can use execVM too Please be aware of the following Server config.cfg requires allowedFilePatching = 2; (which is ussually the case when running with Arma 3: Run Server) No server side signatur verification will work, so verifySignatures = 0; to bypass it You can toggle Code Live to either use the source or PBO file (located in buildPath) Some commands / settings (like compileFinal / config.cpp) cannot be overwritten (anti cheat) HINT: Use [] spawn { compile preProcessFile "x\youraddon\yourfile.sqf" }; instead of execVM "x\youraddon\yourfile.sqf" from console to update file modifications Post Processing The post processing option (defined in .vscode/arma-dev.json) can be helpful to run additional tasks once a command has been successfully executed. An example of running a script when for instance all files are transfered to the remote can look the following: "postProcess": { "transferFiles": "./restart-server.ps1" } Please note these commands are always executed locally Requirements Arma 3 Tools (http://store.steampowered.com/app/233800/Arma_3_Tools/) Visual Studio Code PLEASE MAKE SURE STEAM IS RUNNING AS IT IS REQUIRED FOR PACKING Extension Settings arma-dev.logLevel: setup the log level (Info | Debug | Error) arma-dev.dialogAxisMode: How to display the dialog control axis (0 = truncated, 1 = original) restart required