imthenewguy
-
Posts
4,349 -
Joined
-
Last visited
-
Days Won
54
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by imthenewguy
-
Show me the names of the items when you select them in your inventory.
-
Is your player's name new? If not, why are you putting new in the command?
-
Pushed a fix.
-
Wht is the command you are running in its entirety? Paste the entire thing in here.
-
Config: "Recycler Item"
-
Hey you can either add the item with the skin id so it matches the config, or you can have shoppy stock run the addrecycler command to add a recycler to the players redeemable recyclers.
-
Have you got he latest version of both plugins?
-
Yeah remove it for now. I will have to figure out a solution
-
Might be something I do down the track.
-
Ahh right. Yeah its probably because its not applying the gather bonuses from the other plugins, specifically around the BlastMine skill.
-
Ahh i see the issue. It still uses the config value to set the %. I will update it to use the node value in the next release. For now, adjust "Reduction percentage [1.0 == full reduction]": 1.0, in the config.
-
Change Value "IO" to "Percentage"
-
I don't understand. What is your question?
-
You can follow the video for creating a custom skill. You could then add a custom level reward to give the permission to open a backpack after a set level. "List of rewards the player receives based on level": { "20": { "List of commands and chat messages that the player receives when reaching the specified level [Left = command. Right = Private message to player]. {id} = steam ID. {name} == name.": { "o.grant user {id} backpacks.use": "You unlocked the backpack" }, "List of commands that are fired off when the player data is reset": [ "o.revoke user {id} backpacks.use" ] } }, and you can create custom skills and set a level requirement to unlock them as well, by setting: "Minimum player level required to unlock this node": 0,- 1,447 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
Set "Kill all deployed nature when the associated cupboard is destroyed?" to true -
It's deployed on a large number of servers. It's by no means perfect and I tweak optimization as I find better ways to handle things, and there are very little complaints on server performance. It's a plugin that touches a large number of hooks in oxide, so it will always be a heavier plugin (like raidable bases), but it runs on servers with pop counts of 100+, so do with that info as you will.
- 1,447 comments
-
- 2
-
-
- #leveling
- #progression
- (and 19 more)
-
I need more information. Its not helpful saying you are having the same issue as a support ticket that the guy never really gave me helpful info (as we couldn't get the vid working). Did you guys follow the last comment in there that I mentioned (unloading all other plugins to test)? There are a couple of factors here that can cause this issue: Config issues Conflict issues I need as much info around things like: Are other placeholder items having the same issue, or are they working Does the issue persist when DeploiyableNature is the only loaded plugin Does the default config work
-
That's a good idea. I will add a config option to make the scroll bar visible
- 1,447 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
Yes, create a skill points per level perm in the config and assign it to the prestige oxide group.
- 1,447 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
Its a scrollable element. It's not a bug. You can have as many skills per row now as you like.
-
Yeah could be an undocumented change from this month
-
Not sure how my plugin would stop vanilla behaviour like that. All I am doing is renaming the item.text field.
-
Hey mate yeah that is the correct format. Depending on the shop plugin, you would replace target with the placeholder that represents their userid, such as {id} or %userid%. Also keep in mind the profile name is case sensitive.
- 1 reply
-
- 1
-
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Usage: givelegendary <target> <optional: profile name> So you would run: givelegendary winslow Sergant Helm
