Jump to content

miniMe_rust

Member
  • Posts

    175
  • Joined

  • Last visited

Everything posted by miniMe_rust

  1. Dears, since yesterday's force wipe and game update I had to remove the Monument Owner plugin, because players couldn't play the server anymore and got kicked for "inside terrain violation" errors as soon as they started to move around, e.g. run away from the spawn beach. The problem could be tracked back to the Monument Owner plugin. In a nutshell the [MonumentOwner] plugin loaded fine after wipe, no errors visible. As soon as players connected and started to move around, players were kicked and very lengthy error messages showed in the logs. See attached. In order to solve the problem I unloaded the plugin and checked the config - which is pretty much unchanged. I deleted the /oxide/data/MM_Data/MonumentOwner/CooldownPlayers.json file and reloaded the plugin. I instantly got player kicks again and decided to unload and remove the plugin entirely. It seems some game changes broke the Monument Owner plugin. Please check and correct your plugin, because my players really like it and it adds quality of life to my PvE server. Thank you
  2. Hi jtedal. not quite sure what you're asking. The cause seems quite obvious. From user side a card was swiped, and then management console the depicted error message showed up. Overall function seemed to be unaffected at that time, as the player could continue on the monument and loot it. Tbh I don't remember whether the lock worked. I can't hint you to what in the plugin caused the problem - you're the author and should know that. Besides that I believe your plugin has more pressing problems, but for that I will make a new post. In my eyes this ticket can be closed.
  3. Hi, big thanks for your excellent plugin - worth every cent. I love it! The players on my server are super-happy with it, even though there exist some shortcomings. Overall the functionality is a giant leap in quality of life. I love the configuration options you provide, and found them working really well. Also the first time I see monument locking working even for small places like supermarkets and gas stations. This is great! Some shortcomings I'd like to mention is regarding some inflexibility of the plugin. When the ownership ends a cooldown kicks in. Should the player still be inside the monument area, it should be possible that (s)he can become owner right again, e.g. by looting the next container or operating e.g. Excavator. Especially Excavator is impossible to foresee how long the player needs, and conflicts with the next player becoming owner will happen. Some players come with 3 Diesel, others have many more. Ownership should be handled more flexible, like make it an option that the serverowner can decide a cooldown only kicks in when the player left the area, otherwise ownership can prolong or be regained. It should be possible to define a Discord Hook, so that plugin activity can be monitored. This creates transparency, as messages could go to a public Discord channel, where players can see ownerships and such changes. It should be made more obvious whether ONE OF some criterions must be met, OR A COMBINATION. Players get confused and don't see when they need to do multiple things. It could be given different colors, like red for combination of things and amber for one-of criterions. Again, thank you for your great work.
  4. Failed to call hook 'OnCardSwipe' on plugin 'MonumentOwner v1.4.1' (ArgumentException: Value does not fall within the expected range.) at Oxide.Plugins.MonumentOwner+ControllerMonument.CanPlayerBecomeOwner (BasePlayer possibleOwner) [0x00216] in :0 at Oxide.Plugins.MonumentOwner.OnCardSwipe (CardReader cardReader, Keycard card, BasePlayer player) [0x000d0] in :0 at Oxide.Plugins.MonumentOwner.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x01271] in :0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in :0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in :0 at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in :0
  5. Hi, since recently the Monument Lock no longer handles locks correctly. When a player locks one monument, and another one locks another, it is likely that the 2nd player gets an error saying their team already had locked a monument, and cannot lock another one. However, both players are totally unrelated to each other and not in a team. Edit 17-Jan-2024 Nevermind, I removed this plugin from my server and replaced with "Monument Owner" which provides similar functionality and a bit more. I liked the "Monument Lock" plugin a lot and would pay for it, if it worked reliably. Thanks for your work, and hoping to see an update soon which puts "Monument Lock" back on the rails.

About Us

Codefling is the largest marketplace for plugins, maps, tools, and more, making it easy for customers to discover new content and for creators to monetize their work.

Downloads
3.2m
Total downloads
Customers
12.3k
Customers served
Files Sold
173.9k
Total sales
Payments
3.8m
Processed total
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.