Summary

Community server owners currently have no way of determining who locked or unlocked a combination lock or which code was used. This makes it unnecessarily difficult to investigate disputes, recover bases after technical issues, and perform moderation on community servers.

Problem

The ADM logs already provide many useful player actions for moderation purposes, and recent additions such as player positions in login/logout events have made them even more valuable.

However, there are currently no log entries when a player interacts with a combination lock.

This means server administrators cannot determine:

• who locked or unlocked a gate,

• when the action happened,

• which code was assigned to the lock.

While PC servers may be able to implement similar functionality through scripting or mods, console community servers rely entirely on the built-in server logs. Without this information, many moderation scenarios require manual investigation or cannot be resolved at all.

Suggested solution

Add ADM log entries whenever a player locks or unlocks a combination lock.

For example:

23:29:51 | Player "<username>" (id=<player uid> pos=<player position>) opened CombinationLock4 on Fence with code 1234
23:29:51 | Player "<username>" (id=<player uid> pos=<player position>) locked CombinationLock4 on Fence with code 4321

The exact wording is not important, but the log should include:

• the player,

• the time,

• the position,

• the lock type,

• whether it was locked or unlocked,

• and the resulting code.

Benefits

This information would greatly improve moderation on community servers by allowing administrators to:

• investigate base access disputes,

• recover lock codes after technical issues,

• verify player reports,

• and build better moderation and automation tools.

Since console servers cannot rely on custom scripting, having this information available directly in the ADM logs would significantly improve administration capabilities.

1. Place a fence with a combination lock.

2. Lock or unlock the combination lock.

3. Check the ADM log file.

4. Observe that no log entry is generated for the interaction.

Locking and unlocking a combination lock should generate an ADM log entry containing the player, timestamp, position, lock type, action (lock/unlock) and the resulting combination code.