miniMe_rust

Dears, maybe this is a stupid question, but I wonder whether it is the game itself, another random plugin (like e.g. BoxLooters) or Raidable Bases which is causing this console spam: [BoxLooters] Saved Boxlooters data ... more lines before ... Entity is NULL but is still in saveList - not destroyed properly? m249.entity Entity is NULL but is still in saveList - not destroyed properly? ak47u.entity Entity is NULL but is still in saveList - not destroyed properly? ak47u.entity ... more lines after ... Saved 99,591 ents, cache(0.32), write(0.07), disk(0.06). Saving complete My observation is, that it must be somehow related to Raidable Bases. I am running 2 PvE servers where one has the Raidable Bases plugin, the other one not. Both servers use the BoxLooters plugin. Only on my server with the Raidable Bases plugin I see this kind of console spam. This console spam appears to be triggered every time BoxLooters saves. A while ago nivex added the "/rb savefix" feature which appears to solve relieve the issue, but sadly does not solve the underlying problem since only a few minutes later the same console spam shows again. Hence the savefix appears to be cosmetics to reduce the noise in the console. Is there already any insight, or are we still treating symptoms without knowing the root cause? Thanks in advance for sharing your thoughts, and to nivex for this great plugin. Update 2024-10-21: I received a warning from Codefling for nothing - seems like somebody didn't like the comment above.

Will this plugin need to be updated for the September force wipe? I see a lot of plugin updates being pushed with the remark "will only compile after installing the September update" due to the changed pooling.

Honestly I don't get what you're trying to achieve here. In my eyes you can use the plugin on your PvE server and don't use it on PvP, but I don't see your point where permissions would make any sense. You probably meant to ask for some configuration to set, so that in PvP players can more easy take over a monument, like configure what happens when a player kills the current owner of a monument. Since you didn't get a response yet, I assume I'm not the only one having problems with understanding your use case. It might make sense to elaborate a bit, or make a ticket in the author's Discord.

This plugin does exactly as it says - threw it into my 3000 worldsize server and since then have a Travelling Vendor. Keep up the great work guys! Cheers!

Hi @golgolakk, this looks like a good idea - even though I'd rather lean towards the way rustmaps.com handles map sizes on their URLs. Use of comma as a size/seed separator might have side effects - rustmaps is using an underscore _ to separate. Since this plugin overrides whichever seed you may have set in your server config, it should also be able to override which ever world size you have configured. However, I can't speak for the developer, but I think that's a good idea. Would be great to have that as a feature.

You can disable map markers by editing the config files for each zone in oxide/data/MM_Data/MonumentOwner (subfolders Events or Monuments). Look for this section in the *.json files and change according to whether you want markers to be shown or not: "Display settings": { "Enable the display of the radius of the zone on the map": true, "Enable the display of the zone marker on the map": true, "The position of the marker relative to the position of the monument": "(0, 0, 0)", "The text that will be displayed in the marker": "Owner:" },

Highly recommended purchase! I run 3 servers in total, 2 of which are PvE, and needed a solution to handle which player can claim and loot which monument at which time. Problem here - you get new players trickle in who don't care or don't read or understand server rules, and then just loot whatever entertains them. A constant source of frustration for your fellow server residents and a bad situation for the server owner / admin, who has to enforce server rules. First started with the "Monument Lock" plugin, also available here on Codefling. Loved it, but eventually got errors with it and had to learn that there was no help or (timely) reaction from the plugin author. Can't blame the author, that plugin is free and you can't expect more than best effort. I moved on and found "Monument Owner" which was the "one size fits all" solution for my needs. Configurable cooldown, lootables are really protected, clear zones and map markers with info on the in-game map, adjustable zone sizes and so much more. Players love it! In contrast to other plugins I bought here on Codefling I found @jtedal to be a very active author, even though we had a bumpy start. jtedal not only rewrote the entire plugin which led to the 1.5.x series of updates, he also reacted extremely fast to bug reports and pushed updates and improvements. This is far above the usual standard you get elsewhere and adds to what I call outstanding user experience. So, what makes this plugin stand out? highly configurable monument zones. Config files are mostly self-explanatory wide range of possibilities to lock a monument to a player. I like it simple and want my players to easily claim a monument, but you can make it as challenging as you want, like set a higher score to reach, or let players fulfill tasks e.g. open a security door with a card possibility to set (or disable) cooldowns, so that not a single player blocks a monument all the time and others get a chance you can enable or disable zones as you like - maybe disable monuments like Excavator, and have that handled with another plugin Monument Owner plays nicely together with both, TruePVE and SimplePVE active plugin developer who listens to users Final thoughts: In a perfect world there exists no such things as software bugs. However, reality is a beast, and plugins sit on top of the code Facepunch puts into Rust, known for ... debatable quality, and changes in the game can (and will) break plugins partially or entirely. Let alone there can be bugs in the plugin which need to be addressed. If you encounter any bugs it is key not to wait for a miracle to happen, or to think "somebody else will report it". While that may be true, you can actively help find a timely and good response on any bugs. Thanks to jtedal I learned that a short video clip depicting the error holds much more value than a text of any length, as a video can speak for itself. The solution - an update with the bugfix - came almost instantaneously which deeply impressed me. Highly recommended purchase! Thanks again for a great plugin and all the hard work. Love your plugin!

Hi @kasvoton, would it be possible to add support for "Travelling Vendors"? In July-2024 update notes (rust.facepunch.com/news/road-renegades) it says that the "Travelling Vendor" spawns if there is a ring road present on the map, which should be the case on maps >= 4000. However, most of us use your excellent Harmony plugin to enrich our maps with surface train rails, even though map size would be too small. It would be awesome if you could update (or make another paid plugin) so that we also get a ring road. server.worldsize server.worldsize: "3750" travellingvendor.startevent Can't spawn Travelling Vendor: No roads available to spawn on. Failed to spawn Travelling Vendor. I wonder if we can trick the "Travelling Vendor" to spawn if we manage to get a ring road. Thanks in advance for looking.