Join the Game4Freak Discord Get exclusive plugin sneak peeks, talk directly with VisEntities, never miss important updates, and unlock special discount codes!

Solved Entities Not Visible After Spawning at Monument

Return to plugin
laimin

laimin

Customer
Hello. I’m experiencing a serious issue when players respawn at monuments using your plugin.

The problem only happens when a player spawns directly at a monument through Monument Spawns. After respawning, parts of the monument are not properly loaded on the client side. For example, loot crates, recycler, doors, or other entities may not appear visually. The player can see the ground as empty, but in reality objects exist there.

In some cases the player is also slightly rubber-banded or teleported back a short distance after spawning.

Important:
If the same player walks to the monument normally (without spawning there), everything loads correctly and there are no missing entities.

So the issue seems to be related specifically to the respawn-at-monument process, not the monument itself.

There are no console errors and no anti-cheat violations. The server is stable and this does not happen with normal movement — only when spawning directly at the monument.

This creates gameplay issues because players cannot see loot containers or interact with objects properly until they leave and return or reconnect.

Could you please check if the respawn logic might be causing incomplete network entity loading or snapshot issues after spawning?
 
Recent First Highest Voted
VisEntities said:
Pushed an update. It looks fixed on my end, but please test and confirm
Click to expand...
I normally would not write unless there was a serious issue, but after updating Monument Spawns 1.0.1 I encountered two critical problems.

After the update, about half of the monuments defined in the config are no longer being read. They do not appear on the respawn screen and no sleeping bags are created for them. The config structure has not been changed on my side.

Much more serious issue: approximately 7 minutes after loading the plugin on a live server (around 30 players online), the server completely froze. The game server stopped responding entirely — even the Pterodactyl console became unresponsive. No commands could be executed and the process had to be forcefully restarted.

This behavior has now happened repeatedly, and only occurs when Monument Spawns 1.0.1 is installed. Without the plugin, the server remains stable.

The hosting hardware is more than sufficient (handles 150+ players during peak hours), so this does not appear to be a performance limitation issue.

Please investigate potential entity/network handling or monument parsing issues introduced in 1.0.1, as this is causing full server lockups.
But loading prefabs is solved
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart

Cart

Total -