-
Posts
42 -
Joined
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
BrettG's Achievements
-
Perfect, thank you. And one more question, how do I get it to stop announcing the bases in global chat? I seemed to have turned it on and can't remember what line I edited.
-
Hey, just as the title says, how can I exactly program it so that the plugin will spawn bases at given intervals say between 30-60 minutes so that it doesn't just spawn the max allowed all at once.
-
Sent you a DM from @endridtelek
-
Hello, Reaching out because recently switch to Carbon instead of oxide. The plugin works fine, the only thing I am noticing is that Skinner is taking up an unusually high Hook time with the following information from the c.plugininfo command. Skinner v1.5.0 by Whispers88 Path: C:\Users\Administrator\Desktop\2x Solo Duo\carbon\plugins\Skinner.cs Compile Time: 247ms Uptime: 5h6m42s Total Hook Time: 30099ms Total Memory Used: 9.6 mb Internal Hook Override: False Has Conditionals: False Mod Package: Scripts (83) Processor: Script Processor [.cs] Permissions: skinner.default skinner.craft skinner.items skinner.bypassauth skinner.skincon skinner.skininv skinner.import skinner.skinbase skinner.skinall skinner.default30cd Hooks: # Id Hook Time Memory Subscribed Async/Overrides 1 1330569572 OnServerInitialized 64ms 7.4 mb True 0/1 2 4051942512 CanStackItem 30031ms 2.2 mb True 0/1 3 589422924 OnLootEntityEnd 2ms 0.0 b True 0/1 4 4277473012 OnItemCraftFinished 1ms 0.0 b True 0/1 5 3438704737 OnActiveItemChanged 1ms 0.0 b False 0/1 Any idea what might cause this? It's causing some moderate FPS fluctuation.
-
BrettG started following Build Tools [grade/remove/skins] , Ammo HUD , Static Lootables and 6 others
-
- 205 comments
-
- #updates checker
- #plugin
- (and 5 more)
-
ahh okay, perhaps It was /rbe despawn that I tried before and not /rbe kill_cleanup. I will make sure to try that one next time.
-
Doing the command you mentioned near the base remains just gives me an error saying no raidable bases within 100m. I end up using remove all from the remover tool plugin to delete them. I’m thinking this happens sometimes when the server is shutting down or restarting. The raidable base event seems to be deleted (which is why the command doesn’t work). But doesn’t always delete the entire base. we also haven’t seen anything in error logs. So yeah I bet it is hard to fix something that isn’t giving any errors. Anyways looking forward to future updates.
-
Hey, I am running your raidable base plugin on a Windows server machine running 3 server instances. I am using your tier 1-3 raidable bases. I've found myself having to fly around the map often to delete raidable bases that didn't fully delete. The exterior stone walls will sometimes all be removed but other times only partly removed or not at all. The structure of the base seems to always remain sometimes with loot and sometimes without. Running the raidable bases command to delete a raid base within 100m doesn't work as it just gives me an error saying must be within 100m and I just use an admin remover tool to remove the base. I read in another support ticket you mention something about installing libgdiplus but I'm not seeing many details on Google about how to install that. Hopefully, you can help me out? Thanks.
-
- 205 comments
-
- #updates checker
- #plugin
- (and 5 more)
-
- 205 comments
-
- #updates checker
- #plugin
- (and 5 more)
-
- 205 comments
-
- #updates checker
- #plugin
- (and 5 more)
-
It seems that the number of resources used when I use the /upall command or shift+click isn't correct. I don't have the free upgrade permission (or whatever its called) and it costs a lot less to use upgrade all compared to just upgrading one item at a time. I don't know numbers off the top of my head but lets say I want to upgrade 5 twig bases to wood, IT would cost around 500 wood (again my numbers are probably wrong this is an example) and if I used the /upall it would cost a fraction of that like 135 or something really low.
- 255 comments
-
- #building
- #foundation
- (and 22 more)
-
One suggestion to fix this which would work well in my case is the need of an oxide permission to see the setting button to access the skins
-
- 255 comments
-
- #building
- #foundation
- (and 22 more)
-
- 5 comments
-
- #raidbases
- #raid
-
(and 3 more)
Tagged with: