Glad I never bought in.

I was seriously contemplating when it first started.

I can't wait to see some deliverables.

I think NB's image took a bit of a hit with the Bitfunder disaster. I certainly have a diminished view as a result of it, but hopefully I will be surprised come next month.

Be careful of failed site loads too. They will reset any martingale sequence and also put invalid data in your bet history (hence my previous graphs). The giving up on sequences bug has lost me quite a bit of money.  

Hope a patch comes out soon.

http://i.imgur.com/p8z1N3p.png

I've seen weirder graphs made too, where they curled back on themselves, but the most pressing bug is just that -1|-1 gets reported a few times every now and again.

If you get an undefined number (which you are somehow interpreting as -1), then it would be awesome if it was not written. I notice that around these -1 patches, I see the same bet # reported a few times... so perhaps the page is not loading fully?

Also, another minor improvement might be to block loading unnecessary things. Stuff like the banners and css style sheets take resources and included loading times.

In previous projects, when I have tried to go as lean as possible, I have cut back on things like that. You can easily open a browser window to watch the bot in real time, so do we even need to see the page? This is a pretty big change, so feel free to ignore it.

Apologies, I did read the beginner's guide, and I must have overlooked the description of what "Stop on Win" which is enabled by default does.

The bot speed however. is completely open to interpretation. "As fast as the site allows" reads to me as "as fast as I can with no restriction".

Also, I keep seeing a bug where invalid data is added to cache, which screws the graph. Shouldn't this be filtered?

http://i.imgur.com/JoaloK9.png

Works great, except for when you want to stop. The stop on win option does nothing, and neither does the stop button.

 

The other major feature request should probably be an inbuilt rate limit in line with the FAQ. It should bet once a second on low odds, and scale up. It's basically waste resources on both ends if you go faster than the site lets you.

Still waiting for latest version where my issues are apparently fixed. 

Try restarting. I needed to restart the client once after running for first time.

A few things need to be fixed.

The reset seed lower limit needs to be lowered to 1. http://i.imgur.com/TyR8LHH.png

The stop on losses in a row needs to be far higher than 100 and same with reset after. I want it to go up to at least 1000. http://i.imgur.com/DuOZcAh.png

I am assuming the multiple resets when you win.

Looks, good except it crashes on first bet.

http://i.imgur.com/EkMaPC2.png

EDIT: Has to restart and it was fine. This was the first time running it.

Yes, it certainly appears that Ukyo managed to steal a cool 2mill.

Awesome!

Not accepting Bitcoins fully? Madness! 

Need to reduce the bet cap! 

Not sure why you would jump to the conclusion that I dumped shares. I am aware of the deal... but like I said, my outlook of N&B management dropped as a result of this. "Just trust me to do something with your money" from N&B does not exactly inspire confidence.

What's not to understand? We have a shitty situation, and now an "established" company is stepping in to do something that they can't tell us anything about. The situation is not any less shitty, as all we know is the N&B is somehow involved (and the longer we left in the dark, the shiftier it looks). I reserve the right to point out that an announcement of an announcement of an announcement is not really helping the situation.

How do we know that N&B is helping, and in what capacity of helping should we feel more comfortable? For all we know, N&B could just be preparing to acquire WeExchange... or simply putting Ukyo in contact with another developer... what makes you think that this is automatically a positive?

No matter how I look at it, Ukyo is in the wrong here. If he can't post some kind of proof that the funds are intact or some kind of progress report on the actual technical difficulty, then the only logic conclusion is that the funds are not there.

The descriptions I add to transactions keep on getting lost.

It only preserves the most recent description. I am running latest version 5.15.

Requested further more detailed financials. Thanks for the response!

So what was this resolution process? All we know is that Neo & Bee are involved in this mess somehow now.

This is pretty piss poor management of the issue. I know that my outlook of Neo & Bee has dropped significantly as a result of this.

So is this getting swept under the rug? OP was keeping a list of the payments owed... and it opened my eyes to just how large a scale this was. He obviously crossed the lines with the personal threat... but surely that did not merit destroying the log of BTC owed?