Welcome, Guest. Please login or register.
September 22, 2020, 02:26:33 AM
Home Help Login Register
News:

Shanky Technologies Poker Bot Support Forum  |  General Category  |  Working Profiles (Moderator: sngbot)  |  Topic: Egor's 6-pack profile 0 Members and 1 Guest are viewing this topic.
Pages: 1 [2] 3 4 ... 15 Print
Author Topic: Egor's 6-pack profile  (Read 147448 times)
Mrphil
Extreme Botter
*****

Karma: 70
Posts: 1957


full limit = rakemaker


« Reply #20 on: October 21, 2014, 12:49:48 AM »

Egor,

I've been testing this profile and haven't seen anything big jump out at me. It's a very pushy little beast and most likely pi$$es off the other players at the table.

I'm not a great strategist or 6-man player, but I was wondering if you think it might be beneficial to differentiate between the cutoff compared to Button or Small blind when it comes to some of the weaker hands.

For instance, sixpack would raise with 97o from the cutoff (with no raises/calls). I could see the button and small blind positions doing this, but I'm not sure if raising from the cutoff is optimal play in the long run.

Again, I'm no expert, but I'm bringing up the question of whether you would want to further define some of the weaker hands to possibly only be raised when stilltoact<=2 instead of three?

Logged

My life is a "missed click restoring state"
surfergrrrl
Botter
***

Karma: 5
Posts: 175


« Reply #21 on: October 21, 2014, 01:28:09 AM »


For instance, sixpack would raise with 97o from the cutoff (with no raises/calls). I could see the button and small blind positions doing this, but I'm not sure if raising from the cutoff is optimal play in the long run.


Open raising 97o from the cutoff is a losing play at the vast majority of tables.
Logged
Egor
Forum Admin
Extreme Botter
*****

Karma: 361
Posts: 33703



WWW
« Reply #22 on: October 21, 2014, 03:21:47 AM »

It's a good suggestion and I'm willing to listen.  popcorn
Logged

Please do not PM me about license issues or help stuff - email me or use the Help board. Thanks! -Egor
Mrphil
Extreme Botter
*****

Karma: 70
Posts: 1957


full limit = rakemaker


« Reply #23 on: October 22, 2014, 04:06:42 PM »

Egor, found a bug with the logic of the flop.

The first two lines of the flop:
"When botslastpreflopaction = raise and bets = 0 and raises = 0 and position = first and opponents = 1 usercr
When usercr and random <= 35 call force"

The problem comes when the first line becomes true when we are the first to act on the flop, but it stays true, even to any bet by opponent.

For instance, if we are first to act, we will check, but then there is a 35% chance we will call ANY bet from the remaining opponent no matter what our hand or stacksize. I think you meant to make the second line have a "and bets = 0" to read "When usercr and bets = 0 and random <=35 call force".

Otherwise, you get what happened to me here:

Code:
Shanky Technologies Holdem Version 7.6.4: Hand: 7h 8h
Players = 4 have 87 suited
If calls = 3 or more and raises = 0, call but fold for 2 raises cold
raise if opponents left <= 3 and no calls and first hand cards is black
hands played in session = 55
in timer: players = 4, folds in game= 2, raises = 1, checks = 0, calls = 0, bets = 0, folds = 2
casino =  *Redacted*, game = No Limit Cash, BB = 0.05, Pot = 4 BBs, Stack = 6.48, TI = 0 BBs
In Small Blind
Default Profile: "Doodle 104", Action = call force
Matching user defined condition at line 10, Action = raise 80% force
typing 0.31
clicking Raise
Flop: 5d 4h 5s
Board: pair with 3 suits
have backdoor flush draw
in timer: players = 4, folds in game= 3, raises = 0, checks = 0, calls = 0, bets = 0, folds = 0
casino =  *Redacted*, game = No Limit Cash, BB = 0.05, Pot = 12 BBs, Stack = 6.48, TI = 5 BBs
opponents = 1, position = first
Fold or Bet if checked and fold for a raise
Default Profile: "Doodle 104", Action = betpot force
User defined variable usercr set to true at line 15
Matching user defined condition at line 16, Action = call force
clicking Check
in timer: players = 4, folds in game= 3, raises = 0, checks = 0, calls = 0, bets = 1, folds = 0
casino =  *Redacted*, game = No Limit Cash, BB = 0.05, Pot = 21 BBs, Stack = 6.48, TI = 5 BBs
Matching user defined condition at line 16, Action = call force
clicking Call
Turn: 5d 4h 5s Ts
Board: Pair no possible straight two of one suit
special condition rule 7
in timer: players = 4, folds in game= 3, raises = 0, checks = 0, calls = 0, bets = 0, folds = 0
casino =  *Redacted*, game = No Limit Cash, BB = 0.05, Pot = 28 BBs, Stack = 6.48, TI = 13 BBs
opponents = 1, position = first
Fold or Bet if checked and fold for a raise
Not betting because of Never Bet Below option value
clicking Check
River: 5d 4h 5s Ts Kh
Board: Pair no possible straight, no possible flush
betting on flop but no betting on turn
in timer: players = 4, folds in game= 3, raises = 0, checks = 0, calls = 0, bets = 0, folds = 0
casino =  *Redacted*, game = No Limit Cash, BB = 0.05, Pot = 28 BBs, Stack = 6.48, TI = 13 BBs
opponents = 1, position = first
Fold
Default Profile: "Doodle 104", Action = fold force
clicking Check
in timer: players = 4, folds in game= 3, raises = 0, checks = 0, calls = 0, bets = 1, folds = 0
casino =  *Redacted*, game = No Limit Cash, BB = 0.05, Pot = 48 BBs, Stack = 6.48, TI = 13 BBs
Default Profile: "Doodle 104", Action = fold force
clicking Fold
« Last Edit: November 03, 2014, 09:14:41 PM by Mrphil » Logged

My life is a "missed click restoring state"
Egor
Forum Admin
Extreme Botter
*****

Karma: 361
Posts: 33703



WWW
« Reply #24 on: October 22, 2014, 09:05:35 PM »

That's a good catch, thanks!
Logged

Please do not PM me about license issues or help stuff - email me or use the Help board. Thanks! -Egor
Mrphil
Extreme Botter
*****

Karma: 70
Posts: 1957


full limit = rakemaker


« Reply #25 on: October 23, 2014, 04:05:09 AM »

I thought I would post my modification to possibly be included in an official change.

Changes made to original profile:
1. Added doodle's initial bot settings (the lines above any preflop code) with 120 min bathroom break and sitout if less than 2 opponents on table (Egor usually likes to leave as heads-up with bot but I prefer not)
2. Added fix to the flop mentioned to egor above
3. Changed some of the weaker hands to open raise preflop from the button and small blind, but not the cutoff.
4. Changed to reraise preflop on some of the weaker hands to a frequency of 25% instead of 65% as was initially coded.
5. People wanted to change the profile to play like doodle after 6-pack reached a set number of BBs. I added in a custom user variable to make this easy to happen. Right now, it is set to stacksize <= 999 for the profile to play as 6-pack, but if a user changed the "999" to "200", the bot will play as the default .ppl (which by default is doodle) once the stacksize has doubled up. You can change the stacksize variable to be whatever you want, and it will ensure that the bot will either play 6-pack or default .ppl (doodle) depending on your stacksize at the start of your current hand.

Comments / Questions are welcomed. Hopefully we can continue to improve on this. It's a really aggressive little 6 man beast.

Code below:

--------------------------------

MaxSessionHands = 10000
MaxSessionTime = 720
MaxStackSize = 1000000
BathroomBreakAfter = 120
BathroomBreakTime = 2
SitOutWhenOpponentsAreLessThan = 2
MakePotSizedPreFlopRaisesWhen = 6
FoldToPre-FlopRaisesForAQAJsKQ = OFF
FoldPost-FlopBelowTopPairToAnyBetOrRaise = OFF
FoldToPost-FlopRaisesWithUnpairedBoardsFor = 2
FoldToPost-FlopRaisesWithPairedBoardsFor = 4
NeverBetTurnOrRiverWithHandBelow = 3
NeverBetFlopWithHandBelowMiddlePairWhen = 1
NeverBetFlopWithHandBelowMiddlePairStackSize = 100000
NeverCallPairedBoardsWithHandBelow = 5
NeverCallFlushPossibleBoardsWithHandBelow = 6
FoldToPre-FlopRaiseWith55Or66When = 3
FoldToPre-FlopRaiseWith77Or88When = 3
FoldToPre-FlopRaiseWith99OrTTWhen = 3
FoldToPre-FlopRaiseWithJJOrQQWhen = 2
FoldToPre-FlopRaiseWithAKWhen = 3
FoldToPre-FlopRaiseWithAQsWhen = 2
FoldToPre-FlopRaiseWithAKsWhen = 3
FoldToPre-FlopRaiseWithKQsWhen = 2
SuperTightPlay = OFF
SemiSuperTightPlay = OFF
NoLimp = 15
AggressivePreFlop = 7
AggressivePostFlop = 3
AggressivePreFlopStackSize = 1000000
AggressivePostFlopStackSize = 1000000
MiningForSets = 5
PostFlopinBlindsOverride = 3
PreFlopReRaiseOverride = OFF
MinBetOverride = 5
FoldOrGoAllInWhenOpponentsAfterFoldsLessThan = 5
FoldOrGoAllInWhenOpponentsAfterFoldsLessThanStackSize = 1000000
ApplyFoldOrAllInAfter = 0
FoldOrGoAllInWhenOpponentsAtTableLessThan = 5
FoldOrGoAllInWhenOpponentsAtTableLessThanStackSize = 1000000
AlwaysCallWhenOpponentsRaiseIsLessThan = 4
AlwaysCallWhenStackSizeIsLessThanTotalInvested = 90
Verbose = ON
AutoPlay = ON
UserDefinedGameType = 0
UseOcrAtFullTilt = OFF
AutoRebuyAtUB = ON
AlwaysAskForTableName = OFF
EnableFoldInTurn = OFF
DefaultBetSizeFlop = 100
DefaultBetSizeTurn = 75
DefaultBetSizeRiver = 60

custom
preflop

When botslastaction = none and stacksize <= 999 Usersixpack
//You can set the above stack size limit to whatever you want sixpack to stop working at and for doodle to kick in, for instance three hundred would have doodle play instead when ur over three hundred bb to start the hand


When Usersixpack and raises = 0 and calls = 0 and stilltoact <= 3 and (pairinhand or hand = A or hand = KQ or hand = K9 suited or hand = K8 suited or hand = K7 suited or hand = Q9 suited or hand = Q8 suited or hand = JT or hand = J9 or hand = J8 suited or hand = J7 suited or hand = T9 or hand = T8 suited or hand = T7 suited or hand = 98 or hand = 97 suited or hand = 96 suited or hand = 87 or hand = 86 suited or hand = 85 suited or hand = 76 or hand = 75 suited or hand = 74 suited or hand = 65 or hand = 64 suited or hand = 54 suited) raise 2 force

When Usersixpack and raises = 0 and calls = 0 and stilltoact <= 2 and (hand = 86 or hand = 97 or hand = T8 or hand = T7 or hand = J8) raise 2 force

When Usersixpack and raises = 0 and calls = 1 and (hand = AA or hand = KK or hand = QQ or hand = JJ or hand = TT or hand = 99 or hand = AK or hand = AQ suited or hand = AJ suited or hand = KQ suited) raise 3 force

When Usersixpack and raises = 0 and calls = 1 and stilltoact <= 3 and (hand = 88 or hand = 77 or hand = 66 or hand = 55  or hand = AQ or hand = AJ or hand = AT or hand = A suited or hand = KQ or hand = K9 suited or hand = JT or hand = J9 suited or hand = J8 suited or hand = T9 or hand = T8 suited or hand = 98 or hand = 97 suited or hand = 87 or hand = 86 suited or hand = 76 or hand = 75 suited or hand = 65 or hand = 64 suited or hand = 54 suited) raise 2 force

When Usersixpack and raises = 1 and amounttocall <= 4 and stilltoact <= 3 and (pairinhand or hand = A suited or hand = KQ or hand = JT or hand = J9 suited or hand = T9 or hand = 98 suited or hand = 87 suited or hand = 76 suited or hand = 65 suited or hand = 54 suited) and random <= 65 raise 80% force

When Usersixpack and raises = 1 and amounttocall <= 4 and stilltoact <= 3 and (hand = 64 suited or hand = 65 or hand = 75 suited or hand = 76 or hand = 87 or hand = 86 suited or hand = 85 suited or hand = 97 suited or hand = 98 or hand = J8 suited) and random <= 25 raise 80% force

When Usersixpack and raises = 1 and amounttocall <= 4 and stilltoact <= 3 and (pairinhand or hand = A suited or hand = KQ or hand = K9 suited or hand = K8 suited or hand = K7 suited or hand = Q9 suited or hand = Q8 suited or hand = JT or hand = J9 suited or hand = J8 suited or hand = J7 suited or hand = T9 or hand = 98 or hand = 97 suited or hand = 96 suited or hand = 87 or hand = 86 suited or hand = 85 suited or hand = 76 or hand = 75 suited or hand = 65 or hand = 64 suited or hand = 54 suited) call force

flop
When Usersixpack and botslastpreflopaction = raise and bets = 0 and raises = 0 and position = first and opponents = 1 usercr
When Usersixpack and usercr and bets = 0 and raises = 0 and random <= 35 call force
When Usersixpack and usercr and bets = 1 and raises = 0 and amounttocall < 20% stacksize and random <= 50 raisepot force
When Usersixpack and usercr and bets = 0 and raises = 0 bet 75% force
When Usersixpack and botslastpreflopaction = raise and bets = 0 and raises = 0 bet 75% force

When Usersixpack and pairinhand and havestraightdraw and raises = 1 and amounttocall < 16% stacksize call force

When Usersixpack and opponents = 1 and bets = 1 and raises = 0 and not (botslastpreflopaction = raise or position = first or amounttocall > 50% potsize or amounttocall > 15% stacksize) and random <= 25 raise 80% force

When Usersixpack and (bets = 1 or raises = 1) and opponents = 1 and potsize > 5% stacksize and potsize < 20% stacksize and not (paironboard or flushpossible or straightpossible) and (haveset or havetwopair or hand = AA or havenutflushdraw) and random <= 50 raisemax force

When Usersixpack and (bets = 1 or raises = 1) and opponents = 1 and potsize > 5% stacksize and potsize < 20% stacksize and not (paironboard or flushpossible or straightpossible) and havestraightdraw and overcards >= 1 and random <= 25 raisemax force

When Usersixpack and havetrips and raises <= 1 raisepot force


turn
When Usersixpack and paironflop and not (nobettingonflop or calledonflop or board = AA or board = KK) and opponents = 1 and position = first and bets = 0 and raises = 0 and random <= 66 userturncr

When Usersixpack and userturncr and bets = 0 and raises = 0 call force

When Usersixpack and userturncr and bets = 1 and raises = 0 raise 120% force

When Usersixpack and usercr and not (nobettingonflop or calledonflop or opponents > 1 or bets = 1 or raises >= 1) and not (suitsonflop = 2 and flushpossible and board = A) and random <= 50 bet 60% force

When Usersixpack and havetrips and not (flushpossible or straightpossible) and raises <= 1 raisepot force

 

river
When Usersixpack and nobettingonturn and opponents = 1 and bets = 0 and raises = 0 and potsize < 15% stacksize and (not havepair) and random <= 50 bet 52% force
« Last Edit: October 23, 2014, 05:12:27 AM by Egor » Logged

My life is a "missed click restoring state"
Egor
Forum Admin
Extreme Botter
*****

Karma: 361
Posts: 33703



WWW
« Reply #26 on: October 23, 2014, 05:10:11 AM »

Version 2 now posted at www.bonusbots.com/6pack.txt

Change Log

» Corrected flop check-raise error (as pointed out by Mrphil above) that caused us to make random detrimental calls

» Adopted MrPhil's preflop hand division (moving some of the weaker open-raising hands to the button+ position)

» Reduced checking from first position frequency from 35 to 33% but increased the check-raise frequency from 50% to 60%

» Reduced reraise-from-late-position frequency to 40% from 65% (I agree with MrPhil on reducing the frequency but not all
the way down to 25% as in his version)

Please note that my version has no option settings saved so you can sit-out however you prefer (I prefer never to, and this
profile loves heads up play). Also, the flop calling error that has now been fixed was huge. I was doing okay with
version 1 in spite of that, so am optimistic of version 2!

Thanks for the help MrPhil!  bowdown
Logged

Please do not PM me about license issues or help stuff - email me or use the Help board. Thanks! -Egor
Mrphil
Extreme Botter
*****

Karma: 70
Posts: 1957


full limit = rakemaker


« Reply #27 on: October 23, 2014, 05:39:31 AM »

Nice version update. I see you prefer to keep the preflop reraising hands to stay the same and just lessen the "random" variable. I can agree with that.

The user variable I added was mostly due to people wanting to tighten up above XXX big blinds, so I thought it would make it easier.
I understand if you want to keep this a strict one dimensional profile as originally intended.

Now comes the hard part of finding additional improvements.
It will take some hand grinding and checking through bot logs and Holdem manager logs to find some additional edge at this point.

Really happy with what I'm seeing so far though. I only wish that I wasn't getting the reraise issues on blackchip that I reported in the help section (this kills my winrate, but even with this error, I STILL am positive overall with this profile).

I wasn't expecting much of 6-pack when I first started it given the amount of code, but it is enough to turn doodle into a pushy little 6 man punk (in a good way). My only complaint, which is actually good, is that I ABSOLUTELY HATE people that play 6-pack style when I'm playing real life on tables. I like to watch the bot with 6-pack and imagine how many times the opponents are doing this  banghead  ...  smash

Thank you for creating this Egor  bowdown



Logged

My life is a "missed click restoring state"
Poker8
Global Moderator
Serious Botter
*****

Karma: 30
Posts: 671

Shanky Bonus Bots Rock!


WWW
« Reply #28 on: October 23, 2014, 07:01:05 AM »

OK, Thoughts on below:

Shanky Technologies Holdem Version 7.5.9: Hand: As Ah
Players = 4 have AA
Raise
hands played in session = 14
in timer: players = 4, folds in game= 0, raises = 1, checks = 0, calls = 1, bets = 0, folds = 0
casino = Bodog 6 Max, game = No Limit Cash, BB = 0.05, Pot = 5 BBs, Stack = 2.63, TI = 0 BBs
In Button
Default Profile: "Doodle 104", Action = raisepot force
Matching user defined condition at line 66, Action = call force
clicking Call
Flop: 2s 3c 2c
Board: pair with 2 suits
have best possible overpair
also board pair < 77
in timer: players = 5, folds in game= 1, raises = 1, checks = 2, calls = 0, bets = 1, folds = 0
casino = Bodog 6 Max, game = No Limit Cash, BB = 0.05, Pot = 27 BBs, Stack = 2.53, TI = 2 BBs
opponents = 4, position = last
Play if no Raises but Bet in last position and call one raise
folding because of post flop fold paired option setting
Fold
clicking Fold

Here is the code that directed the call. The raise was a min raise.
When raises = 1 and amounttocall <= 4 and stilltoact <= 3 and (pairinhand or hand = A suited or hand = KQ or hand = K9 suited or hand = K8 suited or hand = K7 suited or hand = Q9 suited or hand = Q8 suited or hand = JT or hand = J9 suited or hand = J8 suited or hand = J7 suited or hand = T9 or hand = 98 or hand = 97 suited or hand = 96 suited or hand = 87 or hand = 86 suited or hand = 85 suited or hand = 76 or hand = 75 suited or hand = 65 or hand = 64 suited or hand = 54 suited) call force

I think we should have re-raised to clear the field down before the flop.
Logged
Egor
Forum Admin
Extreme Botter
*****

Karma: 361
Posts: 33703



WWW
« Reply #29 on: October 23, 2014, 07:53:41 AM »

I must agree with you there and I see a problem now in reducing the reraise random variable to 40% without separating out some stronger hands as MrPhil suggested.

I do want to just call sometimes with AA/KK when an opponent raises because I want to wake up with hands they don't expect sometimes post-flop. However I want that % to be small and never when calls >= 1 like in this case.

Let me see what I can do....
Logged

Please do not PM me about license issues or help stuff - email me or use the Help board. Thanks! -Egor
Egor
Forum Admin
Extreme Botter
*****

Karma: 361
Posts: 33703



WWW
« Reply #30 on: October 23, 2014, 08:06:13 AM »

Version 3 now posted at www.bonusbots.com/6pack.txt

Change Log

» Preflop when acting late and raises = 1 and calls >=1 and we hold AA/KK/QQ/AK we now always reraise, 80% just like when we're weaker

» Same situation but calls = 0 we make the same reraise but 80% of the time. That leaves us 20% of the time to surprise our single open-raising opponent with a strong holding they don't expect us to have.

I think this is an important improvement. Thanks to Poker8  thumbsup
Logged

Please do not PM me about license issues or help stuff - email me or use the Help board. Thanks! -Egor
Egor
Forum Admin
Extreme Botter
*****

Karma: 361
Posts: 33703



WWW
« Reply #31 on: October 23, 2014, 08:10:03 AM »

Actually it will be a lot less than 20% of the time we call a preflop raise against a single preflop open-raiser with AA/KK/QQ/AK because we then have to beat a 40% random gauntlet. So 20% x 60% means we'll only do it 12% of the time. That still sounds okay to me.
Logged

Please do not PM me about license issues or help stuff - email me or use the Help board. Thanks! -Egor
Poker8
Global Moderator
Serious Botter
*****

Karma: 30
Posts: 671

Shanky Bonus Bots Rock!


WWW
« Reply #32 on: October 23, 2014, 11:19:47 AM »

Thanks Egor, I'll give it another shot tonight! boxing
Logged
Mrphil
Extreme Botter
*****

Karma: 70
Posts: 1957


full limit = rakemaker


« Reply #33 on: October 23, 2014, 02:06:00 PM »

Uhhh Egor, unless my phone has gone wonky, i think you accidently reposted the original version (without any fixes and big hole on flop)
Logged

My life is a "missed click restoring state"
Egor
Forum Admin
Extreme Botter
*****

Karma: 361
Posts: 33703



WWW
« Reply #34 on: October 23, 2014, 05:47:28 PM »

your phone must be wonky -- the correct profile states version 3 at the top
Logged

Please do not PM me about license issues or help stuff - email me or use the Help board. Thanks! -Egor
Mrphil
Extreme Botter
*****

Karma: 70
Posts: 1957


full limit = rakemaker


« Reply #35 on: October 23, 2014, 07:12:51 PM »

your phone must be wonky -- the correct profile states version 3 at the top
My mistake. My phone had the old page cached (even when refreshing the browser). Sorry  bowdown
Logged

My life is a "missed click restoring state"
Egor
Forum Admin
Extreme Botter
*****

Karma: 361
Posts: 33703



WWW
« Reply #36 on: October 23, 2014, 07:32:13 PM »

Let's keep this going guys. I'm all for a few more tweaks -- if you can find good ones.  beer
Logged

Please do not PM me about license issues or help stuff - email me or use the Help board. Thanks! -Egor
Mrphil
Extreme Botter
*****

Karma: 70
Posts: 1957


full limit = rakemaker


« Reply #37 on: October 24, 2014, 01:34:03 AM »

Shouldn't we at least call this if not reraise in 6 man from BB to this small of a raise:
(Profile was loaded and doodle backup)
Code:
Shanky Technologies Holdem Version 7.6.4: Hand: Th Ad
Players = 5 have AT
Fold if any raise, raise if folds and no calls else call
Defend Big Blind
hands played in session = 6
in timer: players = 5, folds in game= 0, raises = 1, checks = 1, calls = 1, bets = 0, folds = 0
casino =  *Redacted*, game = No Limit Cash, BB = 0.02, Pot = 8 BBs, Stack = 2.12, TI = 1 BBs
In Big Blind
corrected folds = 2
Fold if any raise, raise if folds and no calls else call
Defend Big Blind
Fold
clicking Fold
« Last Edit: November 03, 2014, 09:12:49 PM by Mrphil » Logged

My life is a "missed click restoring state"
Egor
Forum Admin
Extreme Botter
*****

Karma: 361
Posts: 33703



WWW
« Reply #38 on: October 24, 2014, 03:22:42 AM »

Pot = 8 BB?

That looks like a big raise.
Logged

Please do not PM me about license issues or help stuff - email me or use the Help board. Thanks! -Egor
Mrphil
Extreme Botter
*****

Karma: 70
Posts: 1957


full limit = rakemaker


« Reply #39 on: October 24, 2014, 03:25:39 AM »

Pot = 8 BB?

That looks like a big raise.
No. It was a raise and then a call. I was watching it live.
Logged

My life is a "missed click restoring state"
Pages: 1 [2] 3 4 ... 15 Print 
Shanky Technologies Poker Bot Support Forum  |  General Category  |  Working Profiles (Moderator: sngbot)  |  Topic: Egor's 6-pack profile
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!