Any word on initial exchanges?

Is there any more word on the ICO quoted at the following url?

http://mmxivcoin.com/forum/index.php/topic,2.0.html 

I do believe I had the funds.  Was working buy sell order on the scale of 100,000 sat btc at a time and 0.3333 sat MMXIV with reserves of .1btc and 20mmxiv.  Been using the tool for weeks many instances with very few problems.  Could not get it to go and keep going on this market.  was wondering if anybody else had same issue. 
Was thinking maybe it was some sort of precision issue. What type of variables are being used to hold ask/bid prices? (Float, decimal, double?)  was also wondering about the Satashi above below values.  How would one represent a 2btc markup 200,000,000 sat?     

Ran into another issue where trader stops placing sell orders.   I was trying to get a bot on bittrex MMXIV and buys and sells at 0 volume 0.06. (Had radio set to below) It would place the order first time through but the next ping would cancel order and would not place another sell. 

so no wallet tonight either then?  Alright thanks.

Website down? When I go to http://www.mmxivcoin.com I get http://www.mmxivcoin.com/cgi-sys/suspendedpage.cgi

I'm using extra small instances of windows azure, nice I don't have to worry so much about having the boxes around.  Was running 3 instances per vm.  Been running for a couple weeks now.

Great concept and the app is becoming more bullet proof.  The app saves time and adds the dimension of time.
That and it costs you 3000 qtl to run it. (Really 6000 3000 on bittrex and 3000 on polo if reliability is a factor. )
That and talk of more features for more qtl.

Awesome, thanks will retest on polo and cryptsy.
Verified price calculations are accurate on cryptsy and polo.
Have some issues with polo not canceling orders.  That is orders are piling up.  Not sure what is going on there.  Also noticed the cancel message comes after the price message so it is hard to see what the orders are.  Would recommend giving them there own label.

am running Version 2.1.1.5 on Cryptsy in the Drk/btc and the app fails to calculate the correct price.

the choices I have are Satoshis Below top bid 3500 and the current asking price is 0.00794501 and so my price it should be placing orders is 0.00791001 when it is placing them at  0.00793627.  Tried killing the app  and restarting but did not change things.

Anybody else on Cryptsy notice the discrepancy? Only appears to me on Cryptsy and not on bittrex.  Have not tested Polo yet. 

Verified.  I can run 2 instances on same box.  Not sure I would recommend it though.
Verified.  Steps back Nicely when selling at -x and bid becomes current order.  Thanks, to me that was a key problem the rest so far are nice to haves...  

Verified that it does not save defaults any better.  Fails to save radio and resets to Below Top Ask which really means for more than the top asking price.  This bug is the next biggest source of lost money for me.  especially since we are running multiple instances again on the same box.  you forget to change to below and hit start and if your conservative like me you want to place your orders back a bit but instead it goes forward.  only hope you sell to yourself and your out just fees.

Many thanks  Matt
    

Not just cryptsy. I have reported the problem 4 times. If you choose bottom radio option and your buy/sell becomes current bid app fails to cancel and recalculate. (bottom radio control meaning Satoshi Above Top Ask or Satoshis Below Top Bid)

If you run at +1 yes.  I just want -1 to cancel every ping and recalculate as if first time through.
Bigger the spread the more vulnerable you are.  Defaults don't save for the plus minus option. By default it's plus so forget to hit the radio.
I like the app. I think it could go through a few more rounds of big fixes before anything else.  It's only as strong as the weakest link.  If it would cancel and recalculate app would be much more powerful. The other would be to find out what limitation was introduced that restricts multiple instances.

Yes that is the bug it does not cancel.

1000 sat spread set to -1 1 below current buy. rouge buy for 50000 sat gets placed at x+990, bot moves on next ping to x+989 or 990-1.  rouge order gets canceled. your 989 order does not.    At this point if you are watching you scurry around to try and cancel the order because on the next ping you order stays at +989 untill it sells or looses it's current price status.
When what it should do is cancel the order and recalculate on the next current price.  
Same works in reverse.  
1000 sat spread set to -1 or 1 below current sell.  rouge sell for -900 gets placed and bot moves to -898.  Sell gets bought or canceled and your -898 is now current order and it will not cancel and reset back to -1 of the next best order.

big enough spread and bot looses via repeated rouge buys.  by rouge buy I mean an order that totals 50000 sat or just enough to make an order. Priced -1 or -2 of current sell.  If you have bot set to +1 forget it.  rouge order will send you right into a buy sell wall.  
Thanks for asking.  

Anybody acknowledge this problem? Thanks.

First strategy be a part of all the movement vs Catch dumps and pumps. 
Problem is that if you set bot too aggressive it pays too much and becomes a target.  So then it becomes catch strategy.
Frequency is another major axis. 5-10 or 1-2 min vs 35-5 sec.  say 15 -30 sec but priced 100 below and it may never sell because it rides too high on the waves.  A wale comes and it never reaches you because it moves to slow and market recovers. 
Coin...  I would not recommend using on qtl because it messes around with totals to keep operating.  better getting your 3000 and holding and auto trade in a different coin.  there is a bug in current version that will register account with insufficient funds on the first cancel regardless of how many coins you have.  Trading in an all together different coin removes that possibility.  keeps it running.
Just started running another issue of ticker causing ping pong to stop due to large number of exceptions.

beyond all that it's great it makes orders consistently.  It is endlessly configurable and sometimes buggy. but it makes orders and so if you start small 50000 sat is minimum and run it you can find the right settings and turn up the heat.  Takes time and you have to be prepared to fail so big money fast no so much...
I have had luck in the Pink market on bittrex started with 1000 at -1 sat mostly thrashed and probably lost a bit on fees and bugs not removing orders when it becomes current price.   changed to 3000 at -3 which accumulated good/balanced, got greedy and upped it to 5000 at -5 sat and in this market that proved to be a long wait, 4-5 hours, so in the end I am testing with azure small instances each running 1 copy of the I have somewhat settled on -4 for 40-75 sec for 8000 pink an we will see where it goes.  I have transacted over 200 order over the weekend and it's growing so ++.

Additionally if your too impatient it's easy to say go with above/below radio set the wrong way.  since by default it goes the to aggressive way.   
 

Bug in all versions I have tested to date.  In auto ping pong if you set sell for less than current price and current price becomes your bid, the order fails to cancel order and reset to next lower price.  This issue makes using the app dangerous for most coins and larger volumes.

Error appeared for me when I try and run more than one instance of the app at the same time on the same machine. At the moment I start auto pong on second instance with first one running.

Help with bugs all versions to date.
does not work when trying to run multiple instances of the trader on the same machine at the same time.
Testing on autotrade on Bittrex, if my order was placed at below the current price by 1 and the current price gets sold or removed my -1 order is now the top order.  When the countdown hits 0,   The order should be cancelled and recalculated to -1 the next highest ask/bid order.  Where as I have noticed that my order gets left as the top order for sale and other traders are able to take advantage of the bot.  If I opt for satashi below current price and my order becomes the current price then on the next ping it should recalculate and move my order down to -1 of the next current price.  This is a real weakness in the app. Rouge buy and sell order totally leave users of the app vulnerable.  
Another nice to have would be export to excel in my history portion.  
Also another simple fix would be to make the default radio button value be below the top bid or above the to ask instead of the other way around.  Really easy to miss that and lose BTC, especially if you have to re enter the settings everytime the app loads.  You put in for 300 satoshi less bit forget to hit the radio and you are selling.
Would also love to see range limits on each side to set max and min prices I want to pay and if the current price plus minus offset is outside price limits then skip moving the order.  thanks.