02-25-2011
, 12:19 PM
02-25-2011
, 12:57 PM
02-25-2011
, 05:10 PM
02-26-2011
, 01:50 PM
You should set your Hand History folder location to the default location, the one that HEM takes HHs from, NOT to. TB reads the HHs at the same time HEM does.
S!K
02-26-2011
, 02:02 PM
Quote:
I play headup,and I lose so much money and reload so much times when I play with someone I can't beat or a very lucky guy.
Could you make the manully reload option unavailabe,so I quit when I lose one buyin.Of course the autorebuy option of the poker client is unchecked.
Thanks!
Could you make the manully reload option unavailabe,so I quit when I lose one buyin.Of course the autorebuy option of the poker client is unchecked.
Thanks!
Here's how I see this working; you can still set an overall stop loss for all tables, but you would now be able to set a stop loss for a single table loss as well, i.e if you lose $x on any single table that table alone will be closed.
I think we should be able to make that work, but the implementation and added logic will be trickier than it sounds. I'll have to discuss it with the team, but I'd like to hear thoughts on the usefulness of that. At least for me, there have definitely been sessions that would have gone way better had I killed the action on one table.
S!K
Is this just me?
03-01-2011
, 03:10 PM
I'm looking into this, haven't had any other reports though.
S!K
03-01-2011
, 06:28 PM
Nvm, figured it out. I had forgot the limit was the size of the BB, not the buy-in. 
But I have another problem. Every time I start up a client, the rage quit button crashes as it's launched, leaving a white rectangle that won't move. Could just be my computer, idk. Anyway, could you implement an option to hide the button as default? I never use it.
But I have another problem. Every time I start up a client, the rage quit button crashes as it's launched, leaving a white rectangle that won't move. Could just be my computer, idk. Anyway, could you implement an option to hide the button as default? I never use it.
03-01-2011
, 06:31 PM
Quote:
Nvm, figured it out. I had forgot the limit was the size of the BB, not the buy-in.
But I have another problem. Every time I start up a client, the rage quit button crashes as it's launched, leaving a white rectangle that won't move. Could just be my computer, idk. Anyway, could you implement an option to hide the button as default? I never use it.
But I have another problem. Every time I start up a client, the rage quit button crashes as it's launched, leaving a white rectangle that won't move. Could just be my computer, idk. Anyway, could you implement an option to hide the button as default? I never use it.
03-02-2011
, 12:47 AM
ehhhh, I probably deserve some blame for not having those video tutorials up yet
S!K
S!K
03-02-2011
, 09:05 AM
Quote:
So Tulip, I've been thinking about your issue and I think I may have a better solution than simply disabling Auto-Rebuy. The problem here is not that you have Auto-Rebuy on, it is that you are getting destroyed on a single table. Sooo what if we added another Stop Loss rule for individual tables?
Here's how I see this working; you can still set an overall stop loss for all tables, but you would now be able to set a stop loss for a single table loss as well, i.e if you lose $x on any single table that table alone will be closed.
I think we should be able to make that work, but the implementation and added logic will be trickier than it sounds. I'll have to discuss it with the team, but I'd like to hear thoughts on the usefulness of that. At least for me, there have definitely been sessions that would have gone way better had I killed the action on one table.
S!K
Here's how I see this working; you can still set an overall stop loss for all tables, but you would now be able to set a stop loss for a single table loss as well, i.e if you lose $x on any single table that table alone will be closed.
I think we should be able to make that work, but the implementation and added logic will be trickier than it sounds. I'll have to discuss it with the team, but I'd like to hear thoughts on the usefulness of that. At least for me, there have definitely been sessions that would have gone way better had I killed the action on one table.
S!K
Nice software!Nice people!
Thanks for your pm and hard work,waiting for the new function!
03-03-2011
, 02:49 AM
********
We finally figured out the timer error thanks to On The Clock, we should have a patch for that soon.
S!K
03-04-2011
, 12:16 AM
It is up there, but not quite first. I had to re-prioritize things for a strategic partnership.
Yes Tilt Breaker auto-updates. I like this idea a lot too, but like I said above I have to prioritize at the moment and my plate is full until May. This will be added though, because I think this will help a lot of people.
******
The next release will be fixes for all our bug reports. which are:
S!K
******
The next release will be fixes for all our bug reports. which are:
- Several reports of Stop Time Played resetting to 0 instead of going into lockdown
- We have 2 reports of TB missing hands
- One report of FTP's table closing automation failing on Rush tables
- Support all game types for Auto Break (I think only stud is left)
- A small new feature for your mindset that is a precursor to something much larger
- Another small feature that can be used for your mindset or strategy
- Some integration stuff for the strategic partnership
- A widget tool for the strategic partnership
- Tournament support
S!K
03-05-2011
, 07:02 AM
Hi,S!K,we can see you are very busy,thanks for your hard work,and I have an advice,as you said you are excited by the one table loss funtion which is your idea,I am excited too,I think all the nl and plo players are the same,so could you upgrade the one table loss function first?
I think the most important part of TB is auto-break tab,and the core is control the loss,the other functions are good,but not as important as function of control the loss.
TB is more import for big game players like nl and plo,as I know stud is limit game.Tournament is the same.So You can't lose a lot money as at nl and plo game at one time or one table immediately.
The strategy you said is good,however I learned a lot lessons about emotional control as the other players, it is tough to control tilt still, but TB can control your money no matter you tilt or not.So could you complete the stop loss function first,and work on other strategy later?
Sorry for my poor english
Best wishes!
I think the most important part of TB is auto-break tab,and the core is control the loss,the other functions are good,but not as important as function of control the loss.
TB is more import for big game players like nl and plo,as I know stud is limit game.Tournament is the same.So You can't lose a lot money as at nl and plo game at one time or one table immediately.
The strategy you said is good,however I learned a lot lessons about emotional control as the other players, it is tough to control tilt still, but TB can control your money no matter you tilt or not.So could you complete the stop loss function first,and work on other strategy later?
Sorry for my poor english
Best wishes!
03-05-2011
, 06:37 PM
03-05-2011
, 06:44 PM
Quote:
Hi,S!K,we can see you are very busy,thanks for your hard work,and I have an advice,as you said you are excited by the one table loss funtion which is your idea,I am excited too,I think all the nl and plo players are the same,so could you upgrade the one table loss function first?
I think the most important part of TB is auto-break tab,and the core is control the loss,the other functions are good,but not as important as function of control the loss.
TB is more import for big game players like nl and plo,as I know stud is limit game.Tournament is the same.So You can't lose a lot money as at nl and plo game at one time or one table immediately.
The strategy you said is good,however I learned a lot lessons about emotional control as the other players, it is tough to control tilt still, but TB can control your money no matter you tilt or not.So could you complete the stop loss function first,and work on other strategy later?
Sorry for my poor english
Best wishes!
I think the most important part of TB is auto-break tab,and the core is control the loss,the other functions are good,but not as important as function of control the loss.
TB is more import for big game players like nl and plo,as I know stud is limit game.Tournament is the same.So You can't lose a lot money as at nl and plo game at one time or one table immediately.
The strategy you said is good,however I learned a lot lessons about emotional control as the other players, it is tough to control tilt still, but TB can control your money no matter you tilt or not.So could you complete the stop loss function first,and work on other strategy later?
Sorry for my poor english
Best wishes!
I'm not promising anything though! If it ends up being a larger effort, development will most likely be moved to May.
***************
I will be releasing a new build sometime tonight. This build has a bunch of bug fixes, so no real new features.
S!K
03-05-2011
, 07:22 PM
Quote:
Hi,S!K,we can see you are very busy,thanks for your hard work,and I have an advice,as you said you are excited by the one table loss funtion which is your idea,I am excited too,I think all the nl and plo players are the same,so could you upgrade the one table loss function first?
I think the most important part of TB is auto-break tab,and the core is control the loss,the other functions are good,but not as important as function of control the loss.
TB is more import for big game players like nl and plo,as I know stud is limit game.Tournament is the same.So You can't lose a lot money as at nl and plo game at one time or one table immediately.
The strategy you said is good,however I learned a lot lessons about emotional control as the other players, it is tough to control tilt still, but TB can control your money no matter you tilt or not.So could you complete the stop loss function first,and work on other strategy later?
Sorry for my poor english
Best wishes!
I think the most important part of TB is auto-break tab,and the core is control the loss,the other functions are good,but not as important as function of control the loss.
TB is more import for big game players like nl and plo,as I know stud is limit game.Tournament is the same.So You can't lose a lot money as at nl and plo game at one time or one table immediately.
The strategy you said is good,however I learned a lot lessons about emotional control as the other players, it is tough to control tilt still, but TB can control your money no matter you tilt or not.So could you complete the stop loss function first,and work on other strategy later?
Sorry for my poor english
Best wishes!
- Should the Delay Timer come up?
- If so, should it be a different looking delay timer? Maybe a timer that comes up over the specific table?
- After the table is closed should you be in lockdown, i.e. not able to open up any new tables?
- If you didn't go into lockdown, do you think you would be tempted to re-open the closed table? Hmmm, actually assuming we have TB knowing which table to close, theoretically we could use some of the same logic to block that single table from opening.
Ok, so after typing out my thought process, it seems like the ideal way to execute this would be to possibly have a new delay timer come up on the single table, and then once the table is closed you are not in lockdown, but you won't be able to open up that table name again until your session is over.
Thoughts?
S!K