XMJ(6)

📦

version 1.17.2 · 3 versions

1.17.2 · debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
1.16 · ubuntu noble
1.11 · debian bookworm, ubuntu jammy

, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

🀄 XMJ 💖 — the `xmj`, `mj-server`, `mj-player` era

ok bestie so this is section 6 of the Games Manual and it's literally about playing Mah-Jong on your computer, no cap 🀄✨

🌸 NAME 🌸

xmj, mj-server, mj-player — the little trio of programs you need to play Mah-Jong 💅

✨ SYNOPSIS ✨

ok so here's the whole vibe of how you actually call these things, copy-paste exact bestie:

xmj [--id idnumber]
         [--server address]
         [--name playername]
         [--connect]
         [--show-wall | --no-show-wall]
         [--size N]
         [--animate | --no-animate]
         [--tileset directory]
         [--tileset-path directory-path]
         [--dialogs-popup | --dialogs-below | --dialogs-central]
         [--use-system-gtkrc | --no-use-system-gtkrc]
         [--gtk2-rcfile file]
         [--echo-server]
         [--pass-stdin]
         [--monitor]

mj-server [--server address]  [--timeout seconds]
         [--pause deciseconds]
         [--random-seats | --id-order-seats]
         [--disconnect-penalties N1,N2,N3]
         [--end-on-disconnect]
         [--exit-on-disconnect]
         [--save-on-exit]
         [--option-file file]
         [--load-game file]
         [--no-id-required]
         [--no-manager]
         [--auth-basic id:password]*4
         [--debug]
         [--logfile file]
         [--no-special-scores]
         [--seed N]
         [--wallfile file]
         [--hand-history]
         [--nohist]

mj-player [--id idnumber] [--name playername]
         [--server address] [--password password]
         [strategy options]

💜 DESCRIPTION 💜

So basically it's a set of three programs that let you play Mah-Jong on Unix systems — against actual people or against programs — over the Internet 🌈 iconic.

mj-server — this is the main character fr fr 👑 It's the program that handles communications and control of the game; the rules and the scoring are enforced right there. Players, human or computer, connect to a server via the network.
mj-player — a computer player 🦋 At present it's fairly simplistic, ngl: it's only got offensive tactics and literally no knowledge of defensive play 💀
xmj — the X client, for the human players (that's us, bestie) 🫶

🎀 QUICK START 🎀

ok if you're not tryna read this whole long document (respect, but also 😭):

To start a game against three computer players: start xmj, select "New local game..." from the "Game" menu, and click "Start Game". (Wait about ten seconds for everything to start up.)

periodt. that's it. go slay ✨

🌟 OPTIONS 🌟

🌈 All Programs

--server address — tells you the network address to listen on (if you're mj-server) or to connect to (if you're mj-player or xmj) 💫 If address contains a colon, it means an Internet socket, and it should look like host:port. If address has no colon, it gets interpreted as a Unix file name and a Unix socket is used instead. The default value for address is localhost:5000. Also, address can be set in a dialog box inside xmj 🎀

💖 xmj and mj-player

--id idnumber — the server hands out a unique integer ID to each player (currently just 1 to 4, in order of connection). You should quote this ID when you're reconnecting to a game already in progress — like after losing your network connection, or after you accidentally killed xmj 🙈 The default ID is 0, which means no pre-assigned ID.
--name name — players can give themselves names, and client programs will use them. This option is how you specify that name 💅 For xmj, the default is the value of the environment variable LOGNAME, or if that fails, the username of the logged-in user. For mj-player, the default is "Robot(PID)" where PID is the process id 🤖

🦋 xmj

--connect — by default xmj does not automatically connect to a server, it just waits for you to connect via a menu. Give this option and xmj connects immediately ⚡
--show-wall, --no-show-wall — tells xmj (not) to display the wall 🧱 By default the wall is shown only if you're running on a big enough screen. This option is also controllable via the Display Options preference panel.
--size number — adjusts the size of the main window 🪟 Think of it as the length of a tile rack, measured in tiles. The default — and the largest value accepted — is 19, or 18 if you're on an 800x600 display. The smallest usable value is 14. Also controllable via the Display Options preference panel.

heads up bestie: if the --show-wall option is given, a --size smaller than 19 will have no effect 😭

--animate, --no-animate — switches animation on (off) ✨ Not every tile movement is animated though: only the ones that involve moving tiles to or from a hand from outside. Also controllable via the Display Options preference panel.
--tileset directory — xmj needs pixmaps to display the tiles and the tong box, and this option tells it which directory to find them in 🎨 The default is set at compilation time; the default default is to use the compiled-in tiles 💅
--tileset-path directory-path — gives a colon-separated (or semicolon-separated under Microsoft Windows) list of directories to look in for the directory named by the --tileset option 🔍
--dialogs-popup — by default, most of the dialog boxes for player actions are part of the main window. Use this option and they instead appear as separate transient windows 🪟✨
--dialogs-below — by default, dialog boxes appear in the centre of the table. Give this option and dialogs (apart from some popups) get positioned below the table area. Also: "Please let me know which style you prefer!" 🥺
--dialogs-central — the default: dialog boxes appear in the middle of the table. These options are also controllable via the Display Options preference panel.
--gtk2-rcfile file — if xmj is compiled with GTK+2, this option specifies a GTK rc file to use instead of the program's compiled-in style file. You can use it to change how the program looks 👑 See the description under the Display Options... panel for more details. The file should be an absolute filename; if it's relative, it'll be sought in the current directory (Unix) or the program directory (Windows). Also controllable via the Display Options preference panel.
--use-system-gtkrc, --no-use-system-gtkrc — when xmj is compiled with GTK+2, by default it ignores the system-provided settings, to keep behaviour consistent across systems 🌍 If you want it to use your system settings, set this option. Also controllable via the Display Options preference panel.
--echo-server — with this, xmj will echo to stdout all the protocol messages received from the server. This option is for use in debugging 🔧
--pass-stdin — with this, xmj will send any text given on stdin to the server. This option is for use in debugging 🔧
--monitor — with this, xmj will send requests to the server only in direct response to user actions; it takes no action itself (and hence all auto-declaring and playing is also disabled). This option is for use in debugging 🔧

👑 mj-server

--timeout seconds — when a discard is made, there's a limit on how long players have to claim it ⏳ This option sets that timeout; a value of 0 disables it. The default is 15 seconds. This value can also be set via a GameOption request from a player.
--pause deciseconds — makes the server enforce a delay of deciseconds/10 seconds between each action in the game 🐢 The purpose is to slow programmed players down to human speed (or, in a teaching situation, to slow the game down even more). The current server considers 50 (i.e. 5 seconds) to be the maximum reasonable value for this option. The option can also be requested by players, via a PlayerOption protocol request.
--random-seats — by default, players are seated in order of connection to the server. This option seats them randomly 🎲 It will become the default later.
--id-order-seats — this makes players be seated in numerical order of their ids. It's used by the xmj program to make the New local game.. work as expected 💅
--disconnect-penalties N1,N2,N3 — specifies the penalties applied by the following option, for players who disconnect before the end of a game 😬 N1 is the penalty for disconnecting in the middle of a hand; N2 at the end of a hand but in the middle of a round; N3 at the end of a round (other than end of game). They all default to 0 if not specified.
--end-on-disconnect — if given, a disconnection by one player will gracefully terminate the game 🫠 Mid-hand, the hand is declared a wash-out; after Mah-Jong has been declared, then if a losing player disconnects, their tiles are shown, the hand is scored, and then the game ends; if a winning player disconnects, the hand is a wash-out. The disconnecting player may be assigned a penalty, according to the --disconnect-penalties option, which will be included in the scores printed out by the server. (The penalties will not be visible to the other players.)
--exit-on-disconnect — if given, the server will quit if any player disconnects, instead of waiting indefinitely for reconnection 💀
--save-on-exit — if given, the server will save the state of the game if it quits as a result of a player disconnecting. (It will not save the state if it quits as the result of an internal error.)
--option-file file — names a file of protocol commands which get applied to every game when it starts 📄 Its main purpose is to set non-default game options, via the GameOption protocol message (note that this is a CMsg, not a PMsg). However, users will normally set options and preferences via the xmj control panel, not by this means.
--load-game file — names a file containing a saved game (as a suitable sequence of protocol commands) 💾 The server will load the game; clients connecting will be treated as if they had disconnected and rejoined the game.

more coming, bestie — don't go anywhere 🫶

--no-id-required — okay so picture the most common resume-a-saved-game scenario: one human vs three robots 💀 and the robots come back with totally different names or ids than the robots in the original game had. This option tells the server: bestie, if you can't match a reconnecting player by id or by name, just go ahead and match it to one of the previously disconnected players anyway. (In that case the human normally connects first with the same name, so the human gets matched correctly, no drama. 🫶)
--no-manager — usually the first player to connect becomes the game manager and can change all the game settings. Give this option and nobody gets to change the game settings. Not even them. Periodt. 🚫
--auth-basic id:password — this hands you basic authorization, which is insecure, because the password is transmitted in plaintext 😭. The player with id id must give the specified password to connect. Big note: if you give this argument, you have to give it four times, once for each authorized player — any player id you don't mention will not be allowed to connect. Want someone to connect with no password? Make password empty. Easy. ✨
--debug — turns on various debugging features. In particular, it enables protocol commands that allow one to change the tiles in a hand...
--logfile file — the server will write a complete record of the game to file; it's gonna be quite large, and it's only useful for automatic comparison of different computer players.
--no-special-scores — suppresses the scoring of points and doubles for flowers and seasons. It's primarily intended for running tests of different players; for human use, a game option will be provided to eliminate the specials altogether. 🌸
--seed n — specifies the seed for the random number functions. Used for repeatable tests. 🔁
--wallfile file — names a file containing space separated tile codes giving the wall; used for repeatable tests. (This is a testing option; it is not robust. 🙈)
--hand-history — an option to facilitate certain automatic analyses; if set, a history of each hand is dumped to the file hand-NN.mjs.
--nohist — another option only used in automatic comparison: it saves some CPU time by disabling the book-keeping required to allow players to disconnect and reconnect. ⚡

🧚 mj-player 🧚

--password password — sets the password if basic authorization is in use. 🔐

💅 strategy options 💅

The player has some options you can use to change its "personality" 👑. The meanings are rather approximate, since they actually change parameters which are used in a rather complex way, but the idea is right. These options, each of which takes a floating point value in the given range, are:

--randomness 0.0 .. 1.0 — the most generally useful option: adds random noise to the player's choice calculations, thus reducing its skill level. Values above 1.0 are possible, but don't seem to make matters worse. And no, the dumbed-down players are still not stupid. 😌
--chowness -1.0 .. 1.0 — this affects how much the player likes chows: at 1.0, it will go all out for the chicken hand, at -1.0 it will never chow. The default is 0.0.
--hiddenness 0.0 .. 1.0 — increasing this makes the player reluctant to make exposed sets. At 1.0, it will never claim (except possibly to go mah-jong). The default is 0.0.
--majorness 0.0 .. 1.0 — increasing this biases the player towards collecting major tiles. At 1.0, it will discard all minor tiles, if possible. The default is 0.0.
--suitness 0.0 .. 1.0 — increasing this makes the player try to go for one-suit hands. The default is 0.0

In practice, the --majorness option seems not to be very useful, but the other options change the personality without completely destroying the playing ability. 🎀

In fact, all these options take a comma-separated list of values, which allows the specifications of a set of strategies, which the player will switch between. In this case, the --hysteresis hhh option specifies how much better a strategy should be to switch to it. However, use of this option, and multiple strategies, is probably only useful if you first read the code to see how it works. 👀

🌈 USING THE XMJ PROGRAM 🌈

The main window contains a menu-bar and a table area; the table is in a tasteful shade of dark green. 🟢 The table displays a stylized version of the game: stylized in that there is no jazzy graphics or perspective, and the tiles are not intended to be pictures of real objects, and so on. Otherwise, the layout is as one would expect of a real game. However, the wall may or may not be displayed, depending on option settings and screen size. (See above.)

Specifically, the four players are arranged around the four edges of the table, with "us" at the bottom. For each player, the concealed tiles are displayed nearest the edge of the table; our own tiles are visible, the other players' tiles are face-down. The rightmost concealed tile of other players is highlighted in red when it is their turn to discard. 🔥

In front of the concealed tiles are (to the player's left) any declared sets, and (to the player's right) flowers and seasons, and the tong box if the player is East. The tong box displays the wind of the round in a white circle. If necessary, the flowers and seasons will overflow into the concealed row. 🌸

The discards are displayed face-up in the middle of the board: they are laid down in order by each player, in the natural orientation. TODO: add options to display discards randomly, or face-down. If animation (see --animate option) is not being used, then the most recent discard will be highlighted in red.

The name of a face-up tile can be displayed by right-clicking in the tile. Alternatively, the Tiletips display option can be set, in which case the name of a tile is displayed whenever the mouse enters it. 🖱️

Our tiles are displayed in sorted order, which happens to be Bamboos (1-9), Characters (1-9), Circles (1-9), Winds (ESWN), Dragons (RWG), Flowers, Seasons. We can also arrange the tiles ourselves — see the "Sort tiles in hand" display preference described below. ✨

Actions are generally carried out by clicking a button in a dialog box that appears in the middle of the board. For many actions, a tile must be selected. A tile is selected or unselected by single-clicking it; when selected, it appears as a depressed button. The program will generally pre-select a sensible tile: specifically:

during the initial declaration of special tiles, the rightmost special is selected;
after we draw a tile from the wall, the drawn tile is selected;
when declaring concealed sets after going Mah Jong, the first undeclared tile is selected.

To describe the possible actions, let us run through the course of a game. 🎬

First select "New local game..." from the "Game" menu. A panel will appear. The default options are to play a game against the computer, so click "Start Game". After a second or two, a game will start. (NOTE: this assumes correct installation. If this fails, start a server and players manually, and use the "Join server..." menu item.)

The first thing that happens is a dialog box "Ready to start next hand". The server will not start playing a hand until all players have indicated their willingness to continue play. 🫶

Next, the tiles are dealt. Then each player in turn is expected to declare flowers and seasons. When it is our turn, a dialog will appear with the following buttons:

Declare — declare the selected flower or season. (Note: the program auto-selects the rightmost special tile.) If no tile is selected, this finishes declarations. This button will not appear if the game is being played without flowers and seasons.
Kong — if we have a concealed kong, we can declare it now with this button.
Finish — finish declaring specials and kongs.

When all players have finished declaring specials and kongs, a dialog box appears, asking (on East's behalf) permission to continue.

During play, when we draw a tile from the wall, it will be auto-selected. We may also of course select a different tile. A dialog will appear giving us the following possibilities:

Discard — discard the selected tile. This button also serves to declare a flower or season, and the label changes to "Declare" when one is selected.
&Calling — discard the selected tile and declare a calling hand. This button is only shown when calling is allowed (by default, only Original Call is allowed).
Kong — declare a concealed kong of the selected tile, or add the selected tile to an exposed pung, as appropriate. Note: in most rules, a concealed kong can only be declared (or a tile added to an existing pung) immediately after drawing from the wall, but not after claiming somebody else's discard. Up to and including version 1.10, the server enforced this rule strictly. As from version 1.11, it allows a tile to be added to a pung that you have just claimed: in real life, this corresponds to correcting your Pung! claim to a Kong! claim, which is allowed by all rules. (Obscure note: if you are playing the KongHas3Types option, the resulting kong will be counted as annexed, instead of the exposed kong that would have resulted from a genuine change of claim. This is a bug, but not worth the trouble of fixing. 💀)
Mah Jong! — declare Mah Jong! (no selection needed) 👑

If the wall is not being shown, the dialog will note the number of tiles left in the live wall.

A tile can also be discarded simply by double-clicking it. 🖱️

When another player discards, a dialog appears to allow us to claim it. If the dialogs are in the middle of the table, the dialog displays the tile in a position and orientation to indicate the player who discarded; if the dialogs are at the bottom, this is not done, to save space. In any case the dialog displays the name of the tile, and buttons for the possible claims. If the wall is not being shown, the dialog will note the number of tiles left in the live wall. There is also a progress bar which shows how time is running out. ⏳ The buttons use one variant of traditional English terminology, viz:

No claim — we're not claiming this tile, bestie. If there's no timeout in operation, you literally have to click this to indicate a "pass", and either way it's desirable to speed up play. 💨
Chow — claim for a sequence. If our claim is successful and there's more than one possible sequence to be made, a dialog will appear asking us to specify which one. 🀄
Pung — claim for a triplet. ✨
Kong — claim for quadruplet. 💅
Mah Jong! — claim for Mah Jong. If the claim succeeds, a dialog box will appear asking whether we want the tile for "Eyes", "Chow", "Pung", or a "Special Hand" (such as Thirteen Unique Wonders). (The term "Eyes" is used instead of "Pair" so that in the keyboard accelerators, E can be used, leaving P for "Pung".) 👑

When a player (including us) claims, the word "Chow!" etc. will appear (in big letters on a yellow background, by default) for a couple of seconds above the player's tiles.

When all players have claimed, or timed out, the successful claim is implemented; no additional announcement is made of this.

If a player adds a tile to an exposed pung, and that tile would give us Mah Jong, then a dialog box pops up to ask whether we wish to rob the kong.

After somebody goes Mah Jong, we are asked to declare our concealed sets. A dialog appears with buttons for "Eyes", "Chow", "Pung". To declare a set, select a tile, which must be the first tile in the set for a chow, and click the appropriate button. (If we are going Mah Jong, the first undeclared tile is auto-selected.) When finished, click "Finished" to reveal the remaining tiles to the other players. If we are the winner, there will be a button for "Special Hand": this is used to declare hands of non-standard shape, such as Thirteen Unique Wonders. (Note: the Seven Pairs hand, if in use, should be declared by means of the "Eyes" button, not the "Special Hand" button.)

At this point, a new top-level window appears to display the scoring information. The scoring is done entirely by the server, not by the players; the server sends a text description of the score calculation, and this is displayed for each player in the Scoring window. The information in the Scoring window remains there until the next hand is scored; the window can be brought up at any time via the "Show" menu.

Finally, the "continue with next hand" dialog appears. The hand just completed will remain visible on the table until the next hand starts.

Keyboard Accelerators ⌨️✨

There are keyboard accelerators for all the actions in the course of play. For selecting tiles, the Left and Right arrow keys can be used to move the selection left or right along the row of tiles. In all dialogs, Space or Return will activate the shadowed button, which is usually the commonest choice. Each button can also be activated by typing the underlined letter. (In the Windows GTK1 build, use l (ell) and r instead of Left and Right. The button accelerators do not work, for reasons unknown to me.)

The menus are also accessible via accelerators. To open a menu, press Meta-X (Alt-X on Windows), where X is the underlined letter in the menu name. (Meta-X is often (confusingly) Alt-X on Linux systems.) Then each entry has an underlined letter which if pressed will activate it.

An additional top-level window showing the state of the game can be obtained by selecting "Game info" from the "Show" menu.

A record of the scores so far in the game can be found by selecting "Scoring history" from the "Show" menu. The players are listed in board order, with the original east marked by @. In each hand, the player's hand score appears in parentheses, and then their gain or loss for the hand, beneath which is the running total

There is also a facility for sending text messages to the other players. Select "Messages" from the "Show" menu, and a window will appear: in the top is a display of all messages sent, and below is a single line in which you can enter your message. It will be sent when you hit Return. The message window pops up automatically whenever a message is received, unless prevented by a display preference. If the "Display status and messages in main window" display option is set, then this window will instead appear in the main window, above the table. In that case, there is a checkbox "Keep cursor here" next to the message entry line. Checking this box will ensure that the keyboard focus stays in the message entry field, even when you click on buttons in the game. (Consequently, you will be unable to use keyboard accelerators while this option is checked.)

Starting games and re-connecting 🎮

The "Game" menu has the "New local game..." item to start a new game on your local computer, and the "Join server..." item to connect to an existing game. The dialogs for both these have the following entries:

Checkboxes for Internet/Unix server — These specify whether the server is listening on an Internet socket or a Unix socket. If an Internet (TCP) socket, the host name ("Join Game..." only) and port number should be entered in the appropriate boxes; if a Unix socket, the file name of the socket may be entered, or if it is left blank, a temporary file will be used. These fields are remembered from game to game. 🌐
"Player ID" and "Name" fields — The "Player ID" should be left at 0, unless reconnecting to an existing game, in which case it should be the ID assigned by the server on first connecting to that game. The "Name" field can be anything. When reconnecting to an existing game, if the ID is given as 0, the server will try to use the "Name" to identify the player. (This may not be true in future.) The "Name" field is remembered from game to game. 🆔

The "Join server..." dialog then simply has a "Connect" button to establish the connection. The "New local game..." has the following fields:

For each of three further players — A checkbox to say whether to start a computer player. (Some of) these should be unchecked if you wish other humans to join the games. If checked, there is a text entry to set the players' names, and a text entry field in which options can be given to the players; the latter should only be used if you understand the options! The options are remembered from game to game. 🤖
An "allow disconnection" checkbox — If this is checked, the server that is started will continue to run even if players disconnect. If it is not checked, the server will quit if any player disconnects. If you are playing one against the computer, this should generally be left unchecked, in order to avoid server processes accidentally being left lying around. If playing against people, it should be checked, to allow players to go away, or to guard against network outages. 🔌
As "save game state on exit" checkbox — If this is checked, the server will save the game state (see below on on saving and resuming games) when a player disconnects and causes it to quit. 💾
A "seat players randomly" checkbox — If this is left unchecked, players will be initially seated as East, South, West, North in order of connection. (We always connect first.) If it is checked, the seating will be random. 🎲
A "robot difficulty" numeric entry field — values from 0 to 10 making the robots more skilful. Actually, lower values effectively make the robots a bit tired, so they make mistakes. Beginners probably want 0 to stand a chance of winning sometimes. 🤖
A numeric entry field — to specify the time limit for claiming discards. If set to 0, there will be no time limit. ⏳
A button to start the game — Note that it takes a few seconds to start a game, during which time the dialog stays up with the button pressed. (TODO: fix this!) 🚀

Saving and resuming games 💾

At any time during the play of a game, you can choose the "Save" entry from the "Game" menu. This causes the server to save the current state of the game in a file. The file will be named game-date.mjs by default; if a name has previously been specified, or if the game was resumed from a file, that name will be used. To specify a name, use the "Save as..." entry in the "Game" menu. Note that for security, directories cannot be specified (except by resuming a game), so the file will be created in the working directory of the server.

To resume a saved game, use the "Resume game..." entry from the "Game" menu. This is just like the "New local game..." panel, but it has a box to specify the file containing the saved game. You can either type the file name into the box, or click the "Browse..." button to get a file chooser dialog. (File chooser not available on Windows GTK1 build.)

Setting display and game options ⚙️

The "Options" menu of xmj brings up panels to set various options related to the display and to the game rules. Most of these options can be stored in the preferences file, which is .xmjrc in your home directory on Unix, and xmj.ini in your home (whatever that means) directory on Microsoft Windows.

Display Options 🎨

This panel controls options related to the local display. At the bottom are three buttons: "Save & Apply" applies changes and saves them in the preferences file for future sessions; "Apply (no save)" applies any changes, but does not save them; "Cancel" ignores changes. Note that many display options can also be controlled by command-line arguments; if an option is specified both in the preferences file and on the command line, the command line takes priority.

Position of action dialogs. — This determines where the dialogs for user actions in the game are popped up; see the description of the --dialogs-central etc. options above. This option is stored in the preferences file as

Display DialogPosition posn

where posn is one of "central", "below" or "popup". 🪟

Animation — determines whether tile movements are animated (see the --animate option above). This option is stored in the preferences file as

Display Animate bool

where bool is "0" or "1". 🎞️

Display status and messages in main window — puts the game status and message (chat) windows in the main window, above the table, instead of having separate popup windows. This option is stored in the preferences file as

Display InfoInMain bool

where bool is "0" or "1". 💬

Don't popup scoring/message windows — will prevent the automatic popup of the scoring window at the end of a hand, the message window on the arrival of a message, and the game status window at the end of the game. This option is stored in the preferences file as

Display NoPopups bool