imthenewguy
-
Posts
4,795 -
Joined
-
Last visited
-
Days Won
61
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by imthenewguy
-
Big update has been pushed out. If you haven't left a review of the plugin yet, I would really appreciate some feedback- 1,575 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
When the plugin unloads, the horse stats are adjusted to their original values. The horse won't have its speed adjusted unless a player with the perks mounts it, in which case it will increase its speed. I have added a config option in the next update to allow for the attributes to be selected, so you can only increase the horses run speed and not its turn and trot speeds when mounted.
- 1,575 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
Had a quick look at gather manager and it seems to manipulate the yields the same way that my plugin does as well (cumulatively). The way the the 2 would work would be that both base their modifiers on the default value, and add their additions over the top of it. For example, you have a 2x modifier for gather manager, and a 100% yield increase from Skill tree, and would normally only receive 1000 wood (vanilla rates), you would receive 3000 wood with both modifiers applied. Alpha loot I am not sure of. We stopped running it as we did not require it anymore. The way my plugin applies the loot is to add an additional loot slot to the container once spawned. So long as Alpha loot doesn't clear the contents of the container, it SHOULD work, but I'm not too sure. Worst case you can disable those buffs and replace them with more gather yield buffs etc.
- 1,575 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
Was a debug message I accidentally left in. Has been removed for next patch.
-
That's odd. Add me on discord and we can take a peak. im the new guy#0001
-
Will add hemp to the next release. Regarding damage with ranged weapons, it would be quite resource intensive checking each item whenever a bullet/explosion etc hits it, since these items aren't a part of the BaseCombatEntity class (meaning they can't actually take damage). The only work around would be to monitor each time a bullet lands somewhere and scan the list of deployed objects to see what entity was hit. This can be quite cumbersome when you are working with multiple players spraying automatic weapons at entities (bases, deployables etc). A work around to prevent OP base designs using rocks/trees etc would be to add a console command to kill all entities of a particular type (trees, rocks and bushes). -
When I have enough content to warrant a release or a major bug rears its head. -
Mind pasting the whole error? -
I have a fix for that ready for next release.
-
I can't see any developer hooks in the plugin, so probably not.
- 1,575 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
Have implemented a fix for the refund issue doing it based on craft task, not per crafted item.
- 1,575 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
Will add a console command to do that.
-
I will change the config to allow for the owner to set the container prefab in the config, instead of "small" or "large". So long as it uses the StorageContainer class it should work. Regarding API, would only need a call before the sort happens asking if it can happen. IE: CanQuickSort(uint id) or CanQuickSort(StorageContainer), where if we return false (or a non-null value of it's written that way), it cancels the request.
-
DeployableNature 1.0.6 fixed this issue. Are you running the latest version?
-
1.0.6 fixes the buff issue. Not sure why the yield wouldn't be working. You may have something conflicting with it.
-
It will. Forgot to remove the debug.
-
"Format for BetterChat title showing the playeres level. Set to null to disable.": "<color=#{0}>[Lv.{1}]</color>", "Default colour for BetterChat xp titles": "6D3D23", Those are the default values from memory. <color=# is what is used to colour the text. {0} is the argument used to colour the text, taken from the default colour. {1} is the level itself. Colour uses a hash color. You can pick a colour from here: https://htmlcolorcodes.com/
-
I found the issue. It is the way that the data is handled when the player disconnects. Effectively the player is doubling their stats each time they disconnect and reconnect, since I didn't clear the instanced buff data, and added the saved data to the existing instance on connect. The restart or unload/reload of the plugin wipes the instanced data, hence why it was correcting the problem. It was written in a way to remove unnecessary data from memory, but I forgot to clear it when the user disconnected. Will add to todays patch. Edit: Update pushed (1.0.6)
- 1,575 comments
-
- 2
-
-
-
- #leveling
- #progression
- (and 19 more)
-
Has he respec'd?
-
If you can keep an eye out for what might trigger this, be a respec or something else, I would appreciate it. Cannot seem to find an issue with the code that might cause this.
- 1,575 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
Do you know if the values of the buff are what you are receiving in benefits, or if it uses the new values? Also what version are you running?
-
I will look into it. Is that after a respec?
-
You can just change the string in the lang file to a white space. "AccessReminder": " " Keep in mind it will only display once per player per plugin restart, after they gain xp.
- 1,575 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
What messages are you talking about?
-
Odd. I have added a validation to check the dictionary for any existing entries prior to being added. Should prevent this moving forward. Will be in the next release.
- 1,575 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
