miniMe_rust

Hey thanks for getting back to me. I had this problem with several players. Already went back to version 1.4.1 which resolved the problem for me. I didn't record any clips. Checking logs from this morning (nightly server restart till I downgraded Monument Owner from 1.5.5 to 1.4.1) I don't see any errors. Hence whatever it is, it happens silently. Monuments locked by a player stay locked. The map markers still said monuments were locked to players with 572 or so seconds left. The player was logged off for hours already. After server restart monuments were still locked to the same players. I attach the relevant part of the logs. Before I went back to 1.4.1 I unloaded version 1.5.5 and deleted all the config, language and data files. Then I copied the files back fresh from the ZIP file, and configured the monuments (no domes, cooldown set to 1 second as players should immediately be able to re-gain ownership, and 60 points needed to gain ownership). I also made sure files are owned by the server. No errors in the logs that I could find. That was last night. This morning monument locks were frozen in time, no errors in logs, hence I decided to go back to 1.4.1. Here is an exemplary monument config (Airfield.json) - I set them all in a similar fashion { "On/Off": true, "Local position (regarding the monument)": "(0, 0, -26.673)", "Zone shape settings": { "Type (0 - Sphere, 1 - Box)": 0, "Size": "(100, 100, 100)", "Radius": 205.0, "Zone dimmer (0 - remove the dimmer)": 0, "Use colored spheres to display the status of the monument (Green - free; Red - Busy)": true }, "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)" }, "Monument settings": { "Timers": { "Cooldown timer after becoming monument owner during which the player cannot claim the title again in seconds": 1.0, "Timed duration which the player will retaion ownership of the monument in seconds": 600, "The amount of time which the owner can leave the monument area and retain their title in seconds": 300 }, "Settings for obtaining monument owner status": { "The number of points that the player must receive to become the owner of the monument": 60, "Points for time": { "On/Off": true, "Number of points per 1 sec": 1 }, "Points for NPC damage": { "On/Off": true, "Number of points per 1 damage": 1 }, "Points for Boss damage (Settings for the \"BossMonster\" plugin)": { "On/Off": true, "Number of points per 1 damage": 1 }, "Points for Bradley damage": { "On/Off": true, "Number of points per 1 damage": 1 }, "Points for crates": { "On/Off": true, "Default number of points (if the entity name is not in the list below)": 5, "Entities": { "assets/bundled/prefabs/radtown/crate_normal_2.prefab": 10, "assets/bundled/prefabs/radtown/crate_normal.prefab": 20, "assets/bundled/prefabs/radtown/crate_elite.prefab": 30 } }, "Points for open doors": { "On/Off": true, "Default number of points (if the entity name is not in the list below)": 5, "Entities": { "Green": 10, "Blue": 20, "Red": 30 } }, "Points for collectable items": { "On/Off": true, "Default number of points (if the entity name is not in the list below)": 5, "Entities": { "assets/bundled/prefabs/autospawn/collectable/hemp/hemp-collectable.prefab": 10, "assets/bundled/prefabs/autospawn/collectable/wood/wood-collectable.prefab": 10, "assets/bundled/prefabs/autospawn/collectable/stone/metal-collectable.prefab": 10, "assets/bundled/prefabs/autospawn/collectable/stone/sulfur-collectable.prefab": 10, "assets/bundled/prefabs/autospawn/collectable/stone/stone-collectable.prefab": 10, "assets/content/structures/excavator/prefabs/diesel_collectable.prefab": 10 } }, "Points for start hacking the crate": { "On/Off": true, "Number of points per launch": 50 } }, "Settings for Monument guests": { "Can a non owner enter or stay in the zone": true, "Can deal damage to NPCs if not an owner": false, "Can deal damage to tanks if not an owner": false, "Can deal damage to barrel if not an owner": false, "Can crates be looted if not an owner": false, "Can collectable items (diesel, cards) be pickup if not an owner": false, "Can crates be hacked if not an owner": false, "Can the doors be opened with a card": true, "Can backpacks be looted if not an owner": false, "Can recycler be used if not an owner": true, "Can NPCs target players if not an owner": true, "Can tanks target players if not an owner": true } } } log.txt

Dears, despite "MonumentOwner" (1.4.1) being bugged badly I will have to go back to that version as it at least handled locking and relesing ownerships somewhat ok-ish and problems can be worked around. In the new version 1.5.5 I'm missing proper announcements for monument locks in global chat, and in addition ownership is not released from monuments even if the player logs off and the server does it's nightly restart. Although I like some of the new ideas, especially having points to lock a monument rather than doing a series of things, locking and unlocking as a core feature has to work reliably.

Hi all, you can disregard this and close. The problem came from Pterodactyl, where I created folders and copied files through their GUI. Files and folders were owned by root and not by the Rust server, which led to the error message. I corrected ownership for files and folders, and now the PlayersData.json file is automatically created as it should be. Sorry for the noise.

I've done basically a clean install by removing the old plugin version and deleting each and every file (oxide/data/MM_Data, oxide/config, /oxide/lang, oxide/plugins) related to Monument Owner. Then copied the new files of the ZIP archive into their respective locations (English version) and configured each monument. Finally I copied the .cs file into the plugins folder. After first run the default config was created (oxide/config/MonumentOwner.json) - configuration is set like in previous versions, so players becoming owners or losing ownership should be announced in global chat. This is not the case. I did reload the plugin several times, but no chat notifications showing. What is the problem here? "Notification Settings": { "Prefix": "[MonumentOwner]", "Chat Message setting": { "Use chat notifications": true }, "Facepunch Game Tips setting": { "Use Facepunch Game Tips (notification bar above hotbar)": false, "Style (0 - Blue Normal, 1 - Red Normal, 2 - Blue Long, 3 - Blue Short, 4 - Server Event)": 2 }, "GUI Announcements setting (only for GUIAnnouncements plugin)": { "Do you use GUI Announcements integration": false, "Banner color": "Grey", "Text color": "White", "Adjust Vertical Position": 0.03 }, "Notify setting (only for Notify plugin)": { "Do you use Notify integration": false, "Type": "0" },

This problem report is a bit paradox, because jtedal explicitly requests users to delete the MM_Data/MonumentOwner/PlayersData.json file upon updating to 1.5.5 - however, if you do that there is a lengthy error showing when the plugin is supposed to initialize. I made sure the path oxide/data/MM_Data/MonumentOwner/ exists, and the file PlayersData.json actually does not exist. Then I loaded the plugin which threw below error message. Rust server is running inside a default Pterodactyl Wings node, mostly vanilla. The only way to bypass below error is to manually create an (empty) PlayersData.json in the respective location, and then reload the plugin. [MonumentOwner] Creating a default config... [MonumentOwner] Creation of the default config completed! Failed to call hook 'OnServerInitialized' on plugin 'MonumentOwner v1.5.5' (UnauthorizedAccessException: Access to the path "/home/container/oxide/data/MM_Data/MonumentOwner/PlayersData.json" is denied.) at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean anonymous, System.IO.FileOptions options) [0x0019e] in <e3aa8db986d7457ca73f10110f1283f5>:0 at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.IO.FileOptions options) [0x00000] in <e3aa8db986d7457ca73f10110f1283f5>:0 at (wrapper remoting-invoke-with-check) System.IO.FileStream..ctor(string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int,System.IO.FileOptions) at System.IO.StreamWriter..ctor (System.String path, System.Boolean append, System.Text.Encoding encoding, System.Int32 bufferSize) [0x00055] in <e3aa8db986d7457ca73f10110f1283f5>:0 at System.IO.StreamWriter..ctor (System.String path) [0x00008] in <e3aa8db986d7457ca73f10110f1283f5>:0 at (wrapper remoting-invoke-with-check) System.IO.StreamWriter..ctor(string) at System.IO.File.WriteAllText (System.String path, System.String contents) [0x00026] in <e3aa8db986d7457ca73f10110f1283f5>:0 at Oxide.Core.Configuration.DynamicConfigFile.WriteObject[T] (T config, System.Boolean sync, System.String filename) [0x0003f] in <beb2b64691c64e2b95b99491bd85442c>:0 at Oxide.Core.DataFileSystem.WriteObject[T] (System.String name, T Object, System.Boolean sync) [0x00007] in <beb2b64691c64e2b95b99491bd85442c>:0 at Oxide.Core.DataFileSystem.ReadObject[T] (System.String name) [0x0000f] in <beb2b64691c64e2b95b99491bd85442c>:0 at Oxide.Plugins.MonumentOwner+PlayerDataManager.LoadFiles () [0x0001b] in <7a50ab0e20f34d74be6f8445060ef41f>:0 at Oxide.Plugins.MonumentOwner.OnServerInitialized () [0x0003a] in <7a50ab0e20f34d74be6f8445060ef41f>:0 at Oxide.Plugins.MonumentOwner.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00165] in <7a50ab0e20f34d74be6f8445060ef41f>:0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <795304323ac74a298b8ed190a1dfa739>:0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000de] in <beb2b64691c64e2b95b99491bd85442c>:0 at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <beb2b64691c64e2b95b99491bd85442c>:0 Loaded plugin MonumentOwner v1.5.5 by jtedal [MonumentOwner] Image Scores_jtedal download is completed. [MonumentOwner] Image Crown_jtedal download is completed. [MonumentOwner] Image ExitTime_jtedal download is completed. [MonumentOwner] Image Guest_jtedal download is completed.

You sure can - check the config files for each zone in "oxide/data/MM_Data/MonumentOwner/Monuments" and set the value in the "Zone dimmer" line to 0. I did the same. If you leave the "Use colored spheres" setting true, the plugin will draw red or green borders around monuments, depending on whether it is busy or free. Pretty neat, "Zone shape settings": { "Type (0 - Sphere, 1 - Box)": 0, "Size": "(100, 100, 100)", "Radius": 90.0, "Zone dimmer (0 - remove the dimmer)": 0, "Use colored spheres to display the status of the monument (Green - free; Red - Busy)": true },

Hi kasvoton, I think I worked out how to configure. My mistake was that I set the "Seed" line to "null" before wipe, and gave the plugin only 1 seed in the "Maps" array. I managed to successfully wipe my server by leaving the current seed on top of the json config file, and added my new seed alongside the current seed into the "Maps" array. Upon wipe the wiper plugin successfully chose the new (correct) seed. I think that solved it for me, and this ticket can be closed. Thanks again!

Hi ChickenNugget, I just checked your json and find sftp links in the "Files" section. Pretty sure you need to put in relative paths seen from the root directory of your game server. Hence instead of e.g. "sftp://[email protected]:2022/oxide/data/SkillTree.json" the line should rather read "oxide/data/SkillTree.json" because that is how it is seen from the Wiper plugin. The rest of your json looks pretty good to me. Though I'm not the plugin author I'm pretty sure you need to configure your game server to run the wipe command for you in your preferred rhythm - e.g. biweekly. You might want to take a look at umod.org "Timed Execute" which can do that for you. You're probably running the Rust server off Pterodactyl Panel / Wings and might be able to use Ptero's scheduler to issue the wipe command, and this way don't need additional plugins like "Timed Execute" BR

deleted - I solved it, see below Just one question remains: For the "Files" and "Blacklist" sections, is it possible to use wildcards or exclude entire directories from deletion? Example Blacklist lines: "oxide/data/RaidableBases/" to exclude that entire folder plus subfolders from deletion "oxide/data/copypaste/*.json" to exclude my copied structured from deletion

Hi kasvoton, when I try to "ping" you Discord keeps telling me I can't send a message to you, because you only accept messages from friends.

Current status for this plugin: Still waiting for your update, eager to test it. Managed to get the current plugin version work somewhat stable by unloading plugin on initial server start after wipe deletion of "oxide/data/MM_Data/MonumentOwner/CooldownPlayers.json" doing a nightly restart of my server. Upon restart the plugin loads and works fine for the rest of the wipe The problem stays reproducible and causes "inside terrain violation" and "flyhack" kicks right after the server wiped. By doing beforementioned steps the problem can be worked around, even though it does not explain or appear understandable why the workaround works. Not going to question this, patiently waiting for the update to come, and provide more feedback once it arrived. If you want to check / reproduce it yourself, set up a Rust server with oxide/uMod plugin support in Pterodactyl Panel/Wings, install the Monument Owner plugin and wipe your server. After wipe hell breaks loose, and your players get constantly kicked. You can also verify my workaround, and probably find why it works, and use that to solve the underlying problem. Remark: Disabling map markers as I said in my previous post seems to be a red herring and does not solve the problem. I still have markers disabled, as I don't need the extra info they give. The trick appears to be to unload the plugin immediately after wipe, and keep it unloaded until next server restart (which happens to be nightly in my case) Keep up the good work! Love your plugin.

Dears, this has probably been asked a million times, but I'm really struggling with the setup of this plugin. Trouble begins with the seed I want to use after the wipe. In previous tickets it was said "do no populate the seed and task entries in the json, use the seeds array in the bottom instead". Alright. Looking at my json, there is no "seeds" array anywhere. Instead the part which used to be for the seeds is now called "maps". If I insert my next seed there, it is getting ignored and the wiper sets some random seed. The only success I got so far was by shutting down the server and then populating the "seed" entry with the seed I want to have. Upon reboot a map with the correct seed is getting generated, and I'm good for the wipe. However, when the next wipe comes I enter my new seed into the json "seed" line on top, and run the "wipe" command. When the server restarts, the wiper replaced my manually set seed with something else, only heaven knows where it came from. Hence shut down the server, replace the seed and start it up again. I'm sure I'm doing something wrong. The wiper itself seems to work perfectly fine, and I love it so far. Would it be possible to put out a one-pager which explains configuration? It could be part of the (paid) download. Thanks for a great plugin!

Thanks for taking the time and checking my log. Interesting that you say my server is incorrectly installed. It is a fresh install - Pterodactyl "wings-in-docker" - where the entire stack is dockerized. I even tested and reproduced the bug on a 2nd server of mine. The moment I remove your plugin, players are no longer kicked. Foreseeable that you say the error must be on my side, rather than fixing a problem which clearly comes from your plugin. Cheap, that you don't even ask a single question and simply claim my installation is broken. This is simply not true. I understand that you're not interested in sorting these problems. Therefore this has been my first and last purchase. Amendment: Re-enabled the plugin, but reconfigured it not to use map markers. Without markers it seems to work.