> For the complete documentation index, see [llms.txt](https://help.hydravision.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hydravision.ai/products/online-setfile-builder/create-and-edit.md). # Create & Edit Creating and editing setfiles just became intuitive. ### Getting Started Our intention is to assist you to create new Setfiles easily and without being confused about the 180+ different settings. To begin using the default Setfile, click on `+ New` in the Setfile Vault. Select Default Configuration, enter a file name and click `Create Setfile`.

Create a new setfile — **Create a New Setfile**

A new setfile with default settings will be created and saved to the Vault in the `General Use` Strategy folder. Selecting the setfile will load it into the Editor, ready for configuring. The Setfile input structure in OSB follows the same logical flow and naming that is in MT5. However, we have added Tabs, Categories and Logic Groups to make the structure more intuitive to the way Hydra Vision was designed. ### OSB controls There are a few controls in OSB to make management easier. These are the Icons located at the top of the editor screen:

1. - When editing a setfile, the `Save` option is available to persist the configuration. Note the saved configuration replaces what is shown for this version, and there is no revert option in OSB at present. Each save is stored as a new copy, so earlier saves of the version are kept as its history rather than overwritten. 2. - When editing a setfile, the `New Version` option is available. This will create a new version of this setfile as an increment. A newly created setfile is v1, so New Version on this setfile would be v2. A multi-version setfile is shown in Setfile Vault with an icon. A version dropdown in the editor will allow you to quickly switch between different versions of the setfile. 3. - If you have made changes to the settings, but decide not to Save, you can select to discard them. 4. **Lock Editing** - To safeguard a specific setfile, you can put a lock on it. In Lock Mode you can view and perform all functions other than edit inputs or delete. 5. **Publish Fingerprint** - To publish the configuration of a specific Setfile. Once approved for publishing, a unique URL will be generated and made available for hosting on your own platform. 6. **Setfile Notes** - Open a Notes sidebar, to read/annotate the setfile in plain language so you can easily remember how this setfile behaves at a later date. We find this to be one of the key things to do to avoid having dozens of the same setfile configurations. 7. **Duplicate Setfile** - If you would like to use the current setfile as the starting point for a new setfile, then this will create a duplicate. Useful if you want the same strategy but with some tweaks for a different asset. *This is not the same as creating a new Version of the same setfile.* 8. **Export Setfile** - All setfiles in Hydra Vision are stored in json format. For MT5 we require the .set format. Exporting from Hydra Vision will create a .set format file in your Downloads directory which can be Loaded through the MT5 interface (for live trading or back testing). 9. **Delete Version** - This will delete the current version of the Setfile. If this is the only version, then the Setfile Master record will also be deleted. If the Setfile version is associated with an MT5 Account, you cannot delete it before removing the association. A deleted version, including its saved history, is hidden straight away and kept for 30 days, during which Hydra Vision support can restore it. After 30 days it is removed permanently. 10. **Change Status** - Every setfile has a status. You can adjust this status so you can easily visualise which setfiles you are working with, for example configuring, testing, live. 11. **Strategy Folder** - Setfiles are grouped into Strategy folders. The default 'General Use' folder is where all setfiles are saved by default. You can create new folders as required to provide additional categorisation. Examples could be: Forex Strategies, Long Trail, Low Risk and so on. You can use these however you see fit. {% hint style="info" %} **Dirty Setfile** - If you have made a change to a setfile and not saved these changes, you will be unable to do anything else. We have done this as a safety precaution to prevent you leaving the screen halfway through 30 minutes of edits. All unsaved changes are noted in the Setfile Advisor in the Changes tab. {% endhint %} ### Constraints and Rules The OSB Editor has a number of built-in constraints and rules to assist with configuration. These are visible directly in the editor and through the Setfile Advisor panel on the right side of the editor. Permissible/expected values, dependencies, constraints and type are all made available. When an input value breaks a rule, the Setfile Advisor panel will draw your attention to this value. These are intended to assist you and are not provided as trading guidance. #### Relevant inputs Inputs that have no relevancy in the current configuration are disabled (or can be hidden). This helps you focus on where inputs and attention are required. If a field is enabled, then an input is required by the EA. Many of these are controlled by either a master boolean (yes/no checkbox) or enumerator (dropdown list) input. If you are trying to input into an input that is disabled, it means that the master input has not been set or the input is not required for the current Strategy. In most instances the Help context will guide you to the Master input. #### Rules Most double/int inputs have minimum and maximum expected values. Whilst you could in theory place values in these fields outside of the expected range, it is best practice to keep these range bound. If a field is enabled but has Red borders, check that the input value is within the recommended rules.

**Wrong Values & Disabled/Irrelevant inputs**

Clicking on next to the input name will display context help in the Advisor panel, along with additional metadata to assist you with configuration. {% hint style="warning" %} As the setfile does not know which asset you are trading, some of the ranges can be quite large, such as Zones or Minimum Step Size. A step size of 20 on Forex is very different from Gold. It is expected that you understand the asset you are trading, so that the inputs make sense. {% endhint %} {% hint style="success" %} Always remember to save your edits. There is no auto-save feature. You will be alerted if there are unsaved changes in your setfile before you can close or export it. {% endhint %}