I am a bit new here, but have spent decades in the Backgammon community.
In backgammon it is a game of skill and luck.
The skill is making moves that give the most good moves you can, while at the same time minimizing your opponents good moves.
I have seen it time and time again that players will ...
Search found 22 matches
- Sun Aug 24, 2025 11:22 am
- Forum: Bugs
- Topic: Great effort, but randomness feels questionable
- Replies: 1
- Views: 58
- Sat May 03, 2025 4:50 pm
- Forum: General
- Topic: Lobby Chat
- Replies: 1
- Views: 859
Re: Lobby Chat
Well it works sometimes... I wonder if I have too many connections from a single IP...
- Sat May 03, 2025 1:39 pm
- Forum: General
- Topic: Lobby Chat
- Replies: 1
- Views: 859
Lobby Chat
Programming question, not sure of the best place...
I am running on a test server that does not have user auth enabled.
Does the standard client (On Linux) ignore Lobby messages from Unauthenticated users?
Lobby_msg.png
It is not displayed in the lobby for users in game or not...
Any ideas ...
I am running on a test server that does not have user auth enabled.
Does the standard client (On Linux) ignore Lobby messages from Unauthenticated users?
Lobby_msg.png
It is not displayed in the lobby for users in game or not...
Any ideas ...
- Thu May 01, 2025 10:47 am
- Forum: General
- Topic: pokerth.proto question
- Replies: 0
- Views: 1192
pokerth.proto question
I am working on a bot (yes open source) and have a question about "PlayerResult"
message PlayerResult {
required uint32 playerId = 1;
required uint32 resultCard1 = 2;
required uint32 resultCard2 = 3;
repeated uint32 bestHandPosition = 4 [packed = true];
required uint32 moneyWon = 5;
required ...
message PlayerResult {
required uint32 playerId = 1;
required uint32 resultCard1 = 2;
required uint32 resultCard2 = 3;
repeated uint32 bestHandPosition = 4 [packed = true];
required uint32 moneyWon = 5;
required ...
- Fri Apr 18, 2025 1:26 pm
- Forum: Installation
- Topic: Wireshare DIssector
- Replies: 3
- Views: 7513
Re: Wireshare DIssector
see pull request #445
- Thu Apr 17, 2025 11:28 am
- Forum: Installation
- Topic: Wireshare DIssector
- Replies: 3
- Views: 7513
Re: Wireshare DIssector
Here's the first working version I have.
It has a lot of debug stuff and need clean up but works.
It support message types
-- Dispatcher function table
local MESSAGE_TYPE_ANNOUNCE = 1
local MESSAGE_TYPE_INIT = 2
local MESSAGE_TYPE_INIT_ACK = 6
local MESSAGE_TYPE_PLAYERLIST = 12
local MESSAGE_TYPE ...
It has a lot of debug stuff and need clean up but works.
It support message types
-- Dispatcher function table
local MESSAGE_TYPE_ANNOUNCE = 1
local MESSAGE_TYPE_INIT = 2
local MESSAGE_TYPE_INIT_ACK = 6
local MESSAGE_TYPE_PLAYERLIST = 12
local MESSAGE_TYPE ...
- Mon Apr 14, 2025 11:22 pm
- Forum: Installation
- Topic: Wireshare DIssector
- Replies: 3
- Views: 7513
Re: Wireshare DIssector
I figured it out... need to rework things a bit.
Once I get a the 10 most common messages working i'll do a PR for review
Tom
Once I get a the 10 most common messages working i'll do a PR for review
Tom
- Mon Apr 14, 2025 6:58 pm
- Forum: General
- Topic: header's picture 2
- Replies: 4
- Views: 7257
Re: header's picture 2
And in the era they all came from wouldn't they be all smoking?
- Mon Apr 14, 2025 11:44 am
- Forum: Installation
- Topic: Wireshare DIssector
- Replies: 3
- Views: 7513
Wireshare DIssector
I am working a dissector to parse PokerTH packets and I am seeing some issues with the protoc description and the data
Maybe the protoc spec has changed or the generator I am using is making mistakes...
init_ack (6)
0000 74 ee 2a fb ee cc ae 8b a9 2c a0 16 08 00 45 00
0010 00 52 f3 bd 40 00 33 06 ...
Maybe the protoc spec has changed or the generator I am using is making mistakes...
init_ack (6)
0000 74 ee 2a fb ee cc ae 8b a9 2c a0 16 08 00 45 00
0010 00 52 f3 bd 40 00 33 06 ...
- Sun Apr 13, 2025 8:51 pm
- Forum: Installation
- Topic: testing building connectivity.pro
- Replies: 12
- Views: 9044
Re: testing building connectivity.pro
I get this message
00 00 00 16 08 01 12 12 0a 04 08 05 10 01
12 04 08 01 10 0b 18 00 20 02 28 2f
message AnnounceMessage {
message Version {
required uint32 majorVersion = 1;
required uint32 minorVersion = 2;
}
required Version protocolVersion = 1;
required Version latestGameVersion = 2 ...
00 00 00 16 08 01 12 12 0a 04 08 05 10 01
12 04 08 01 10 0b 18 00 20 02 28 2f
message AnnounceMessage {
message Version {
required uint32 majorVersion = 1;
required uint32 minorVersion = 2;
}
required Version protocolVersion = 1;
required Version latestGameVersion = 2 ...
