aboutsummaryrefslogtreecommitdiff
path: root/advtrains/trainhud.lua
diff options
context:
space:
mode:
authorTanavit <tanavit@posto.ovh>2025-03-26 10:57:05 +0100
committerorwell <orwell@bleipb.de>2025-04-08 21:27:06 +0200
commitc08896f9f5cccc08f49f14944c1a9c0c8c0b5796 (patch)
treeaca2a5934fe70290cdffe3eda8e8a4ff67afc671 /advtrains/trainhud.lua
parent923850523d2aa510a6258585af9e7c0a2c949eaa (diff)
downloadadvtrains-c08896f9f5cccc08f49f14944c1a9c0c8c0b5796.tar.gz
advtrains-c08896f9f5cccc08f49f14944c1a9c0c8c0b5796.tar.bz2
advtrains-c08896f9f5cccc08f49f14944c1a9c0c8c0b5796.zip
Translations improvement.
File : - advtrains : init.lua wagons.lua - advtrains_line_automation : scheduler.lua stoprail.lua Actions : - Conversion of attrans() to S() - Insertion of S() function calls where needed. Miscellaneous : - Removing of personnal tries on update-translastions.sh which should not have been committed. # Third and last patch of a serie of three to be applied to the master branch of advtrains on commit #0b7fdc6 # # ATTENTION : # # 1. These patches come from a derivation of the l10n branch which, afaik, is not yet merged in the master branch. # I guess that applying these patches will shortcut the l10n branch. # 2. These patches contain translations strings of for the modification I proposed some month ago for basic_trains which, # afaik, are not yet merged in its master branch.
Diffstat (limited to 'advtrains/trainhud.lua')
0 files changed, 0 insertions, 0 deletions
hl str"> **Usage:** `/xtempban <player_or_ip> <time> <reason>` The `time` parameter is a string in the format `<count><unit>` where `<unit>` is one of `s` for seconds, `m` for minutes, `h` for hours, `D` for days, `W` for weeks, `M` for months, or `Y` for years. If the unit is omitted, it is assumed to mean seconds. For example, `42s` means 42 seconds, `1337m` 1337 minutes, and so on. You can chain more than one such group and they will add up. For example, `1Y3M3D7h` will ban for 1 year, 3 months, 3 days and 7 hours. **Example:** `/xtempban Joe 3600 Some reason.` ### `xunban` Unbans a player. **Usage:** `/xunban <player_or_ip>` **Example:** `/xunban Joe` ### `xban_record` Shows the ban record on chat. **Usage:** `/xban_record <player_or_ip>` This prints one ban entry per line, with the time the ban came into effect, the expiration time (if applicable), the reason, and the source of the ban. The record is printed to chat with one entry per line. **Example:** `/xban_record Joe` ### `xban_wl` Manages the whitelist. **Usage:** `/xban_wl (add|del|get) <player_or_ip>` Whitelisted players are allowed on the server even if it's otherwise marked as banned. This is useful to only allow certain users from shared computers, for example. The `add` subcommand adds the player to the whitelist. The `del` subcommand removes the player from the whitelist. The `get` subcommand checks if the player is in the whitelist, and prints the status to chat. **Example:** `/xban_record add Jane` ### `xban_gui` Shows a form to consult the database interactively. **Usage:** `/xban_gui` ## Administrator commands The following commands require the `server` privilege, so they are only available to server administrators. ### `xban_dbi` Imports ban entries from other database formats. **Usage:** `/xban_dbi <importer>` The `importer` argument specifies from which database to import. These are the supported import plugins at the time of writing: * `minetest`: Import entries from Minetest's ban list (`ipban.txt`). * `v1`: Old format used by xban (`players.iplist`). * `v2`: Old format used by xban (`players.iplist.v2`). **Example:** `/xban_dbi minetest` ### `xban_cleanup` Removes all non-banned entries from the xban db. **Usage:** `/xban_cleanup`