-
Posts
127 -
Joined
-
Last visited
1 Follower
Recent Profile Visitors
1,918 profile views
iLakSkiL's Achievements
-
Changed Status from Pending to Closed Changed Fixed In to 3.1.1
-
Updated in 3.1.1
-
If it's only happening when the server boots up, it's not likely an issue to worry about. The error is related to the UnloadableTrainWagons being spawned in on start. Worst case scenario, there could be a single train wagon somewhere that doesn't have modified loot. Best case scenario, and most likely, everything is fine. If it's happening all the time, then there is something wrong. But this error is related to it detecting a train wagon that it's trying to modify.
-
Changed Status from Pending to Work in Progress
-
mlrs hurts players inside raidable base
iLakSkiL replied to PhatBlinkie's Support Request in Support
Changed Status from Pending to Work in Progress -
mlrs hurts players inside raidable base
iLakSkiL replied to PhatBlinkie's Support Request in Support
I'll take a look. I can go through the RaidableBases plugin and work on an update for MLRSDamage that integrates better with it. When I first coded all of it, it was when MLRS was new and RaidableBases hadn't addressed it yet, so there integration wasn't possible at the time. Inside of MLRSDamage, the line for "Allow Damage to Raidable and Abandoned Bases" just checks to see if the building blocks being damaged have an ownership of "0". This is regardless of who "owns" the raid, for those PVE raids, where you don't want someone else doing damage to the base. This is what I can work on to integrate with RaidableBases. It does the other checks however. So if Damage to Players is off, then maybe the line in the RaidableBase profile "Allow Players To Use MLRS" is somehow overriding it and allowing player damage. But first, maybe see if setting "Allow Players To Use MLRS" to false in your RaidableBases profiles fixes the issue? I'll work with the author of RaidableBases to see where conflicts may be coming up, but theoretically, if MLRSDamage has Allow Damage to Players as false, but players are taking damage, then some other plugin must be overriding MLRSDamage. -
I'll look into it. I have no idea how the metal detecting stuff works, so it'll take some research. -
Changed Status from Work in Progress to Closed
-
Changed Status from Pending to Work in Progress
-
Were you using an older version of the plugin? If so, my guess is that it's not loading the new file correctly, and still using the older config file. The "unknown command" signifies that it's not loading properly. Try renaming the oxide/config/CustomGather.json file, so that it acts as a backup. Delete the .cs file from your plugins folder, and try re-uploading the newest version again.
-
Changed Status from Work in Progress to No Response
-
Changed Status from Pending to Work in Progress
-
Is it compiling correctly in the console output? Was your file browser not updated after compiling the plugin? There's no reason why it wouldn't make those files.... I'd need more information to go off of than just that the files apparently didn't get created.
-
I'm not sure what you mean by a "list of modifiers." Do you mean a list of every thing that this plugin controls and can modify? Or like a list of entities/items and their modified rates of gather? I just uploaded a new rewrite of the plugin. In the config json file you can see all the areas that the plugin controls, i.e. picking items off the ground, fishing, harvesting, excavator, etc. And in the data json, you set the gather rates for specific areas, like the overall gather rate which includes items picked off the ground, items picked from planters, and harvested items like trees and ore, and then the other areas like fishing, excavator, quarries, etc.
-
Changed Status from Work in Progress to Closed
