Haasonline Simple Trade Bot For BTCe and Bitstamp[Main topic]

[g0re79]

@g0re79:
If you give the software a minute or so to collect the Fee and Wallet from the API then the first issue can not be happening. Updating this information is NOT instant to prevent flooding of a API/exchange, it asks a minute or so to fetch up. Only when really needed the software forces a update on those values for example just before trading. (this is made this way to prevent flooding of a exchange, you could get blocked if this happens from the software side)

It works well from beginning, eg. if I set trade amount to 90% and have 0,135 BTC on BTCe account, it will correctly count trade amount as 0,121 BTC. But after running backtest, I end up with trade amount of 8999999,1 BTC (and all test trades in tradfe log are made with this huge amount). I suspect this to be somehow caused by decimal place issue (. and ,) because numbers are shown with commas in Windows interface - If You set number as 1,5 then comma is ignored and number is changed to 15. So If You trade 0,121 then You will end with 121 instead. There is nothing I can do about that, as its fully automated process for example:

I have 1 BTC, set trade amount to 95% and result is 0,95 BTC which turns to 95 BTC..

Is this issue based on region? I mean if in US numbers are shown with dot and in EU with commas? And please note that this is related to windows interface - I dont know if its the same with web interface, because I dont have a time to play boring "click´n´wait" game.

Please know: there is no danger because of these reported issues.

With previous issue, while everything with decimal places separated with comma is turned to non-decimal numbers its quite dangerous (even percents are affected, so 0,5% changes to 5%)..

I am planning to fire up virtual machine with clean US version of W7 instalation to find out if this issue persist in different environment (and to test whether web interface is faster on clean PC). But I don´t know when, as I have little time

[Stephan224]

Try to use dots as decimals characters. Most of the users are from the USA and so the dot is the base decimal character inside the software.

The high trade-amounts displayed at the backtest/benchmark where caused by another fall-back. I have changed it to the absolute values to "solve" this. But still i do not expect this will work out as everybody might expect. At All-in and Percentages the wallet amount does not get changed and so the trade-amount does not follow the changes caused by simulated trades.

@Demonxaian:
The activation of the trade-bots will be an option under the Server settings. If you want you can enable it here. Last buy ans sell price are saved and restored too now. (i undo these changes)

@kalross:
The roof-in problem requires more time from my side to backtrack the cause of that. I will continue the update first and then i get back on it. I am sorry i have to move this one for this moment.

[maccie]

Is there anywhere somekind of guide to set up some basic strategies for simple trading bot?

[Stephan224]

Version 0.9.9.1 has just been released to solve all the recent reported problems.

This are the points that are changed within this version.
- New: Option added to the server settings to activate the trade-bots on start
- Improvement: More information added on insurance messages
- Bugfix: Missing signals page for the safeties added (applies only to web-interface)
- Bugfix: Speed problem is solved
- Bugfix: Backtest/benchmark issues with the all-in and percentages solved (for as far as possible)
- Bugfix: Usage of the comma decimal in the Classic Windows Interface is fixed (use dots!)
- Bugfix: Small improvement to the feeovercome insurance (it did fall back to 10% for some reason)

To install the update just restart the software and you will get the update form. It is not expected you may lose your trade-bots or settings on this update.

[g0re79]

Try to use dots as decimals characters. Most of the users are from the USA and so the dot is the base decimal character inside the software.

You don´t understand me - I am already using dots as decimal places, but haasbot automatically changing dots to commas on various places. Its mainly to show how parameters are set, but also to count with them. Take a look at this screenshot as for an example - there is price change insurance set by 0(dot)5% but shown like 0(comma)5%. If I doubble click this insurance, next window with 0(comma)5% will appear:



Does not matter that price drop is not shown at all (another issue), when I now click "close", on next interface refresh 0.5% changes to 5%



This is rooted throughout whole haasbot, so it basically mean it's useless for EU non-dots countries

EDIT: New update released during my post, I´ll edit my post after some testing

[g0re79]

Version 0.9.9.1 has just been released to solve all the recent reported problems.

This are the points that are changed within this version.
- New: Option added to the server settings to activate the trade-bots on start
- Improvement: More information added on insurance messages
- Bugfix: Missing signals page for the safeties added (applies only to web-interface)
- Bugfix: Speed problem is solved *** Web intrerface is like 30% faster tham before, but I still prefer Windows interface (all in one screen), which now run like flash
                                                  *** Bear in mind that in Windows interface You have to wait to GUI update before expecting / performing any mayor changes / results
- Bugfix: Backtest/benchmark issues with the all-in and percentages solved (for as far as possible) *** Confirmed
- Bugfix: Usage of the comma decimal in the Classic Windows Interface is fixed (use dots!) *** Confirmed - awesome so far !!!
- Bugfix: Small improvement to the feeovercome insurance (it did fall back to 10% for some reason) *** Confirmed

To install the update just restart the software and you will get the update form. It is not expected you may lose your trade-bots or settings on this update. *** Lost APIs on this update, BOTs survived

Its finally getting better after few weeks 

[jamieb81]

Is there anywhere somekind of guide to set up some basic strategies for simple trading bot?

I would like that as well, but for the Beginner licence 

[throwaway222]

I don't know what exactly you changed in the formula to calculate the EMA but PLEASE revert it. It has added huge amounts of noise to my 1 hour MACD histogram. You can double check this easily, even with the default settings you will see a lot of noise.

I missed out on $300+ overnight after I switched the bot off after updating it and noticing the difference (I am trading litecoin). I can't retune it, the noise is from the alternate method you have implemented.

Please either roll it back or quickly push an update with both methods!

Thanks

[silverston]

after updating the bot can not sell at all.

Code:

19.03.2014 6:38:02 Order failed or timed out: Sell 0,1 Ltc @ 19,18131067 Usd/Ltc. Reverting to previous position.
19.03.2014 6:36:46 There are open orders.
19.03.2014 6:34:37 There are open orders.
19.03.2014 6:33:26 There are open orders.
19.03.2014 6:32:12 There are open orders.
19.03.2014 6:31:01 There are open orders.
19.03.2014 6:29:49 There are open orders.
19.03.2014 6:28:38 There are open orders.
19.03.2014 6:27:28 There are open orders.
19.03.2014 6:25:40 There are open orders.
19.03.2014 6:24:30 There are open orders.
19.03.2014 6:23:17 There are open orders.
19.03.2014 6:22:06 There are open orders.
19.03.2014 6:20:54 There are open orders.
19.03.2014 6:19:43 There are open orders.
19.03.2014 6:18:33 There are open orders.
19.03.2014 6:17:23 There are open orders.
19.03.2014 6:16:14 There are open orders.
19.03.2014 6:15:01 There are open orders.
19.03.2014 6:13:47 There are open orders.
19.03.2014 6:12:01 There are open orders.
19.03.2014 6:10:51 There are open orders.
19.03.2014 6:09:39 There are open orders.
19.03.2014 6:08:29 There are open orders.
19.03.2014 6:07:19 There are open orders.
19.03.2014 6:06:09 There are open orders.
19.03.2014 6:04:59 There are open orders.
19.03.2014 6:03:49 There are open orders.
19.03.2014 6:02:38 There are open orders.
19.03.2014 6:01:27 There are open orders.
19.03.2014 6:00:17 There are open orders.
19.03.2014 5:59:07 There are open orders.
19.03.2014 5:57:53 There are open orders.
19.03.2014 5:56:42 There are open orders.
19.03.2014 5:55:06 There are open orders.
19.03.2014 5:53:54 There are open orders.
19.03.2014 5:52:42 There are open orders.
19.03.2014 5:51:31 There are open orders.
19.03.2014 5:50:20 There are open orders.
19.03.2014 5:49:08 There are open orders.
19.03.2014 5:47:56 There are open orders.
19.03.2014 5:46:45 There are open orders.
19.03.2014 5:45:29 There are open orders.
19.03.2014 5:44:17 There are open orders.
19.03.2014 5:43:03 There are open orders.
19.03.2014 5:41:52 There are open orders.
19.03.2014 5:40:41 There are open orders.
19.03.2014 5:39:30 There are open orders.
19.03.2014 5:38:16 There are open orders.
19.03.2014 5:37:02 There are open orders.
19.03.2014 5:35:52 There are open orders.
19.03.2014 5:34:41 There are open orders.
19.03.2014 5:33:28 There are open orders.
19.03.2014 5:32:15 There are open orders.
19.03.2014 5:31:05 There are open orders.
19.03.2014 5:29:54 There are open orders.
19.03.2014 5:28:44 There are open orders.
19.03.2014 5:27:34 There are open orders.
19.03.2014 5:26:23 There are open orders.
19.03.2014 5:25:10 There are open orders.
19.03.2014 5:24:00 There are open orders.
19.03.2014 5:22:50 There are open orders.
19.03.2014 5:21:40 There are open orders.
19.03.2014 5:20:28 There are open orders.
19.03.2014 5:19:18 There are open orders.
19.03.2014 5:18:07 There are open orders.
19.03.2014 5:16:56 There are open orders.
19.03.2014 5:15:41 There are open orders.
19.03.2014 5:14:30 There are open orders.
19.03.2014 5:13:20 There are open orders.
19.03.2014 5:12:06 There are open orders.
19.03.2014 5:10:53 There are open orders.
19.03.2014 5:09:39 There are open orders.
19.03.2014 5:08:29 There are open orders.
19.03.2014 5:07:18 There are open orders.
19.03.2014 5:05:30 There are open orders.
19.03.2014 5:04:18 There are open orders.
19.03.2014 5:03:08 There are open orders.
19.03.2014 5:01:56 There are open orders.
19.03.2014 5:00:46 There are open orders.
19.03.2014 4:59:35 There are open orders.
19.03.2014 4:58:22 There are open orders.
19.03.2014 4:57:07 There are open orders.
19.03.2014 4:55:56 There are open orders.
19.03.2014 4:54:46 There are open orders.
19.03.2014 4:53:30 There are open orders.
19.03.2014 4:52:20 There are open orders.
19.03.2014 4:51:06 There are open orders.
19.03.2014 4:49:55 There are open orders.
19.03.2014 4:48:45 There are open orders.
19.03.2014 4:47:34 There are open orders.
19.03.2014 4:46:20 There are open orders.
19.03.2014 4:45:07 There are open orders.
19.03.2014 4:43:52 There are open orders.
19.03.2014 4:42:42 There are open orders.
19.03.2014 4:41:32 There are open orders.
19.03.2014 4:40:21 There are open orders.
19.03.2014 4:39:12 There are open orders.
19.03.2014 4:38:01 There are open orders.
19.03.2014 4:36:51 There are open orders.
19.03.2014 4:35:41 There are open orders.
19.03.2014 4:34:30 There are open orders.
19.03.2014 4:33:19 There are open orders.
19.03.2014 4:32:08 There are open orders.
19.03.2014 4:30:55 There are open orders.
19.03.2014 4:29:40 There are open orders.
19.03.2014 4:28:20 There are open orders.
19.03.2014 4:27:08 There are open orders.
19.03.2014 4:25:54 There are open orders.
19.03.2014 4:24:40 There are open orders.
19.03.2014 4:23:28 There are open orders.
19.03.2014 4:22:14 There are open orders.
19.03.2014 4:21:03 There are open orders.
19.03.2014 4:19:52 There are open orders.
19.03.2014 4:18:40 There are open orders.
19.03.2014 4:17:27 There are open orders.
19.03.2014 4:16:15 There are open orders.
19.03.2014 4:15:00 There are open orders.
19.03.2014 4:13:45 There are open orders.
19.03.2014 4:12:34 There are open orders.
19.03.2014 4:11:22 There are open orders.
19.03.2014 4:10:06 There are open orders.
19.03.2014 4:08:55 There are open orders.
19.03.2014 4:07:45 There are open orders.
19.03.2014 4:06:04 There are open orders.
19.03.2014 4:04:53 There are open orders.
19.03.2014 4:03:41 There are open orders.
19.03.2014 4:02:02 There are open orders.
19.03.2014 4:00:46 There are open orders.
19.03.2014 3:59:35 There are open orders.
19.03.2014 3:58:23 There are open orders.
19.03.2014 3:57:13 There are open orders.
19.03.2014 3:56:01 There are open orders.
19.03.2014 3:54:50 There are open orders.
19.03.2014 3:53:39 There are open orders.
19.03.2014 3:52:27 There are open orders.
19.03.2014 3:51:15 There are open orders.
19.03.2014 3:50:00 There are open orders.
19.03.2014 3:48:49 There are open orders.
19.03.2014 3:47:38 There are open orders.
19.03.2014 3:46:26 There are open orders.
19.03.2014 3:45:14 There are open orders.
19.03.2014 3:44:02 There are open orders.
19.03.2014 3:42:51 There are open orders.
19.03.2014 3:41:39 There are open orders.
19.03.2014 3:40:26 There are open orders.
19.03.2014 3:39:17 There are open orders.
19.03.2014 3:37:57 There are open orders.
19.03.2014 3:36:46 There are open orders.
19.03.2014 3:35:37 There are open orders.
19.03.2014 3:34:18 There are open orders.
19.03.2014 3:33:07 There are open orders.
19.03.2014 3:31:16 There are open orders.
19.03.2014 3:30:04 There are open orders.
19.03.2014 3:28:53 There are open orders.
19.03.2014 3:27:42 There are open orders.
19.03.2014 3:26:31 There are open orders.
19.03.2014 3:25:16 There are open orders.
19.03.2014 3:24:06 There are open orders.
19.03.2014 3:22:54 There are open orders.
19.03.2014 3:21:35 There are open orders.
19.03.2014 3:20:21 There are open orders.
19.03.2014 3:19:10 There are open orders.
19.03.2014 3:18:00 There are open orders.
19.03.2014 3:16:49 There are open orders.
19.03.2014 3:15:38 There are open orders.
19.03.2014 3:14:27 There are open orders.
19.03.2014 3:13:15 There are open orders.
19.03.2014 3:12:00 There are open orders.
19.03.2014 3:10:42 There are open orders.
19.03.2014 3:09:31 There are open orders.
19.03.2014 3:07:51 There are open orders.
19.03.2014 3:06:39 There are open orders.
19.03.2014 3:05:27 There are open orders.
19.03.2014 3:04:16 There are open orders.
19.03.2014 3:03:05 There are open orders.
19.03.2014 3:01:50 There are open orders.
19.03.2014 3:00:37 There are open orders.
19.03.2014 2:59:21 There are open orders.
19.03.2014 2:58:10 There are open orders.
19.03.2014 2:56:59 There are open orders.
19.03.2014 2:55:49 There are open orders.
19.03.2014 2:54:36 There are open orders.
19.03.2014 2:53:25 There are open orders.
19.03.2014 2:52:13 There are open orders.
19.03.2014 2:50:56 There are open orders.
19.03.2014 2:49:45 There are open orders.
19.03.2014 2:48:34 There are open orders.
19.03.2014 2:47:24 There are open orders.
19.03.2014 2:46:11 There are open orders.
19.03.2014 2:45:00 There are open orders.
19.03.2014 2:43:49 There are open orders.
19.03.2014 2:42:35 There are open orders.
19.03.2014 2:42:35 Order failed or timed out: Sell 0,1 Ltc @ 19,18131067 Usd/Ltc. Reverting to previous position.

but no one open order now
so all three bots
edit.
after server restart the settings are not saved

[kalross]

after updating the bot can not sell at all.

Code:

19.03.2014 6:38:02 Order failed or timed out: Sell 0,1 Ltc @ 19,18131067 Usd/Ltc. Reverting to previous position.
19.03.2014 6:36:46 There are open orders.
19.03.2014 6:34:37 There are open orders.
.......
19.03.2014 2:42:35 Order failed or timed out: Sell 0,1 Ltc @ 19,18131067 Usd/Ltc. Reverting to previous position.

but no one open order now
so all three bots
edit.
after server restart the settings are not saved

I've had a couple of disconnects from BTC-E resulting in failed trades and have to re-enter key to connect.

K

Update:  Getting lots of this???

19/03/2014 23:47:26 Order failed or timed out: Sell 89.41866610 Ltc @ 17.17416667 Usd/Ltc. Reverting to previous position.
19/03/2014 23:47:26 Insurances agree on trade command
19/03/2014 23:47:26 Sell signal produced by the indicator(s).
19/03/2014 23:39:20 Order failed or timed out: Sell 89.41866610 Ltc @ 17.29500367 Usd/Ltc. Reverting to previous position.
19/03/2014 23:38:11 Order failed or timed out: Sell 89.41866610 Ltc @ 17.29500367 Usd/Ltc. Reverting to previous position.
19/03/2014 23:38:10 Sell signal produced by a safety.
19/03/2014 23:38:10 Dynamic drop-loss: SELL
19/03/2014 23:38:10 Order failed or timed out: Sell 89.41866610 Ltc @ 17.3081755 Usd/Ltc. Reverting to previous position.
19/03/2014 23:37:01 Order failed or timed out: Sell 89.41866610 Ltc @ 17.3081755 Usd/Ltc. Reverting to previous position.
19/03/2014 23:37:01 Sell signal produced by a safety.

[silverston]

after updating the bot can not sell at all.

Code:

19.03.2014 6:38:02 Order failed or timed out: Sell 0,1 Ltc @ 19,18131067 Usd/Ltc. Reverting to previous position.
19.03.2014 6:36:46 There are open orders.
19.03.2014 6:34:37 There are open orders.
.......
19.03.2014 2:42:35 Order failed or timed out: Sell 0,1 Ltc @ 19,18131067 Usd/Ltc. Reverting to previous position.

but no one open order now
so all three bots
edit.
after server restart the settings are not saved

I've had a couple of disconnects from BTC-E resulting in failed trades and have to re-enter key to connect.

K

I have permanent api problem today with BTC-e/
5 min work and disconnect.
contacting with btc-e support - they say api working without problem.
I cant trade anymore now.

[_thekev]

I'm trying to trade alts at cryptsy, but the bot price only seems to update every half-hour (multiple coins). What is going on?  It is placing orders based on old data, and ends up reverting its position when they don't clear.

[SmokedMolex]

Things this software should have:

Well it's a gimme since it needs a lot.

But according to Haas everything works because he confirmed it with "beta testers"

Let me know when I can upgrade.  I get tired of trying to input all these API keys and bot settings only to find out this software is more fucked up than ever.

The standard method here seems to be "If it's working, fix it" 

Anyone else notice all the new people coming out of the woodwork saying this is broken?

This software is the biggest joke ever and it's not even funny.

[silverston]

Things this software should have:

Well it's a gimme since it needs a lot.

But according to Haas everything works because he confirmed it with "beta testers"

Let me know when I can upgrade.  I get tired of trying to input all these API keys and bot settings only to find out this software is more fucked up than ever.

The standard method here seems to be "If it's working, fix it" 

Anyone else notice all the new people coming out of the woodwork saying this is broken?

This software is the biggest joke ever and it's not even funny.

I disabled the bot because he always loses api connection.
waiting for Stephan comment

[Stephan224]

I am working on the reported BTC-e issue. I started on this yesterday sinds it was reported here but i was not able to reproduce the situation yet. All test-runs and my real-time trading setup are reporting good trading. (i will continue my search today)

@SmokedMolex:
I love your comments about the beta testers, but there was a group of about 30 people in place for verification. There was even an extra test done to track the order by the main server too. The testers reported it was working good and i saw this was true because i saw the trades they made. So this testing has been confirmed in two ways. (this code is removed by now btw)

About the saying the software is a joke... it is not. You can setup a very easy strategy and make coins with it, just have a look here (https://www.haasbot.com/basic-strategies/) and here (https://www.haasbot.com/drop-loss-strategies/) These are the most basic strategies that one can setup and there is nobody who can tell me this is not working.

Just to tell: the screenshots on the pages that i posted are made yesterday from a live trading server. It are real screenshots, not simulated ones. The trades moments that you see there have really been executed. So tell me... is this broken software at work? I do not think so, the numbers and logs tell something else. (nothing holds you back to do the same like i did in these examples)

[SmokedMolex]

@Stephan

After this latest update, all the API information is gone again. All the bots are gone again.  It's like starting all over every time you update this software. Why is it so difficult?

I don't understand your development style.  The normal method of development is to release a candidate and call it alpha.  People test it, find bugs, you fix and release as a ("testing") release.  When you've patched as much as possible you call it beta and the testing still continues until you get to a point where a feature freeze is implemented.  But the way you are releasing software like crazy keeps us all chasing down problems. 

If we could get to a point where we say ok this is it 9.8.2.0 is running good and stable then that is fine.  I will use it knowing it has some quirks here and there.  That's understandable. So when you release 9.8.3.x I am expecting a solid upgrade path that fixes the previous issues WITHOUT adding NEW features.  Then when 9.9.x.x comes out I am thinking well ok this is going to be a big upgrade path and I may have to start over. But that's not what happens.  After this update I went back in to try and fix some things but it is a mess in that directory.

Now we got all kinds of problems with , and . and trades not running like they were before. 

Yes I understand it takes time to learn new software.  I've spent many days learning something and how it works only to find it completely broken or "modified" in a new release which makes all the time I spent before that a waste.

How would you feel if someone was wasting your valuable time with updates that were always broke, nonstandard or just plain didn't work?  And then understand that you paid almost $1000 for that? And then lost more than that on software that wasn't stable? And then had to spend even more time to relearn how things work with new versions?

I can't speak for everyone and I won't try to but I think any sane and rational person would be pissed off by this.

[Stephan224]

@Stephan

After this latest update, all the API information is gone again. All the bots are gone again.  It's like starting all over every time you update this software. Why is it so difficult?

I don't understand your development style.  The normal method of development is to release a candidate and call it alpha.  People test it, find bugs, you fix and release as a ("testing") release.  When you've patched as much as possible you call it beta and the testing still continues until you get to a point where a feature freeze is implemented.  But the way you are releasing software like crazy keeps us all chasing down problems. 

If we could get to a point where we say ok this is it 9.8.2.0 is running good and stable then that is fine.  I will use it knowing it has some quirks here and there.  That's understandable. So when you release 9.8.3.x I am expecting a solid upgrade path that fixes the previous issues WITHOUT adding NEW features.  Then when 9.9.x.x comes out I am thinking well ok this is going to be a big upgrade path and I may have to start over. But that's not what happens.  After this update I went back in to try and fix some things but it is a mess in that directory.

Now we got all kinds of problems with , and . and trades not running like they were before. 

Yes I understand it takes time to learn new software.  I've spent many days learning something and how it works only to find it completely broken or "modified" in a new release which makes all the time I spent before that a waste.

How would you feel if someone was wasting your valuable time with updates that were always broke, nonstandard or just plain didn't work?  And then understand that you paid almost $1000 for that? And then lost more than that on software that wasn't stable? And then had to spend even more time to relearn how things work with new versions?

I can't speak for everyone and I won't try to but I think any sane and rational person would be pissed off by this.

Yes i fully agree it is annoying if you lose the trade-bots and settings. Thats the entire reason why the save system has been changed last time and why you did lose them. I have warned for this in advance it will happen this time. (at least i understand you speak about the update from 0.8 to 0.9)

I thought the development style itself is not so complex. The past small update did not bring any big new features, the coming build will also not bring anything new. And if there is something, then thats something small. (a checkbox or some new information field for example)

Big updates or big fixes are tested in advance, this changes from a week to a couple days in advance (beta, the alpha test is already done by this time). Anything that comes back is collected and solved based on the impact is to the code and inner workings itself. (i am sure there are people who can confirm this)

Both the testers and the team test everything before its finally launched. And yes some things like the usage of decimals could go untested sometimes, i do not keep track of where the testers are located world-wide. So i have to admit i must put more care in this kind of things.

But at the moment, on the buglist there is not much.

This is what i have;
- Roof-in does not buy (confirmed, is solved for the next update)
- Strange web-errors are visible (confirmed, is solved for the next update)
- Possible price rounding issue found (solved in advance)
- BTC-e goes offline after X minutes (still unconfirmed issue)
- Orders remain open (still unconfirmed, maybe related to the BTC-e issue)
- Doge/Btc at Cryptsy does not work (still unconfirmed issue)

- Later: Re-review the ema calculation (confirmed changes but also expected changes due the new weighted prices)
- Later: Re-review all decimal input methods.

I do not push the update at the moment because there unconfirmed and open issues.

What i also want to say is that i do understand that you are pissed off. But really from my point of view its working here and i (and the team) are doing our best here to get the same problem(s) with BTC-e. Once we do we will solve it and give it a big stress test again. After this a update is pushed as usual. But needless to say, maybe we found it and we solved it and we could not find anymore issues. And even you may have tested it properly. This still can not avoid this kind of problems or bugs can happen. And again, it is anoying if its happens and i totally agree but i am not sure what to do more then what i do now.

Like i said before i am happy to get you into the beta testing each time. This allows you to comment in advance and make sure it works good for you to.

[AscotV]

Hi all,

I am a (proud) member of the Haasbot development team. I understand there are some issues at the moment and for this reason I will put some new features on hold.
To speed up the process of finding and resolving bugs I'm providing a "shortcut" for the bitcointalk community here: If you experience a problem and can collect as much technical details as possible (details on how to reproduce, debug logging, ...) you can forward this to <lander AT haasbot DOTcom>

Don't spam me with problems concerning licenses, payment, feature requests, vague issues ("Sometimes it hangs"),... I won't reply nor forward them, so don't bother. For all these things you can create a support ticket, as usual.

By the way: this is temporary. I'm not planning to become the first line tech support

[trubar]

When i restart tradebot one settings is lost. I found out that one xml is not saved properly. I am using last build of tradebot.

Whole XML:

<?xml version="1.0"?>
<TradeBot xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <GUID>a65956f8-10b9-406a-bd2b-93b2f8648b86</GUID>
  <Name>LtcBtc</Name>
  <FullLogbook>true</FullLogbook>
  <Platform>BTCe</Platform>
  <CurrencyExchange>
    <PrimaryCurrency>Ltc</PrimaryCurrency>
    <SecondaryCurrency>Btc</SecondaryCurrency>
  </CurrencyExchange>
  <CoinsPosition>Bought</CoinsPosition>
  <TradeBotAmount>
    <TradeAmountType>StaticTradeAmount</TradeAmountType>
    <StaticTradeAmount>1.0</StaticTradeAmount>
    <PercentageBoughtSide>50</PercentageBoughtSide>
    <PercentageSoldSide>50</PercentageSoldSide>
  </TradeBotAmount>
  <Activated>false</Activated>
  <LastBuyValue>0.027458750</LastBuyValue>
  <LastSellValue>0.028067835</LastSellValue>
  <TradeIndicators>
    <anyType xsi:type="IndicatorMAHistogram">
      <Platform>BTCe</Platform>
      <Exchange>
        <PrimaryCurrency>Ltc</PrimaryCurrency>
        <SecondaryCurrency>Btc</Se

I am losing settings of bots at restart. Can you save settings on 10 minutes interval or something. Not just on close of an app.

[Tron2013]

Version 0.9.9.1
is selling mutch below last buy price, like other version before (for my point of view)
Insurange Overcome and Never sell below are aktive but do not stopp the selling

They buy with 0.02799 and sell 4 min later with 0.01399 not realy nice

I am playing around some weeks and all the coins from my mining mashines BTC and Alt are gone with this tool.
Its better for me to do not aktivate the STB.