-
Posts
61 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by 21mac21
-
my bad, that was (just) a debug information. no error, no glitched item. you can just remove the line if(baseEntity is DroppedItemContainer) Puts("DroppedItemContainer spawned"); or download the latest version of the plugin -
Hey @NEXT, @Chill Roleplay, @Papi Rusty, thanks for your reports and the open (NEXT). I'll do my best to optimize the plugin further. It may be a problem because I've re-written the plugin multiple times but now it should work much better. - The problem with "gir.toggle" was solved (see https://codefling.com/files/support/19902-gir.toggle/ if you are interested in the cause). - Loot bags (dropped when the corpse despawns) are not supported by my plugin - Dropped loot (from barrels etc.) is now supported by my plugin. Please have a look at the section "known bugs" on the plugins page https://codefling.com/plugins/glitched-item-retriever There are two bugs (not made by me) that need to be fixed by Facepunch first, I did not find a workaround for them. I am working hard on a "close to 100% reliability", a better loggin (for admins) etc. Feel free to report any problems, suggestions, logs etc. and I promise to have a look at them ASAP.
-
Changed Status from Pending to Closed Changed Fixed In to 1.4.2
-
Thanks for reporting this bug. The problem was... my head. When an admin grants the permission to a group (like "Default"), it does not matter if the PLAYER has the permission or not (which was done when you used gir.toggle), since the permission was still inherited by the group. I just updated the plugin and updated the plugins description on the codefling page. The combined logic is now: - when a user has no permission (does not matter if inherited from a group or given to the player directly), no item will be retrieved. - when the user has the permission, the file "ExcludedPlayers.json" in the plugins data folder will be checked. If the player (who dropped an item) is contained: the item will not be retrieved, otherwise it will. When a player used "/gir.toggle", his steamID will be added/removed from the json file. Also, have a look at the changelog i added for version 1.4.2
-
Thanks for the suggestion! I'm not saying no, I just need some information on "why" beforehand. If an item, weapon, bag etc. glitches through the ground, i will be teleported back up onto the surface but will not move in any x or y direction. So you'll find it where your corpse (or when it already despawned: your loot bag) is. That's exactely where Rust adds the "death marker" on your map. I know, when you die again, the "old" death marker gets deleted / repositioned to the last place of death. But this plugin was not designed to keep a marker on the map after multiple deaths. The timer is kinda hard to do since (as I learned some days ago) there is not "THE ONE" despawn time for your loot, bags, corpse etc. Rust calulcates the despawn time dynamically depending on the item values. But there are exceptions so the despawn time will differ, depening on where the item is contained in: - corpse --> which will despawn into a loot bag - backpack - container (when you exchange items and put some in a crate, barrel etc.) - dropped on the floor by the player Examples: your loot bag will despawn instantly if the "best" item in your inventory is a torch, it will stay there for 40 minutes when the best item is a SAR, it will stay for 1 hour if the best item is an M249. cou can find the "despawn time" on rustclash, for example https://wiki.rustclash.com/item/m249
-
you CAN run the commands but the plugin is designed to do it AUTOMATICALLY. please re-read the paragraph "how does it work" in the plugin description: https://codefling.com/plugins/disbanded-team-restore?tab=details -
Hi TheFarrier, please see my response at this ticket: https://codefling.com/files/support/17898-failed-to-call-hook-'onserversave'-on-plugin-'disbandedteamrestore-v1.5.2/
-
Changed Status from Work in Progress to Pending
-
@Magnumk, @RR_Tappi: first of all: I am very sorry for the overdue answer. i'm taking bugs etc. very seriously but was drowning in work that had to be done before april (when my wife gave birth to our third girl). I'm back on track and will now take care of it. I just uploaded a new version 1.5.3 which includes more logging and exception handling. to get a more detailed output in the server console, change this line in the plugin file private bool debug = false; to private bool debug = true; @RR_Tappi FYI: You sent me the names of all your installed plugins, I went trough all of them and found no problem in using any of them besides my plugin. I did only test it on windows and with oxide, so currently I do not support carbon and was not able to test the linux version of the game server.
-
Hi Next, thanks for your honest feedback. It like to have a look deeper in this, why it does not always work. Currently, I am working on more detailed logging (for admins only) so you can see what glichted where and why it was (not) retreived. Like: "Permission not set for player xyz" or "item was more than x meters below the ground" (which is a threshold of my plugin, to determine if an admin threw it under the terrain on purpose). If you guys find any clues WHEN/WHERE it does not work, please drop me a DM and i''ll glady try to reproduce the problem. Like "when dying in monument xyz" or "when killed by a timed explosive" etc. THe more details the better I'm not running a real carbon server myself, just for test cases. Since the used logic is the same as for oxide, carbon SHOULD not be the problem, but I can't garantuee this.
-
Did this ever happen to you that the bag glitched UNDER a foundation AND trough the terrain? Glitching under the terrain mostly happens when you get killed when being very close to the terrain or when moving fast towards it (dropping from / crashing with a helicopter). If you want, I can demonstrate it on my test server 🙂 I can give you temporary admin rights (so you can use noclip) and test whatever you want.
-
Hi papi rusty, do the players have to permission? it's not set automatically after installing the plugin. a player himself can use /gir.toggle or you can use a permission manager to set glitcheditemretriever.active also: did youn try it as an admin? activate noclip/vanish, go beyond the map (but not further than 3 meters as noted in my plugins' description) and drop something. does it get retrieved?
-
Changed Status from Pending to Work in Progress
-
Hi there, can you send me a list (or screenshot of "MyRustServer", if you use this) of the plugins you have installed (as direct message maybe)? there may be some conflict with other plugins that work with the teams configuration. Another user reported this exact error when he was using "Better teams" by ahigao along with my plugin. after uninstalling, it seemed to work flawless.
-
Hi Malkizid, great ! Happy to hear that the problem was solved. Sure, he can contact me at anytime 🙂
-
Hi OvO, I've sent you a DM to ask for further information about your server/setup
-
Hi, can you DM me the whole log / server console output please? I'll look at it ASAP. Thank you
-
Changed Status from Pending to Closed Changed Fixed In to 1.5.2
-
Hi nickw, you are correct, the file was still 1.5.1 since the upload was not successful, somehow. I just uploaded 1.5.2 and tested it by downloading the plugin again. confirmed: 1.5.2 Thanks for pointing that out!
-
I am so sorry for missing this comment, I swear I did not get an email notification about this 😞 Yes, the new backpacks are also "items" that will be retrieved. But as I saw: you bought, tested and reviewed the plugin. Thanks a lot, I am glad it solved your problem!
-
Hi RR_Tappi, Sorry for the late reply. My kKids are ill. Yes, that was the reason why I made this plugin. Our server restarted at a given time and after it was online again, all teams were lost. Feel free to test my plugin. if it does not work in YOUR case I'll work with you on a solution. 100% refund garantuee if it does not fix your problem, promised 🙂
-
If this still happens, I could add some debug lines to output/log to the console. I was never able to reproduce this error, no other server owner ever reported this bug. the error happened in the oxide function "Oxide.Core.DataFileSystem.WriteObject" that I call, I can debug any further into that code (not mine).
-
Changed Status from Pending to Can't Reproduce
-
Changed Status from Pending to No Response
