Username: Password:

Author Topic: Feature Request to mitigate bagholding  (Read 8450 times)

Offline Doc

  • Rookie
  • *
  • Posts: 35
    • View Profile
Feature Request to mitigate bagholding
« on: May 03, 2017, 01:39:57 PM »
When an alt has a bump it usually has a dump right after, but this dump isn't always smooth. More often then not it happens that after a bump there is a small dump, a very quick and short bump, and then a big dump again. My GUNBOT usually buys after the first dump, doesn't or can't sell after the short bump and  there I am with my bag for days...

what I'd like would be a function that prevents GUNBOT from buying right after a sell, it could be something like this:

dontbuy for: 100 cycles (GUNBOT cycles)
dontbuy for: 00:23:59:00 (in dd:hh:mm:ss format)
dontbuy for: 10% (meaning that if it sold at 1.00000000 GUNBOT won't buy above 0.90000000)
dontbuy for: 0.05000000 (meaning that GUNBOT won't buy above that value)
dontbuy for: false (dontbuy feature is off)

and it could be great to combine those with an AND/OR function like:

dontbuy for:  0.05000000 AND 00:02:00:00 (meaning that for 2 hours after a sell GUNBOT won't buy even if alt goes below 0.05000000)


just an idea, hope it helps

Offline Clannad

  • Rookie
  • *
  • Posts: 38
    • View Profile
Re: Feature Request to mitigate bagholding
« Reply #1 on: May 06, 2017, 10:24:18 PM »
Hi Doc,

I like the idea !  For myself I would prefer one of those two methods (technically they are equivalent because from % you can calculate price and vice-versa).

- dontbuy for: 10% (meaning that if it sold at 1.00000000 GUNBOT won't buy above 0.90000000)
or
- dontbuy for: 0.05000000 (meaning that GUNBOT won't buy above that value)

Let's see what Gunthar says about it ...