This repository is for gathering the data displayed by my Dragons of the Void - Raid Loot Tiers user script, that I wrote for players of the game Dragons of the Void. To install the script itself, go to Greasyfork (even though I will probably update it using GitHub, at some point).
First, if you do not have write access, then to modify files you will need to create a fork (click the "Fork" button at the top of the page), edit the files and create a pull request. Once approved, the pull request will be merged and your changes will be applied.
If you have write access, you can either create a branch, then a pull request or update the files directly.
All the relevant files are in the csv format and located in the "community-gathered data" folder (more details about each of them down below):
- "Basic data" folder
- "Base damage taken" folder
- "Loot tiers and drop data" folder
- "On-hit drops" folder
It is absolutely not necessary to update everything at once. Usually, the loot tiers will come a lot later than the rest. Once the files have been modified, raid_list.json will automatically be updated and be made available to the users of my script within a minute or two.
"csv" stands for "comma-separated values". A csv file is just lines of characters (anything) separated by commas and can be read as a table. GitHub may display then as tables in preview mode, so look at the "code" tab instead if you need the syntax of the file.
If the content of a cell contains a comma, then put the whole cell between quotes but, otherwise, quotes are not needed. Please, write numbers with comma separators (1,000,000 instead of 1000000 or 1 000 000).
For an empty cell, simply do not put anything between the commas.
To end a line, just go to a new line (no character is needed to end a row).
Example:
- csv:
Column 1,Column 2,Column 3,Column 4
A,12,"I love cats, dogs and birds",
"B","1,300,752",,1/2
- Result:
| Column 1 | Column 2 | Column 3 | Column 4 |
|---|---|---|---|
| A | 12 | I love cats, dogs and birds | |
| B | 1,300,752 | 1/2 |
These files contain basic information about raids. It is important to know that only raids added here will appear in the script.
As a general rule, leave an empty cell or a question mark if you do not know what to put (use the option that seems the most relevant; read the rest of the file if needed).
About a few columns:
- Raid name: Type the exact same name that is displayed in the game
- Health on X: it is the health of the raid on X difficulty (obviously...)
- "On-hit drops?", "Loot expansion?"...: "Yes", "No" or "?"
These files contain damage type and damage values for each raid on each difficulty.
If a raid does not exist on every difficulties while there is a column for another difficulty, then leave the cells for the missing difficulties empty.
This folder contains subfolders named after various categories of raids, each one containing folders named after raids.
There are two cases that you will encounter:
- If a raid has an image loot table, then you will find the images (.png, .jpg, .jpeg, .webp but I prefer .png) alongside the file "Loot table.csv", which contains two columns: "file name" and "date of first use". The second column is obvious (usual format: "January 31st, 2024") and in the first column, type the name of the image that was uploaded to the folder (only upload new loot tables). Preferred format for the loot table name: Raid_Name_Number with numbers starting at 1 (0 for beta only).
For example: if the John Rabbit world raid is released on April 1st, 2025, then upload John_Rabbit_1.png in community-gathered data/Loot tiers and drop data/World raids/John Rabbit/ and fill new line in community-gathered data/Loot tiers and drop data/World raids/John Rabbit/Loot tables.csv the following way:
File Name,Date of first use
John_Rabbit_1.png,"April 1st, 2025"
- Else, you will find files named after each difficulty the raid is available in: Easy.csv, Hard.csv, Legendary.csv.
You should input a question mark in drop rarity cells (common, rare...) if you ignore the answer.
In the extra drops ones (remove these columns if not needed), input the skill level(s) like studious inspector does (for example, "DV3,DV7") if known, 0 or leave empty if nothing drops, and input a question mark if you do not know. If you do not know which tiers benefit from the skills, you can add the skills to the maximum tier only.
In the "Bonus" column, input nothing if the tier is not a bonus one, and the needed skill level if it is a bonus tier.
No need to bother with these files if you do not know any tier.
Quest bosses and minibosses are special: generally they follow the patterns found in the associated_Example_folders so only create files for the exceptions.
If the folder does not exist, then:
- you will find templates for each file in the
_Example_folder; some columns being optionnal - to create a folder on GitHub, you must create a file by adding both names in the file name: if you want to create new_folder containing new_file in existing_folder, then when you name your file type "new_folder/new_file" instead of just "new_file"
These files contain keen eye levels required for each raid on each difficulty. Input them like studious inspector does ("KE3,KE7", for example) if something drops, leave empty or add 0 if nothing drops. Only add raids that have at least one on-hit drop in one difficulty.
If a raid does not exist on every difficulties while there is a column for another difficulty, then leave the cells for the missing difficulties empty.
Notes.csv contains messages to display above loot tables and giving additional information, for example if there is a guaranteed drop.
- In the first column, input a condition in Python that raids must verify for a message to appear. You can use the following variable names (everything is case sensitive and none is mandatory): name (name of the raid), type (what is being displayed as raid type by the user script, like '' for regular raids, 'Guild raid', 'World raid'...), size ('Large'...), loot_format ('Image' if the loot table is available as an image, like world raids, else 'EHL'), difficulty and mode ("questing" for quests, "healthless" for raids without a health bar and "raiding" for the rest).
- In the second column, type the text to display. Add the name of the raid (or, in case of a group of raids, the name of said "group"), because the notes are also displayed on the full list of raids so people must know what they refer to.
Example: type == 'Guild raid' and difficulty == 'Hard',Hard guild raids always drop an additional void token.
This note applies to guild raids on hard difficulty. The words "and" and "or" can be used, alongside parenthesis, for conditions involving several criteria.
Also, note that in csv files, GitHub does not like double quotation marks for anything other than surrounding a whole cell. Hence why I used single ones for the two character strings ('Guild raid' and 'Hard').