-
Hi guys!
After years of learning and testing and coping with lockdown and other IRL stuff, here i am back with a new bot script for the community.
Smokybot is a trend following bot that using MA and Oscillators. It also has budget management just like my version of Phsai’s SMM. It also has stop loss so relatively “safe” to leave it run forever…hopefully lol.
Hopefully the tool tips could explain what is what and what is for. If not, please find me in Haasonline DIscord and i would be grateful if the others could help explore and support other users.
Last but not least, thank you Phsai for teaching and guiding me in using Haasscript.Little bit details
1. You need to have these installed https://www.haasscripts.com/t/pshaicmd-sqzmom-extended/ and https://www.haasscripts.com/t/haasbot-utilities-vpm3-create_adjust_close-virtual-position-management-for-running-haasbots/
2. Compatible with Hedge and One-Way market. If you are not trading in hedge market or in one-way market, tick Not Hedge
3. Trading Balance is in profit currency. USDT/BUSD in those market and crypto in Inverse.
4. Suggested time interval is 15 minutes.
5. Always start with ALL Trade Settings options UN-TICKED to let the bot preparing values.
6. Test with default values before changing anything to understand the bot. If the default value result is not satisfying, find the best one using HaasLab. 8 weeks backtest is highly recommended.
7. Because of the dynamic part of the slot size you need to use custom wallet amount in HaasLab.
8. PAY ATTENTION to the log warning if you feel something is off before screaming the bot is not working.May the Profits be with you!
*Backtest was Bybit USDT Futures BIT/USDT 4 Weeks on Feb 2 22
Version:
2022.1.25
-
-
-
-
-
Have been following this script for a while… settings need creative inputs when using on inverse accs (profit in Crypto) to get ANY backtest results… here’s what I mean. Regular leverage accs profit in USDT so the custom wallet and trading balance settings are calculated in USDT and display correctly in USDT even though it uses BTC as the quantity for contract sizes, AWESOME works correctly …whereas inverse lev accs profit in crypto so the custom wallet and trading balance are calculated as crypto and inverse trading amount as USD per contract and don’t display correctly in BTC because it uses usd as the quantity for contracts (the inverse trading amount setting) and reads the custom and trading balances as BTC amounts … It will correctly calculate BTC profit but the wallet totals will be wrong extremely wrong. If you enter actual BTC amounts instead of USD/T in the custom or trading balance settings the bot won’t be able to execute orders because it states the contract size is to small (below exchange min)… and if you add USD amounts in those settings it thinks you have that many BTC in BTC. Normal lev acc $1000 in custom and trading balance settings and it works on $1000… Inverse lev acc 1000 in both custom and trading balance settings and it works on you have 1000 BTC… ok so how about I say 0.2 for custom and trading bal settings on a inverse x10 leverage acc and it won’t make a trade nor backtest results because it’s below min contract size (for an inverse acc). It’s probably unavoidable in the code and the calculations of profit for inverse accs will be sound as long as you ignore the wallet balance figure and just look at the additional coin it added to amount you put in…the min amount for inverse accs is $10 USD (which the bot will show as 10BTC in your results). Only putting in a inverse amount in settings also yields no results. Just be sure to check your settings and play around with them until you receive realistic profit amounts… $1000 will NOT YEILD YOU 100+ BTC over a week lol.. the bot isn’t magic. returns will be in decimal amounts.
-
-
Sorry for the late reply.
so yeah, that is a coding mistake in the taking profit part. the solution would be:
1. manually close the position in the exchange then either use VPM to close the position in the bot or stop and clean the bot
2. use the later version which does not have this problem.
-
-
-
-
