So are you switching hi/lo?  Or changing the chance?

   If I understand you correctly, I think that the above, with addition stuff would do it.  lossstreak is a counter of loses before a switch.  lossswitch is when it will switch.
So the first loss lossstreak will go from 0 to 1 and loss switch will be 1 so it will switch.  It resets lossstreak to 0 and lossswitch to 2.  If you lose again, lossstreak will be 1 and switch is 2, and another loss and it will be streak 2 switch 2, so it should switch. 

Another easier to code way to go would be

if (math.random() < .5) then bethigh = !bethigh end

That line will switch randomly about 50% of the time.   random gives a random number between 0 and 1.  so you can change the .5 to whatever value you like.  .75 for 75% switch or .25 for 25% or any other number between 0 and 1.

Just add that to the else part of your script. 

   You could easily do that.  But you don't have it completely described.    If your just planning to lose all of the bets that's easy...

I think your asking to switch hi/lo each time you lose 1 more then the last time. 

What happens when you win?  Reset back to switch on the first loss?

You would need two counters.

lossstreak = 0 -- How many loses in the current streak
lossswitch = 1  -- When to switch


if (win) then   --  Bet won

   lossstreak = 0  -- reset
   lossswitch = 1 -- reset

else   -- Bet lost

   lossstreak += 1  -- increase lossstreak

   if (lossstreak == lossswitch) then
      bethigh = !bethigh
      lossswitch += 1  -- increase switch count
      lossstreak = 0  -- start streak again
   end 
   
end

   Hopefully that helps. 



 

 

   I tried again, and got the failure, but the balance was updated correctly.  Figured I would delete the info in the roaming folder.  no I get an unhandled exception.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.Serialization.SerializationException: There was an error deserializing the object of type DiceBot.pdlogin. Encountered unexpected character 'U'. ---> System.Xml.XmlException: Encountered unexpected character 'U'.
   at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, XmlException exception)
   at System.Runtime.Serialization.Json.XmlJsonReader.ReadAttributes()
   at System.Runtime.Serialization.Json.XmlJsonReader.ReadNonExistentElementName(StringHandleConstStringType elementName)
   at System.Runtime.Serialization.Json.XmlJsonReader.Read()
   at System.Xml.XmlBaseReader.IsStartElement()
   at System.Xml.XmlBaseReader.IsStartElement(XmlDictionaryString localName, XmlDictionaryString namespaceUri)
   at System.Runtime.Serialization.XmlReaderDelegator.IsStartElement(XmlDictionaryString localname, XmlDictionaryString ns)
   at System.Runtime.Serialization.XmlObjectSerializer.IsRootElement(XmlReaderDelegator reader, DataContract contract, XmlDictionaryString name, XmlDictionaryString ns)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalIsStartObj ect(XmlReaderDelegator reader)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
   at System.Runtime.Serialization.XmlObjectSerializer.InternalReadObject(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
   --- End of inner exception stack trace ---
   at DiceBot.json.JsonDeserialize[T](String jsonString)
   at DiceBot.PD.Login(String Username, String Password, String otp)
   at DiceBot.cDiceBot.btnLogIn_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
DiceBot
    Assembly Version: 3.0.0.2
    Win32 Version: 0.0.0.0
    CodeBase: file:///C:/Users/Bob/bitcoin/Bots/DiceBot-3.0.3%20Beta/DiceBot.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34251 built by: FX452RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
SharpLua
    Assembly Version: 2.0.4696.34005
    Win32 Version: 2.0.0.0
    CodeBase: file:///C:/Users/Bob/bitcoin/Bots/DiceBot-3.0.3%20Beta/SharpLua.DLL
----------------------------------------
System.Windows.Forms.DataVisualization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.DataVisualization/v4.0_4.0.0.0__31bf3856ad364e35/System.Windows.Forms.DataVisualization.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data.SQLite
    Assembly Version: 1.0.94.0
    Win32 Version: 1.0.94.0
    CodeBase: file:///C:/Users/Bob/bitcoin/Bots/DiceBot-3.0.3%20Beta/System.Data.SQLite.DLL
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Transactions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Net.Http
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Net.Http/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Net.Http.dll
----------------------------------------
PresentationCore
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll
----------------------------------------
WindowsBase
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
SMDiagnostics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll
----------------------------------------
System.ServiceModel.Internals
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Went back to 3.0.1 and logged into PRC fine.  Logged out and tried 3.0.3 and still getting the "failure to login or register".  Weird thing is it correctly updates my balance.  That shouldn't happen if the password or userid was invalid.     
  

    Just downloaded the 3.0.3 beta.  I was unable to log onto PRC and Just-dice.  PRC updated the balance and then said logon failed.  Just-dice just failed.  Went back to 3.0.2 and logged onto both sites fine. 

   It's not "Hard" at all.  "expensive" is relative. 

Only you can decided if it's worth investing in. 

Once this dig whale finishes I'm guessing we'll have around 1.2 Mil clams. 

Assuming all are staking that's 1440 / 1200000 =   .12% inflation daily.  .12 * 365 = 43.8% yearly

Those are just the staking assumptions.   There is much more to consider before investing in a coin.  anticipated price, long term value, stability, etc etc.  And I'll leave that up to you.. 

   I took a quick look, and I'm no expert by a long shot.  I selected one of the 4.6 clam inputs, and that wallet had several 4.6 clam inputs, looking back at one of those, they came from the digger.  So it almost looks like the digger has several accounts on Poloniex.  That's one way around the withdrawal limits...    

   Depending on the system load on Poloniex, your deposit could be used to fund someones withdrawal, with out being merged into another address.  So just because you see a lot of 4.6 input's doesn't mean Poloniex is digging.  it only means Poloniex has a lot of clams broken up into 4.6 clam piles.  Which make sense since the digger is using Poloniex to unload.  


    This is not to say it could not be Poloniex, Just that based on them giving away clams in the beginning (via a dig???) and the fact the digger is using poloniex, makes it more unlikely.  

   Or...   The digger is sending his 4.6 clam outputs to poloniex...  Poloniex was the first exchange to have clams,  They had a large clam giveaway.  I thought it had to do with them digging their clams at that time. 

   Oh that would make sense.  OK, Will wait for your update.  Thanks

   Hey Seuntjie,

   Can you take a peek at the tip function for JD.  Doesn't seem to be working correctly.  Not sure exactly what the problem is, but I think the tip gets kicked off, but doesn't complete.  Then my script keeps retrying it and eventually gets muted.  I don't know for sure it's the script retrying, but that's my guess.

            Thanks 

   That site only works for Just dice users.  You have to have a userid on just-dice, and it has to be registered with the faucet.  The faucet tips the clams to the user instead of sending via the blockchain. 

   Yup, I missed the -8.2 bet and forgot he would keep all of the profit on the last streak. 

That's still to risky for me.  You have to wade through all of those loses, hoping to hit that 10 green streak.   He is betting 60% or was it 65% (can't see the screen shot while typing this).  Even then he could go quite a while...

   Try it again.  If you start at the bottom.  He bets 2.869 and wins 1.501.  He's not taking that profit.  His next bet is for 4.370 (2.869 + 1.501) So he's still risking his original bet (2.869) and now the profit he made (1.501).  He won that and tries again (6.656).  And then he busted (10.137)  

   He didn't lose 10.137 he lost 2.869, and the time to make the other bets.  If you look, the only streak he stopped increasing and locked in his profit, was the one he won 100 on.  

   So he lost every other streak.  But you only count the initial bet in each streak (because that's the actual lose)
2.869 5.393 6.654 4.368 8.210 6.652 5.390 (4.363)

He lost 39.536 ( + all profit) before his winning streak started.  

   It is really weird.  His starting bets are not always the same (as far as I can tell).  But it looks like he takes his starting bet and adds the winnings for the next bet.  So he won around 100 clams risking around 4.  It looks like he's actually losing quite a bit to get that 100 clam win...    

   Actually just in that screen shot, he lost around 37 clams to make 100.  That's not bad. of course that's just one screen shot.   

   Now that, there is funny, I don't care who you are....   

   He is including himself in the current clam investors, not as a whale/digger.   

  No...  He's running a bot.

10:37:11 *** (986902) <botox> [#783773238] bet 1.08584688 CLAM at 80% and won 0.25788863 CLAM ***

IS the sky falling?  Again!!!  

    As long as this is not an exploit, I have no problems with the clams being dug.  We shouldn't change the rules in the middle of the game.  

I would bet 80% of clam holders would want to freeze digging, just to hold their stake and value.  I'm in the 20% club, that says let it ride....

Once this person finishes digging/dumping, the price will stabilize for a little and then continue to rise.  But there should then be more clams on the market to help the growth without it getting to out of hand, to quick.          

   Now's the chance to by fresh clams, cheap....  

   Try walletpassphrase=your wallet pass phrase. 

   Happy belated Birthday to QiBucks. 

My first transaction to my wallet was 8/11/14.   A bit late, but 1 year + and still going strong.   Way to go.... 

   Staking is a very modest 5% per year, so your looking at 1.36 QBK per day staking 10,000.

Bag bonus for someone with just a little more then 10,000 last month was 0.0121875 BTC.  The bonus varies, But that gives you an idea what it could be.