Username: Password:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - zardos

Pages: [1]
1
Technical Support & Development / Re: Bugs/Issues tracker v3.3.2
« on: June 20, 2017, 06:45:18 PM »
Manual buys will mess up the bot's ability to sell properly (will probably sell at a loss).

Currently, the bot will override it's buy price with the latest (manual buy) price.   It will then ignore any buy prices that it used before this... Only the last bought price in the My Trades book is used.

So if it buys:
BOT-->            AMT: 50    LP = $2     Paid $100   
and then then coin drops -- and I manually buy
MANUAL-->     AMT:30    LP=$1.50   Paid $45

It will throw away the "$2" price completely, and start selling GAIN% above price $1.50 (with all 80 coins).   This will be a loss.   This is probably unnecessary, but I'll do the simple math below to show it's a loss.   I'm assuming GAIN is at 0% for ease of computation (it should buy and sell and break EVEN with gain at 0%)

If the bot sells the 80 units at $1.50 (ignoring the fact it bought the 50 at a higher price) it will reap $120.    But there is $145 invested.  This is a loss of $25

Note: if you are freaked out that I have GAIN set to 0% -- ok, lets say it was at 2.5% --- it would then sell at $123 instead of $120... Still a loss of $22

2
General Discussion / Clicking sound with 3.2 GUI fix
« on: May 24, 2017, 12:56:51 PM »
Hey all, i wanted to tell everyone what i noticed tonight... I put on my headphones and was able to hear this "clinking/cluncking" sound with 3.2 GUI.  I soon realized it was the bot refreshing all the "web pages" (bots) on the GUI.   You can get rid of the sound by going to control panel and Sound... and changing the Start Navigation sound to None.   At first i thought my headphones were failing on me, lol.

3
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 24, 2017, 07:11:18 AM »
The frozen console GUI was fixed with the steps above. Thank you all!

But now I'm having this "Waiting for orders: 0 ETH" like on the image below.



Not only with ETH but with lots of other pairs too.

I have to stop the pair and start it again for it to be fixed.


THIS ^^^^^   
In Telegram, many many are talking about this issue.  It's the main issue I have every day.   I just looked at my 10 pairs, and 3 of them were stuck in this waiting for 0 order state.    Granted, some had BUY orders waiting... BUT, these buy orders were WAY down on the chart -- nowhere near a buy point.   So I have to manually close the BUY order (sometimes there isn't a buy order, it's just stuck with no orders), and restart the bots every 6 hours.   Hope you can figure out what is going on here!

4
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 13, 2017, 12:16:01 AM »
Priority ALLPAIRS-params.js vs poloniex-BTC_XXX-config.js changes after starting GUNBOT.

Tested: gunthy-linuxx64 - only with poloniex

ALLPAIRS-params.js:
Code: [Select]
...
BOT_SLEEP_DELAY:(1000) * 22
BOT_ON_FAIL_DELAY:(1000) * 55
...

poloniex-BTC_XXX-config.js:
Code: [Select]
...
BOT_SLEEP_DELAY:(1000) * 44
BOT_ON_FAIL_DELAY:(1000) * 55
...


>>> STARTING

When starting the bot (./gunthy-linuxx64 BTC_XXX poloniex) it prioritizes ALLPAIRS-params.js over poloniex-BTC_XXX-config.js.
Output:
Code: [Select]
next delay will be 22s

>>> RUNNING

Changing the ALLPAIRS-params.js while the bot is running will have no effect. Looks like the file is not watched.
But changing poloniex-BTC_XXX-config.js while the bot is running, triggers the reconfiguration and now it prioritizes poloniex-BTC_XXX-config.js over ALLPAIRS-params.js.

Changing poloniex-BTC_XXX-config.js to:
Code: [Select]
...
BOT_SLEEP_DELAY:(1000) * 44
BOT_ON_FAIL_DELAY:(1000) * 99 // <-- changed
...

Output:
Code: [Select]
next delay will be 44s
Suggestions:
- Watch both configs (ALLPAIRS-params.js and market-BTC_XXX-config.js) for changes.
- In any case (starting and running) prioritize the specific config (market-BTC_XXX-config.js) over the general config (ALLPAIRS-params.js).
I think this is what I am talking about too... here's what I wrote in Telegram & Gun asked me to post here:

1) set refresh time to 20 secs in Allpairs
2) set refresh time to 120 in Dash pair
3) start bot — it will use the 20 sec time
4) make a change and resave the Dash pair
5) Bot will reconfigure and use the 120 time
6) stop the bot and restart the bot — it will switch to the 20 sec time from AllPairs again

The problem here is, it breaks the reconfig totally.   I suggest it always use the AllPairs as the override regardless of which is saved last.        Of course, I also am an advocate of switching this, to make the coin's config the override, and All Pairs just a default (opposite of the way it works now)... but that's another issue for down the road.   I think the "quick fix" is to do what I said in second sentence.

PS - I always feel bad reporting/suggesting...     I wanted to compliment Gunthar on an awesome job on the bot!  Really good work!

5
I installed this today.. Working good!   In Settings, you can change the colors back to "Windows Default" which look a lot better than these above IMO
EDIT: You can also set it not to "dim" the brightness when the window loses focus.

6
This looks nice, thanks!

7
General Discussion / Re: Idea / Feature request: "The Bag Grower"
« on: April 13, 2017, 10:20:13 AM »
This is a cool idea!  I hadn't thought about breaking even and saving extra coins for long term investment.

8
General Discussion / Re: Price to Sell helper
« on: April 13, 2017, 10:11:48 AM »
The only way an Excel sheet can hurt you is if there are macros in it.   There are none in this sheet.  It would warn you if there were when you open it.

9
General Discussion / Price to Sell helper
« on: April 11, 2017, 06:25:11 PM »
I posted a simple Excel spreadsheet in the Telegram messenger for everyone, but I think it would be better to post it here.

It will take all your BUYs on a coin, and let you pick a % gain, and it will tell you the sell point for that.   It takes into account the Poloniex fees as well.  So you'd go to My Trades on Poloniex, and copy and paste the text into the sheet... Text like this:
2017-04-11 12:45:31   Buy   0.00397950   10.00000000   0.03979500
2017-04-11 12:44:29   Buy   0.00397950   0.12756235   0.00050763
2017-04-11 12:42:35   Buy   0.00397950   13.25420355   0.05274510
2017-04-11 10:30:53   Buy   0.00398421   0.76653741   0.00305404

Then just set the % and then you can copy the SELL AT price.   These instructions are on the Sheet too.
This sheet is free for all to use.  Please let me know if you find any errors, or make improvements!
Kevin Crane

10
Technical Support & Development / Re: For bagholders only
« on: April 11, 2017, 09:13:47 AM »
 :)

All I have to say on this thread at this time....
AKA Kevin Crane

11
This may not be the way Gunthar is going, but:

I'd like to see a "real GUI" for the bot instead of scrolling text.   Put the SELL price and BUY price is a UI that doesnt scroll... in a .... "Window".   Put other info too like how close it is to buying or selling, maybe as a progress bar.   Show last prices.   Maybe have buttons that do things.  Like one to force a sell/buy at market price.  A button to clear old buy orders and reset to BUY mode....   just brainstorming here.. But mainly, getting a static UI instead of scrolling text.

To be clear, I'm not criticizing, just suggesting!

Pages: [1]