beee
-
Posts
444 -
Joined
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by beee
-
Ok it makes sense now, try that one out. RustRBLootEditor.zip
-
replace . with , maybe?
-
Please extract the attached file in v1.4.3 folder and see if that works for you. RustRBLootEditor(replace in 1.4.3).zip
-
Changed Status from Pending to Closed Changed Fixed In to 1.4.3
-
Suggestion: Filter for Items that don't spawn
beee replied to Jackelmyer's Support Request in Support
Changed Status from Pending to Closed -
That's odd, i can't replicate this issue.
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Suggestion: Filter for Items that don't spawn
beee replied to Jackelmyer's Support Request in Support
yeah i could display them with red overlay, will try to include that next update. -
Changed Status from Pending to Closed
-
Will consider it, thanks for the suggestion.
-
Changed Status from Pending to Closed Changed Fixed In to 1.4.1
-
Let me know if the update pushed worked out for you.
-
Just noticed that ticket and i happened to push a bulk select and delete functionality but editing didn't come to mind. Will include it in next update, probably after forced.
-
no it's fine i found the issue, posting an update now
-
If you paid for this file, better dm it rather than send here.
-
please send here the loot file so i can test it out
-
Will consider having a multi profile comparison view, but can't promise it would be anytime soon. -
show me your config plz
-
Changed Status from Pending to Not a Bug
-
It looked like an out of date oxide compiler issue, it might have auto updated itself.
-
So it was not showing this error before you edited the config? If so please send me your config file.
-
Will consider that for future update, if it doesn't work for you change it in the cs file for now.
-
Someone sent me about this same plugin recently, that's XDStatistics i believe. So basically they are sending messages with a syntax error in the color tags, we looked into fixing it from their lang file but seems like part of it was in hardcoded. Anyway, I will look into detecting syntax mistakes in messages in the future, but for now what you can do is set Force Color to true
