# How to test a shorter locked crate timer on a Rust server

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Configuration](https://rustsc.com/learn/configuration/index.html.md)

A shorter locked crate timer changes how much time other players have to arrive after the hack starts. Try that encounter on a test world before changing it on a survival server.

## Measure from the start of the hack

Facepunch’s server setup guide shows hackablelockedcrate.requiredhackseconds in server.cfg. Its example value of 600 means ten minutes. Read the value your running server already uses and first test a crate with that value.

Start a fresh hack and record the visible countdown. Have a second player begin at a spot where they often are when an event starts. Check whether they can reach the crate while it is still locked.

## Repeat the encounter with one change

Use the same kind of crate and starting point for the shorter test. Begin a new hack after the new value is active and compare the timer and the second player’s arrival. Keep the crate’s appearance time separate from how long it takes to unlock.

If the change cuts out the part of the encounter you want, keep the original value. If you adopt it, check the game reads the same value after the next start.

## Sources

- [Facepunch server configuration example for the crate hack duration](https://wiki.facepunch.com/rust/Creating-a-server)

## Related resources

- [Why did a Rust setting change back after restart?](https://rustsc.com/learn/configuration/keep-a-rust-setting-after-restart/index.html.md)

---

HTML version: https://rustsc.com/learn/configuration/test-a-rust-locked-crate-hack-timer/
