... | ... | @@ -23,7 +23,7 @@ Example: `buy 0.001 @9000` |
|
|
| **FOR EXAMPLE** | **An example when we say autotrading is doing some `if, else` comparisons on infinite repeat with no waits or anything, which just runs at 1000 times a second forever. Commands with waits in them are always fine! You can do as many of them as you like. With as many repeats as you like. Next release will have a progressive rate limit on number of commands able to be run per second, so if you hit 1000 actions /second, you will be aggressively slowed right down and a warning message will automatically display advising you that you have possibly made some mistake in your command. Since that's the likely reason. The other reason is this one specific person who intentionally abuses ichibot with `if, else` comparisons on infinite repeat and basically gives us the middle finger.** |
|
|
|
| **Alias Warning** | **So aliases are structured so that something you do inside the alias does not "leak" out of the alias into the rest of the command string. So try and put all your tasks for that instrument inside the alias. For example, doing `alias btc instrument btcusdt` - `btc, buy 1` - will be fine. That's a single action. So we exempt that. However if you do say `alias btc instrument btcusdt, check value askprice` - `btc, buy 1`, then it will execute that buy 1 on the instrument you were in when you ran the command. So be weary of this. This is a bit of an outliar / rare situation. And not likely many people would attempt to do. But I ran into it by accident, so thought I'd better share.** |
|
|
|
| **----------------------------** | **-------- **initrun** ----------** |
|
|
|
| **initrun Warning** | **If you insist on putting raw commands in your initrun, intended to execute when it connects to server, be aware that it will stop loading your initrun at any `wait` orders. So you'd want to make sure that the command is at the very bottom of your initrun, otherwise the initrun will not complete.** |
|
|
|
| **initrun Warning** | **If you insist on putting raw commands in your initrun, intended to execute when it connects to server, be aware that it will stop loading your initrun at any `wait` orders. So you'd want to make sure that the command that contains the wait is at the very bottom of your initrun, otherwise the initrun will not complete. And obviously you could only have one of these types of commands. For example - if you removed `alias` from the start of a command and just had the raw command in your initrun. Which it is not designed to do, but if you insist on using it this way, then just be aware that it won't complete if it has to wait half way through your initrun.** |
|
|
|
| **----------------------------** | **-------- **Experimental Features** ----------** |
|
|
|
| **`feature cbor-0`** | **Can only run on the latest client-app version v19.12** - Sends your websocket messages to you in binary encoded CBOR instead of JSON. Mainly for testing purposes at this stage. Just stick it in your initrun under global. - If for some reason you need to open an older version, ensure you remove this before connecting. |
|
|
|
| **----------------------------** | **---------- **Discord/Telegram Webhook** -------------** |
|
... | ... | |