-
Posts
1,556 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by dustyhansen
-
- 10 comments
-
- #tech tree
- #disable
-
(and 1 more)
Tagged with:
-
- 43 comments
-
- #christmas
- #npc
-
(and 5 more)
Tagged with:
-
- 7 comments
-
- #rust
- #custom map
-
(and 4 more)
Tagged with:
-
NpcHordeRustEdit Plugin Failed to Compile
dustyhansen replied to dustyhansen's Support Request in Support
Thanks! -
I am running 2.1.3 and it seems like it is not autorunning the event. I was able to manually start it, but my players tell me it is not happening on its own. I manually started Harbor and it said it was at P15, but there is no harbor at that location and when i go there there is no cargo ship either.
-
The plugin is failing to compile on today's update. NpcHordeRustEdit - Failed to compile: NpcHordeRustEdit.cs(296,93): error CS0019: Operator '==' cannot be applied to operands of type 'NetworkableId' and 'uint'
-
Same issue, plugin fails to compile.
-
-
-
Building Damage Regardless of Setting
dustyhansen replied to dustyhansen's Support Request in Support
What response were you looking for? When I place a wall with a window in it it is raidable, but a regular wall isn't. -
- 67 comments
-
- #stacks
- #chest stacks
- (and 9 more)
-
Did you try picking up items? Like stone and hemp? Those are not showing the gather rate for me.
-
- 67 comments
-
- #stacks
- #chest stacks
- (and 9 more)
-
- 103 comments
-
- #panel
- #infopanel
- (and 4 more)
-
It appears to be broken after today's Rust update. I am no longer getting 2x gather rates as I have it configured at.
-
- 67 comments
-
- 1
-
-
- #stacks
- #chest stacks
- (and 9 more)
-
I am trying to use this plugin to prevent players from damaging each others buildings, that's all. I set a rule with default to allow and then I added block player_building. It works great for walls and doors, but not for windows and ceilings, etc. Was this an oversight or am I missing something?
-
How about you write the plugin so it isn't required to delete the config file every time you update it?
-
When I upgrade to this latest version of the plugin I get this error in console and the plugin unloads:
-
- 67 comments
-
- #stacks
- #chest stacks
- (and 9 more)