Crafting alias that allows players to craft both non-magical and magical items. This system is highly customizable, which allows the usage of server rules to dictate what can be crafted, where items can be crafted, how often items can be crafted, and how fast items can be crafted. Ultimately, it is up to server staff to determine the settings. I highly recommend viewing the main documentation on GitHub (link below).
settings.jsonc is an example file as to what settings you can setup for your server (If you copy and paste, remember to remove comments, which is anything after //, otherwise Avrae will throw a parsing error). If you do not have a svar named crafting_settings, then it will turn to default settings (which are found at settings.jsonc).
Categories are symbolized by the main dictionary key within the settings svar. Some examples are the common and nonmagical item categories. There are two kinds of item categories: type-based and cost-based categories. Cost-based categories use numbers as their keys and type-based use names as their keys.
Settings:
{
"permanent": {
[
"Level Requirement (int)",
"DC (int)",
"Nat1 Penalty (int)",
"Nat20 Bonus (int)",
"Total Successes (int)",
"Total Failures Allowed (int)",
"Cooldown In Seconds (int)",
"Retail Item Cost in GP (int or float)",
"Hex code (with or without #)"
]
}
}Level Requirement: Level required to craft the item type
DC: DC required to meet for success
Nat1 Penalty: Penalty to successes for a Nat1
Total Successes: Successes necessary to finish crafting the item
Total Failures Allowed: Maximum failures
Cooldown In Seconds: Cooldown between crafting sessions (3600 seconds is an hour)
Retail Item Cost in GP: Cost of item in GP (use decimal for costs that include copper and silver)
Hex code: Color code for embed card (set to "" for random color)
Settings:
{
"0": {
[
"Level Requirement (int)",
"DC (int)", "Nat1 Penalty (int)",
"Nat20 Bonus (int)",
"Total Successes (int)",
"Total Failures Allowed (int)",
"Cooldown In Seconds (int)",
"Hex code (with or without #)"
]
}
}Level Requirement: Level required to craft the item type
DC: DC required to meet for success
Nat1 Penalty: Penalty to successes for a Nat1
Total Successes: Successes necessary to finish crafting the item
Total Failures Allowed: Maximum failures
Cooldown In Seconds: Cooldown between crafting sessions (3600 seconds is an hour)
Hex code: Color code for embed card (set to "" for random color)
Using numbers as keys, they are thresholds on costs. I.e. If I try to craft a 5gp item, by default it goes past the 0gp threshold, but not the 101gp threshold.
Example:
{
"0": [5, 8, -1, 5, 1, 1, 7200, "#242528"],
"101": [9, 13, -2, 5, 5, 2, 14400, "#242528"]
}If you do not have the settings below, it does revert to default settings:
lfg_integration: This is a setting that works with the LFG Alias I have written. All this does, is it will display a message with the LFG that the character is currently crafting.
Default: False
pro_rate_refund: Whether or not the character gets a prorated refund if they decide to stop a project early. The prorated refund is calculated as followed:
(1 - ((Number_of_Successes / Number_of_Successes_Needed) + (Number_of_Failures /(Number_of_Failures_Allowed * 2)))) * .5Default: true
success_dispType: Display counter type for successes. Valid values:
- None
- "bubble"
- "square"
- "hex"
- "star"
Default: "star"
failure_dispType: Display counter type for failures. Valid values:
- None
- "bubble"
- "square"
- "hex"
- "star"
Default: "hex"
jack_of_trades: Whether or not Jack of All Trades applies to the crafting check.
Default: true
reliable_talent: Whether or not Reliable Talent applies to the crafting check.
Default: false (I would highly recommend that this left disabled, as rogues are already powerful. Giving them reliable talent could lead to guaranteed successes.)
success_mod_threshold: The thresholds above the DC for additional successes.
Default (don't forget to remove the comments, otherwise it will throw an error):
{
"-999": 1, // This key is always by default as meeting the DC always results in 1 success
"5": 2,
"10": 3,
"15": 4,
"20": 5 // The highest key sets the maximum amount of successes possible (even with Nat20 bonuses)
}whitelisted_channel_ids: This list allows staff to control what channels/threads craft commands (that alter the CCs in any fashion) are run in. You will need to grab the channel ID of each channel/thread you want whitelisted. If the list is empty, then it will allow all channels/threads.
Default: []
parent_channel_inherit: This determines if threads of whitelisted channels inherit the whitelisted status. This is not recommended as this does not stop players from creating threads within channels and running commands without staff knowledge. Default: false
xp_categories: This determines if players get xp for finishing items. Category names need to match those setup, otherwise players will not receive xp. If the xp_categories is turned on, the subalias will add xp to xp tracker (recommended to use the New XP library made by bryonius, otherwise it shows up in cvars). These are the valid input types:
- string (singular category or all categories):
- Name of a single category i.e.
"common" "all", will allow all categories
- Name of a single category i.e.
- list (singular category or selective categories):
["category 1", "category 2", "category 3"]- If
"all"is a string in the list, it will allow all categories
- If
- dictionary (selective types and categories):
{"category 1": "all", "category 2": ["perm", "all"], "category 3": "perm"}- If
"all"is a value (either as a string or a string within a list), it will allow all item types within that category.
- If
- boolean (true or false):
true, will act like"all"false, does not give xp at all
Default: false
Max_history: Max number of items that show up in history per list.
Default: 15
Requests can be made at this link.
All requests can be viewed at this link. All requests are viewable by all, if I have any problems I will restrict access to these links.
You can click the button below to view my ko-fi page. Donations like this help me write more aliases and donators do get priority on feature requests.
