Repository navigation
Player info related placeholders
Go back to Placeholders index
| Placeholder | Description | Details |
|---|---|---|
%PTM_firstjoin% |
Displays the current player's first join date | Datetime format can be customized |
%PTM_firstjoin_<nickname>% |
Displays the first join date for a specific player | Datetime format can be customized |
| Placeholder | Description | Details |
|---|---|---|
%PTM_lastseen_<nickname>% |
Displays the last seen date for a specific player | Datetime format can be customized |
%PTM_lastseen_elapsed_<nickname>% |
Displays the elapsed time since a specific player was last seen | Playtime format can be customized |
%PTM_lastseen_elapsed_#_<nickname>% |
Displays the elapsed time since last seen, converted to a specific time unit | Replace # with one of the available time units
|
Error messages are disabled by default. To enable them, set enable-errors to true under the placeholders field in config.yaml.
Cause: The current online player's session could not be resolved when evaluating %PTM_firstjoin% — typically because OnlineUsersManager has no record of them at evaluation time.
Steps to check:
- This should not occur for a player who is actively online. If it persists, check for session management errors in the server logs and contact me on discord.
Cause: An unexpected exception was thrown while retrieving the current online player's first join date.
Steps to check:
- This should not occur under normal conditions. Check the server logs for the underlying exception and contact me on discord.
Cause: An unexpected exception was thrown while retrieving the current online player's join streak — typically because the player's session is null at evaluation time.
Steps to check:
- This should not occur for a player who is actively online. If it persists, check for session management errors in the server logs and contact me on discord.
Cause: No record matching the provided nickname exists in the database.
Steps to check:
- Double-check the spelling and casing of the nickname — it must match exactly as stored.
- Confirm the player has joined the server at least once. Players who have never connected have no database record.
Cause: The player's database record exists but the last_seen field is null. This typically happens for players imported via a database migration, or for players who joined before last-seen tracking was enabled.
Steps to check:
- The field is populated automatically when the player disconnects. Have the affected player join and leave the server once.
Cause: The player's record exists in the database but the first_join field is null. This can occur after a manual database import or migration that did not populate this column.
Steps to check:
- This should not occur for a player who is actively online. If it persists, check for session management errors in the server logs and contact me on discord.
Cause: The plugin found the player's UUID but their data has not yet been fully loaded from the database. This is a transient state that occurs briefly after a player joins.
Steps to check:
- This resolves automatically within a second or two. No action required under normal conditions.
- If the message persists, check for database connection issues or thread pool exhaustion in the server logs.