imthenewguy
-
Posts
3,858 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by imthenewguy
-
1. Yes, you can set the source that items are dropped from from the list on the main sales page (under "Gathering Sources"). The number represents the drop source. Here is an example of the config for an Avocado: "avocado": { "enabled": true, "base_shortname": "apple", "skin": 2783687116, "gathered_from": [ 2 ], "dropWeight": 100, "max_count": 2, "imageURL": "https://i.imgur.com/OKmLpNk.png", "market_enable": true, "market_buy_price": 10.0, "market_sell_price": 5.0, "market_quantity": 0, "loot_container_drop_weight": 100.0 }, Under the option "gathered_from", you can see there is currently a number 2 inside of the array. This represents Arid trees (trees found in the desert). If you wanted to change its drop source by removing it from arid trees, or adding additional drop sources, you could adjust it like so: "gathered_from": [ 2, 6, 7 ], This would make it so avocados could drop from pumpkin and potato patches. 2. If you do not plan on adding NPCs that will be used to access the market, then yes you can prevent certain players from accessing it by only assigning the cooking.market.command permission to certain users/groups. If you have the market accessible via NPCs then any player can speak to the NPC and access it. -
They won't conflict, but you may want to lower the buff modifiers in EpicLoot for Builders, Assemblers and Fabricators buffs due to the nature of the buffs. I had players able to make a profile by crafting/recycling items because the combined values from SkillTree and EpicLoot made them proc way too often. -
At this point the only thing you can do is set the benefits for wearing x amount of a certain item, and add whatever set bonuses you want to those benefits. May be something I could look at in the future though.
- 250 comments
-
- 1
-
-
- #enhanced
- #custom loot
- (and 7 more)
-
Version 1.0.13
441 downloads
Random Trader is a plugin that spawns a random shop along the side of the road, and is loaded with a randomly chosen shop profile. When a player interacts with the vending machine they are presented with randomly selected items from the shop profile, which are given random stock amounts and a random scrap/econ/SRP price. The plugin allows for the minimum and maximum stock and price values to be set in the config, and allows for the number of items displayed to be adjusted. The plugin comes with 4 loot tables by default: Clothing Weapons Tools Random items The following shops are automatically added if you own the relevant plugins Cooking EpicLoot Installing the plugin is as simple as dropping some files inside of your oxide folders. Ensure CopyPaste and ImageLibrary are loaded on your server. The plugin will acquire the files from my dropbox and stores them in the appropriate folder. If you own Cooking and/or EpicLoot, both plugins will automatically create profiles for RandomTrader in your config. Command: spawntrader Usage: /spawntrader <profile name> Example: /spawntrader weapons - will spawn a random shop with the weapons profile loaded. Command: despawntrader Usage: /despawntrader <profile name> Example: /despawntrader weapons - will despawn the weapons shop if it is spawned. Command: rtremovestoredata Usage: /rtremovestoredata <profile name> Example: /rtremovestoredata cooking - deletes the data for cooking from your config. Command: rtfindnewshops Usage: /rtfindnewshops Example: /rtfindnewshops - Finds new shops that are not in the config and saves them to the config. Useful for forcing external plugins to load their shop profiles in (Cooking/EpicLoot). Command: rtcheckpoints Usage: /rtcheckpoints Example: /rtcheckpoints - shows you the potential spawn locations for the shops. randomtrader.use - required to access the shop. randomtrader.admin - required to manually spawn/despawn vending machines. Config example: https://pastebin.com/MvcdBtTb$14.99- 23 comments
- 1 review
-
- 4
-
-
-
- #vending
- #vending machine
- (and 6 more)
-
The token is simply programmed to add the player to a group. The group that the token can provide them with can be any group you like, such as VIP, Admin, VIPExtended etc. The player then inherits any permissions that you have assigned to that group, such as nightvision, weapon damage etc. An example would be: You create a new oxide group called "Battle" You configure the token to add the player to the group "Battle" once consumed. You assign the permission nightvision.allowed to the group (o.grant group Battle nightvision.allowed). Whenever a player consumes the token, they will be added to the "Battle" group, and will have access to the nightvision command. -
Your best bet is to create an oxide group and have the plugin assign the player to that oxide group.
-
The error may be caused by trying to access an invalid container type. These are the valid crates that are included by default: ["crate_normal_2"] = 1f, ["crate_normal"] = 3f, ["crate_elite"] = 15f, ["crate_underwater_basic"] = 6f, ["crate_underwater_advanced"] = 12f, ["heli_crate"] = 10f, ["bradley_crate"] = 10f, ["codelockedhackablecrate"] = 10f, ["codelockedhackablecrate_oilrig"] = 10f, ["crate_tools"] = 1.5f Other devs can use the HookMethod: public void GenerateItem(BasePlayer player, string type = null, List<string> item_shortname = null, string tier = null, bool msg = false) Type = the buff type. List<string> item_shortname is a list of shortnames that we randomly pick from. Only add 1 shortname if you want a guarantee for that item to be picked. Tier is the letter of the tier (s/a/b/c). Msg is the message a player will receive. Msg returns a message in the following format "You received: {0}. \n- Tier: {1}. \n- Value: {2}" Alternatively they can call it via a console command: "genitem <target ID/name> <optional: item shortname> <optional: enhancement type> <optional: tier>"
-
DOes not support defenses, only perks. Will add a config option allowing you to specify skins for specific items. The useless combos were intentional (a lot of games do this). You will need to use the whitelist of the blacklist if you don't want that to be the case. The explanation for Should we use the default item loot table for the below containers? is correct. The artisan idea is interesting. I am looking at potentially integrating it with a revamped professions plugin I am planning though, so we will see what becomes of it.
- 250 comments
-
- 1
-
-
- #enhanced
- #custom loot
- (and 7 more)
-
Ask the dev to maintain the item.nam when re-creating the items.
-
No idea. All I know is 500x500 works for me.
-
What update are you talking about? Unless you have something that adjusts the names of your items, a restart of the server should not have any effect on the item.name, unless you have another plugin that could be causing issue. Potential conflicts between stack modifiers etc.
-
Changed Status from Pending to Closed
-
Was patched in 1.0.2. You will need to update it in your lang.
-
Just make sure it's 500x500 as well.
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Will add to next patch
-
Will patch in the next update.
-
Yeah you can have 1 command added token atm.
-
You can change the supporter containers in the config from memory. That would be the best way to go.
-
container.transform.position < -400 Not sure what that is. Does he mean Vector3.Distance, or the y value is 400 underground? My containers also spawn under ground as well, but they are at around 800-1000. The API released today doesn't help.
-
Changed Status from Pending to No Response
-
Changed Status from Pending to No Response
-
If raidable bases allows you to add items to the loot table that change their display name, then yea you could follow the same format and add them to your item list. I can't see any options in the API list to add loot to the raidable bases loot table.
