Back

Guides

Community created guides, helpful strategies, and more.
TOPIC | [DATA] Coli skills + enemy stats
1 2 3 4 5 6
As of Dec 4, 2019, the devs have released the amazing Game Database.

This database contains the stats, level, and element of each Coliseum enemy. The only thing missing from the database is the AI behavior at this time, but it may be added later. In any case, this extra thread is overkill and now RETIRED. Please post in the main thread instead. Thanks everyone!
Data - Coliseum skills + enemy stats

Hi everyone! This is the supporting data collection thread for the skills + enemies guide and Coliseum skills + enemies tool.

As of Coliseum 2.0, most previously dev-sanctioned data collection methods for Coliseum enemies have been removed in favor of code improvements. Coliseum 2.0 is a wonderful update, but this also means that collecting data for enemies has become much, much more difficult, and I can no longer do it by myself. This is where you come in!

In this thread, I provide requests for data to keep my tool updated. When new venues / enemies / updates come out, we will need new data.

You can help in a few ways: share your data with the provided spreadsheet format, or post in this thread in the requested thread format. Please check out How to record.

You may choose as few or as many types of requested data to contribute. Every little bit helps, thank you!
As of Dec 4, 2019, the devs have released the amazing Game Database.

This database contains the stats, level, and element of each Coliseum enemy. The only thing missing from the database is the AI behavior at this time, but it may be added later. In any case, this extra thread is overkill and now RETIRED. Please post in the main thread instead. Thanks everyone!
Data - Coliseum skills + enemy stats

Hi everyone! This is the supporting data collection thread for the skills + enemies guide and Coliseum skills + enemies tool.

As of Coliseum 2.0, most previously dev-sanctioned data collection methods for Coliseum enemies have been removed in favor of code improvements. Coliseum 2.0 is a wonderful update, but this also means that collecting data for enemies has become much, much more difficult, and I can no longer do it by myself. This is where you come in!

In this thread, I provide requests for data to keep my tool updated. When new venues / enemies / updates come out, we will need new data.

You can help in a few ways: share your data with the provided spreadsheet format, or post in this thread in the requested thread format. Please check out How to record.

You may choose as few or as many types of requested data to contribute. Every little bit helps, thank you!
Bonsai pixels (tofu and tea motif) by miirshroom
Types of data

This post contains a detailed description of the types of data that we collect. If you prefer to skip to how to help, please check out how to record.

We are interested in several categories of data, listed below. Please feel free to choose as few or as many categories as you'd like. If a category is not listed but you believe it should be, please post to discuss in this thread.

Enemy KO requirements

We collect data that helps us to determine which stats our dragons need to KO an enemy with a specific skill or combination.

In any skill damage formula, the components to filling out the OHKO threshold are skill name + damage, skill caster offensive stats, target full health, and target defensive stats.

Easy-to-gather data includes: The skill you are using, the corresponding offensive stat of the user (physical = STR, magic = INT), and the skill damage caused to the enemy.

Buffs / debuffs / damage modifiers (Defend, Contuse, camping bonus, etc.) would also need to be recorded if they were present, though preferably we would avoid including them if possible.

Inferrable data includes: The DEF / MND of the enemy based on the provided "easy-to-gather" data.

Trickier-to-gather data includes: The exact total health of the enemy. This needs to be viewed in the browser console (details here). From the full health value, we can guess the VIT of the enemy by subtracting the assumed health based on Level. The devs have said that it's perfectly okay to collect data in this manner. See this post.

Enemy elements and AI

We collect data about the enemy's element (Neutral, Earth, Plague, etc.) as well as what kinds of skills they use.

Some exact enemy behaviors are difficult to determine because they may rarely use certain skills (such as an elemental ultimate), but we can get a general idea of what the enemy is like from its more commonly-used skills (Scratch, Contuse, etc.)

Enemy offensive stats

We collect data about the enemy's offensive stats (STR, INT).

Easy-to-gather data includes: The skill used by the enemy, the skill damage caused by the enemy, and your dragon's DEF, MND, and Element.

Buffs / debuffs / damage modifiers (Defend, Contuse, camping bonus, etc.) would also need to be recorded if they were present, though preferably we would avoid including them if possible.

Inferrable data includes: The STR / INT of the enemy based on the provided "easy-to-gather" data.

QCK and turn order

We focus on collecting data that gives us insight into the turn orders during battle.

While enemy QCK is no longer possible to determine exactly after Coliseum 2.0's changes to available data, we can still learn something from recording turn orders.

This is a rather involved process, so the data recording format and full explanations for the QCK and turn order section will come at a later date. Sorry for the inconvenience!
Types of data

This post contains a detailed description of the types of data that we collect. If you prefer to skip to how to help, please check out how to record.

We are interested in several categories of data, listed below. Please feel free to choose as few or as many categories as you'd like. If a category is not listed but you believe it should be, please post to discuss in this thread.

Enemy KO requirements

We collect data that helps us to determine which stats our dragons need to KO an enemy with a specific skill or combination.

In any skill damage formula, the components to filling out the OHKO threshold are skill name + damage, skill caster offensive stats, target full health, and target defensive stats.

Easy-to-gather data includes: The skill you are using, the corresponding offensive stat of the user (physical = STR, magic = INT), and the skill damage caused to the enemy.

Buffs / debuffs / damage modifiers (Defend, Contuse, camping bonus, etc.) would also need to be recorded if they were present, though preferably we would avoid including them if possible.

Inferrable data includes: The DEF / MND of the enemy based on the provided "easy-to-gather" data.

Trickier-to-gather data includes: The exact total health of the enemy. This needs to be viewed in the browser console (details here). From the full health value, we can guess the VIT of the enemy by subtracting the assumed health based on Level. The devs have said that it's perfectly okay to collect data in this manner. See this post.

Enemy elements and AI

We collect data about the enemy's element (Neutral, Earth, Plague, etc.) as well as what kinds of skills they use.

Some exact enemy behaviors are difficult to determine because they may rarely use certain skills (such as an elemental ultimate), but we can get a general idea of what the enemy is like from its more commonly-used skills (Scratch, Contuse, etc.)

Enemy offensive stats

We collect data about the enemy's offensive stats (STR, INT).

Easy-to-gather data includes: The skill used by the enemy, the skill damage caused by the enemy, and your dragon's DEF, MND, and Element.

Buffs / debuffs / damage modifiers (Defend, Contuse, camping bonus, etc.) would also need to be recorded if they were present, though preferably we would avoid including them if possible.

Inferrable data includes: The STR / INT of the enemy based on the provided "easy-to-gather" data.

QCK and turn order

We focus on collecting data that gives us insight into the turn orders during battle.

While enemy QCK is no longer possible to determine exactly after Coliseum 2.0's changes to available data, we can still learn something from recording turn orders.

This is a rather involved process, so the data recording format and full explanations for the QCK and turn order section will come at a later date. Sorry for the inconvenience!
Bonsai pixels (tofu and tea motif) by miirshroom
How to record

You may help by either using a spreadsheet or post in this thread. It is not necessary to do both.

Please only report for enemies for which we are missing data in the skills and enemies tool. This section will only typically be necessary during large Coliseum updates where new enemies are introduced or existing ones are changed. If you'd like to be pinged with new requests, please ask to be added to the ping lists.

Reporting with spreadsheet

The spreadsheet template contains instructions and separate tabs for recording.

Click here for the spreadsheet template (make a copy)

Reporting in thread post

If you'd prefer to post in this thread, please use the following formats.

Enemy KO requirements

Please submit:
Quote:
Enemy:
Skill:
Damage:
STR/INT:
Buffs / debuffs / damage modifiers *: Aim for data without modifiers if possible, but please list if they exist

Enemy: The name of the enemy that was attacked with your dragon's skill.

Skill: The name of the skill that your dragon used to attack.
For easiest calculation, please collect the damage data of Eliminate for STR and Contuse for INT if possible. Otherwise, a different skill is acceptable.

Damage: The regular (non-critical-hit) damage caused to the enemy by your dragon's skill.

STR/INT: The STR and INT of the dragon that used the skill.

Buffs / debuffs / damage modifiers: If possible, please try to avoid buffs / debuffs / modifiers that change the damage totals. However, if you cannot avoid them, please record all of the ones that were present during the turn of your attack.

There are two kinds of modifiers when collecting Enemy KO threshold data:
  1. Offensive modifiers on your dragon, such as Rally, Concentration, Contuse, or STR / INT camping bonuses from the captcha.
  2. Defensive modifiers on the enemy, such as Sear and Petrify.

* If your flight currently has first place in Dominance, your dragon will incorrectly display as having 1 extra stat, but the stat does not have a true effect. (ie: A dragon with a true STR of 117 will erroneously display a STR of 118.) Please record your dragon's true stats.

This only applies if your flight's flag shows up in first place on the left hand of the Dominance screen. Second and third places are not affected, and it doesn't matter which flight is first on the right hand side of the Dominance screen.

Optional:

Enemy total health amounts are required for us to complete the KO threshold data, but to collect this data, it is necessary to view information in the browser console (explained below). The devs have said that it's perfectly okay to collect data in this manner. See this post.

Learn how to help collect enemy total health data here.

Enemy elements and AI

Please submit:

Enemy: The name of the enemy that you encountered.
Element: The element of the enemy (ie: Neutral, Earth, Plague, etc.)
Enemy skills: The names of skills that you have observed the enemy to cast. (ie: Scratch, Contuse, etc.)

Enemy offensive stats

Please submit:
Quote:
Enemy:
Enemy Skill:
Enemy Damage / Healing:
Dragon DEF/MND:
Dragon Element:
Damage modifiers *: Aim for data without buff / debuff modifiers if possible, but please list if they exist

Enemy: The name of the enemy that attacked your dragon or used a healing skill on its allies.

Enemy Skill: The name of the skill that the enemy used to attack or heal with.

Enemy Damage / Healing: The regular (non-critical-hit) damage / healing caused by the enemy's skill.

Dragon DEF/MND: The DEF and MND of the dragon that was hit by the skill. The lower, the better; very high DEF/MND can cause skills to hit for the minimum 1 damage, which won't give us an accurate number. (Not relevant if the enemy used a healing skill.)

Dragon Element: The Element of the dragon that was hit by the skill. (Not relevant if the enemy used a healing skill.)

Buffs / debuffs / damage modifiers: If possible, please try to avoid buffs / debuffs / modifiers that change the damage totals. However, if you cannot avoid them, please record all of the ones that were present during the turn of your attack.

There are two kinds of modifiers when collecting Enemy offensive stats data:
  1. Offensive modifiers on the enemy, such as Rally, Concentration, or Contuse.
  2. Defensive modifiers on your dragon, such as Bolster, Defend, Anticipate, or DEF / MND camping bonuses from the captcha.

* If your flight currently has first place in Dominance, your dragon will incorrectly display as having 1 extra stat, but the stat does not have a true effect. (ie: A dragon with a true DEF of 5 will erroneously display a DEF of 6.) Please record your dragon's true stats.

This only applies if your flight's flag shows up in first place on the left hand of the Dominance screen. Second and third places are not affected, and it doesn't matter which flight is first on the right hand side of the Dominance screen.



Enemy QCK and turn order

Without being able to see stats after Coliseum 2.0, keeping track of QCK is very involved and will require detailed explanation and setup. The QCK / turn order section is not available for now; sorry for the inconvenience.
How to record

You may help by either using a spreadsheet or post in this thread. It is not necessary to do both.

Please only report for enemies for which we are missing data in the skills and enemies tool. This section will only typically be necessary during large Coliseum updates where new enemies are introduced or existing ones are changed. If you'd like to be pinged with new requests, please ask to be added to the ping lists.

Reporting with spreadsheet

The spreadsheet template contains instructions and separate tabs for recording.

Click here for the spreadsheet template (make a copy)

Reporting in thread post

If you'd prefer to post in this thread, please use the following formats.

Enemy KO requirements

Please submit:
Quote:
Enemy:
Skill:
Damage:
STR/INT:
Buffs / debuffs / damage modifiers *: Aim for data without modifiers if possible, but please list if they exist

Enemy: The name of the enemy that was attacked with your dragon's skill.

Skill: The name of the skill that your dragon used to attack.
For easiest calculation, please collect the damage data of Eliminate for STR and Contuse for INT if possible. Otherwise, a different skill is acceptable.

Damage: The regular (non-critical-hit) damage caused to the enemy by your dragon's skill.

STR/INT: The STR and INT of the dragon that used the skill.

Buffs / debuffs / damage modifiers: If possible, please try to avoid buffs / debuffs / modifiers that change the damage totals. However, if you cannot avoid them, please record all of the ones that were present during the turn of your attack.

There are two kinds of modifiers when collecting Enemy KO threshold data:
  1. Offensive modifiers on your dragon, such as Rally, Concentration, Contuse, or STR / INT camping bonuses from the captcha.
  2. Defensive modifiers on the enemy, such as Sear and Petrify.

* If your flight currently has first place in Dominance, your dragon will incorrectly display as having 1 extra stat, but the stat does not have a true effect. (ie: A dragon with a true STR of 117 will erroneously display a STR of 118.) Please record your dragon's true stats.

This only applies if your flight's flag shows up in first place on the left hand of the Dominance screen. Second and third places are not affected, and it doesn't matter which flight is first on the right hand side of the Dominance screen.

Optional:

Enemy total health amounts are required for us to complete the KO threshold data, but to collect this data, it is necessary to view information in the browser console (explained below). The devs have said that it's perfectly okay to collect data in this manner. See this post.

Learn how to help collect enemy total health data here.

Enemy elements and AI

Please submit:

Enemy: The name of the enemy that you encountered.
Element: The element of the enemy (ie: Neutral, Earth, Plague, etc.)
Enemy skills: The names of skills that you have observed the enemy to cast. (ie: Scratch, Contuse, etc.)

Enemy offensive stats

Please submit:
Quote:
Enemy:
Enemy Skill:
Enemy Damage / Healing:
Dragon DEF/MND:
Dragon Element:
Damage modifiers *: Aim for data without buff / debuff modifiers if possible, but please list if they exist

Enemy: The name of the enemy that attacked your dragon or used a healing skill on its allies.

Enemy Skill: The name of the skill that the enemy used to attack or heal with.

Enemy Damage / Healing: The regular (non-critical-hit) damage / healing caused by the enemy's skill.

Dragon DEF/MND: The DEF and MND of the dragon that was hit by the skill. The lower, the better; very high DEF/MND can cause skills to hit for the minimum 1 damage, which won't give us an accurate number. (Not relevant if the enemy used a healing skill.)

Dragon Element: The Element of the dragon that was hit by the skill. (Not relevant if the enemy used a healing skill.)

Buffs / debuffs / damage modifiers: If possible, please try to avoid buffs / debuffs / modifiers that change the damage totals. However, if you cannot avoid them, please record all of the ones that were present during the turn of your attack.

There are two kinds of modifiers when collecting Enemy offensive stats data:
  1. Offensive modifiers on the enemy, such as Rally, Concentration, or Contuse.
  2. Defensive modifiers on your dragon, such as Bolster, Defend, Anticipate, or DEF / MND camping bonuses from the captcha.

* If your flight currently has first place in Dominance, your dragon will incorrectly display as having 1 extra stat, but the stat does not have a true effect. (ie: A dragon with a true DEF of 5 will erroneously display a DEF of 6.) Please record your dragon's true stats.

This only applies if your flight's flag shows up in first place on the left hand of the Dominance screen. Second and third places are not affected, and it doesn't matter which flight is first on the right hand side of the Dominance screen.



Enemy QCK and turn order

Without being able to see stats after Coliseum 2.0, keeping track of QCK is very involved and will require detailed explanation and setup. The QCK / turn order section is not available for now; sorry for the inconvenience.
Bonsai pixels (tofu and tea motif) by miirshroom
[center][size=6][b]Ping lists[/b][/size][/center] [center][size=4][url=http://www1.flightrising.com/forums/gde/2531111#post_35417722]Types of data[/url] | [url=http://www1.flightrising.com/forums/gde/2531111#post_35417724]How to record[/url] | [url=http://www1.flightrising.com/forums/gde/2531111#post_35417728]Current requests[/url] | [url=http://www1.flightrising.com/forums/gde/967048]Main guide[/url] | [url=http://www1.flightrising.com/forums/link?url=https%3A%2F%2Ffir-fr-coli-skills.firebaseapp.com]Tool[/url] Ping lists | [url=http://www1.flightrising.com/forums/gde/2531111#post_35417729]Thanks[/url] [/size][/center] Please ask Sylvandyr if you'd like to be added to the ping lists for new data requests. Being on the ping list does not obligate you to respond to new requests, and you may asked to be removed at any time. Pings are not expected to occur very frequently. They will typically occur on a large Coliseum update where new enemies are added, or if an old zone was revamped and some enemies were changed. [code] @Serpenthyne @Maki @MunchkinLynx [/code]
Ping lists

Please ask Sylvandyr if you'd like to be added to the ping lists for new data requests. Being on the ping list does not obligate you to respond to new requests, and you may asked to be removed at any time.

Pings are not expected to occur very frequently. They will typically occur on a large Coliseum update where new enemies are added, or if an old zone was revamped and some enemies were changed.

Bonsai pixels (tofu and tea motif) by miirshroom
Current requests

This section lists the current requests for data. As we find the stats and attributes of each enemy, they will eventually be removed from this list.

Due to time constraints, it is possible that this section may not be updated straight away; the first thing to receive updates will be the Coliseum skills + enemies tool.

If you notice any discrepancies in the tool for enemies that are not listed here, please feel free to report that in this thread!


Enemy data needed

Currently up-to-date for the new enemies from Night of the Nocturne 2018. Thanks everyone!

---

Please help collect:
  1. None at the moment

Instructions for each section are in this post.

Thank you! :)
Current requests

This section lists the current requests for data. As we find the stats and attributes of each enemy, they will eventually be removed from this list.

Due to time constraints, it is possible that this section may not be updated straight away; the first thing to receive updates will be the Coliseum skills + enemies tool.

If you notice any discrepancies in the tool for enemies that are not listed here, please feel free to report that in this thread!


Enemy data needed

Currently up-to-date for the new enemies from Night of the Nocturne 2018. Thanks everyone!

---

Please help collect:
  1. None at the moment

Instructions for each section are in this post.

Thank you! :)
Bonsai pixels (tofu and tea motif) by miirshroom
Thanks

Special thanks to our volunteers for collecting all the data that made it possible for us to infer stats post-Coli-2.0!

Our lovely volunteers:
Maki, Serpenthyne, MunchkinLynx, Lililira

Thank you to FR Devs for letting us know that viewing any visible data available to the browser is absolutely okay.
Thanks

Special thanks to our volunteers for collecting all the data that made it possible for us to infer stats post-Coli-2.0!

Our lovely volunteers:
Maki, Serpenthyne, MunchkinLynx, Lililira

Thank you to FR Devs for letting us know that viewing any visible data available to the browser is absolutely okay.
Bonsai pixels (tofu and tea motif) by miirshroom
Using the Browser Console

Sometime between August and November 2019, devs updated the available data stream again to make the information even less human readable. Therefore, the guide below is no longer accurate. I will probably have to collect this information myself since it is difficult to explain what to look for.

Enemy total health amounts are required for us to complete the KO threshold data, but to collect this data, it is necessary to view information in the browser console (explained below). The devs have said that it's perfectly okay to collect data in this manner. See this post.

Before Coli 2.0, all of the monster stat data was directly available in the browser console. The method described below is the way that we used to collect data. Now only the enemy total health is exposed, but it's a very necessary piece of data for KO thresholds and I'm grateful that it's still there!

Viewing and submitting data
  1. Open an up-to-date Google Chrome browser.
  2. Press F12 to make the Browser Console visible. You must perform this step before visiting the Coliseum.
  3. At the uppermost section of the Browser Console, select the Network tab if you haven't already. (Other tabs may include Elements, Console, Sources, Performance, Memory, etc.)
  4. To view the next desired options, you may or may not need to click to toggle your Filter button. It looks like a tiny red funnel icon. See screenshot.
  5. If your Filter button is toggled correctly, the menu below it will be visible. (In the screenshot, it's the list of options saying All, XHR, JS, CSS, Img, Media, Font, WS, Manifest, Other). Make sure you select the WS option.
  6. Click the Coliseum link. You should now be able to see an entry pop up in the Websockets window. See screenshot. Click the link.
  7. Clicking the long websocket link should bring up an additional section. See screenshot. Make sure the Frames tab in the new section is selected. (In some versions, Frames is called Messages instead.)
  8. Enter the venue in question. You will notice the Frames keep updating (tab is called Messages in some versions); scroll up through the entries until you find something that looks like this screenshot. It's usually the line in which you can catch a glimpse of the Coliseum venue name. You can click to expand the little downward arrows to get some of the nested information to display. Sometimes you won't get this start-of-battle data. If you seem to not have received it and feel like you're just scrolling through an endless list of incomprehensible numbers, either move on to a new battle or cast a buff like Haste to get a similar data block that contains "instance id" and some info, copying that instead. (The info won't be as comprehensive but it can still contain health amounts.)
  9. Right click on the main line in the frames section and click Copy message. You must use this feature instead of attempting to use your computer shortcuts such as Ctrl+C. See screenshot. You may get something like this:

    42["5717b911e268bcc37c78f76a2a6f4b0d197edebea411e115b9d0f8d897c8d5bf",["thunderhead_savanna",[[513,[435,60],408,"Flesh Forager",14,"2",9,14,1000,0,false,false],[91,[495,140],405,"Dire Vulture",14,"2",0,14,980,0,false,false],[339,[555,220],408,"Flesh Forager",14,"2",9,14,1000,0,false,false]],[ [846,2519972,"Elrethyl",1526383,[119,5,8,6,72,5,5],[[495,1],[1193,53],[498,4],[526,32],[521,27],[674,0],[674,0],[674,0],[687,57],[687,57]],false,9,[870,870,0],25,"dragon",8]],false,21] ]

Paste this message for me into this thread and you're done! The idea is to encounter the different enemies in the packs, that way we have full coverage of the monsters. It would be awesome if you could label each message with the pack that you encountered (for quicker browsing), but the participants can be read from the full message.

What the data contains

We seem to receive a few more stats just enemy Health, but the arrays for your own dragons vs. the arrays for the enemies are populated slightly differently.

For comparison:

Your dragon's array

0: 846
1: 2519972
2: "Elrethyl"
3: 1526383
4: [119,5,8,6,72,5,5]
5: [ [495,1],[1193,53],[498,4],[526,32],[521,27],[674,0],[674,0],[674,0],[687,57],[687,57] ]
6: false
7: 9
8: [870,870,0]
9: 25
10: "dragon"
11: 8

0: Instance ID, each participant in the battle has its own to remain uniquely-identified
1: Dragon ID
2: Dragon Name
3: ?
4: Array of dragon stats, listed as STR, INT, AGI, VIT, QCK, DEF, MND
5: Something to do with coordinates / animation frames maybe?
6: Some flag / property boolean
7: Your dragon's Element ID (0 = Neutral, 9 = Arcane, etc.)
8: Something to do with health?
9: Level
10: The type of battle participant
11: ?

An enemy's array (both normal and boss)

0: 513
1: [435,60]
2: 408
3: "Flesh Forager"
4: 14
5: "2"
6: 9
7: 14
8: 1000
9: 0
10: false
11: false

0: 650
1: [416,65]
2: 419
3: "Rockback Charger"
4: 14
5: "2"
6: 1
7: 14
8: 5640
9: 0
10: false
11: false

0: 343
1: [465,100] in one possible Training Fields pack, [435,60] in one possible Woodland Path pack
2: 93
3: "Crimson Emperor"
4: 14
5: "2"
6: 6
7: 2
8: 180
9: 0
10: true
11: false

0: Instance ID, each participant in the battle has its own to remain uniquely-identified
1: Position coordinates
2: The enemy's Real ID
3: Enemy name
4: Unclear. Woodland Path enemies have shown values of 12 and 14. Thunderhead Savanna has also shown values of 14. Could be some art type or something.
5: Perhaps "type of participant", like index 10 of dragon array
6: Element ID (0 = Neutral, 1 = Earth, 9 = Arcane, etc.)
7: Enemy Level
8: Total Health
9: ?
10: Whether the enemy floats in the air
11: ?

You'll notice that unlike the dragons, the enemies don't seem to send all their stats.
Using the Browser Console

Sometime between August and November 2019, devs updated the available data stream again to make the information even less human readable. Therefore, the guide below is no longer accurate. I will probably have to collect this information myself since it is difficult to explain what to look for.

Enemy total health amounts are required for us to complete the KO threshold data, but to collect this data, it is necessary to view information in the browser console (explained below). The devs have said that it's perfectly okay to collect data in this manner. See this post.

Before Coli 2.0, all of the monster stat data was directly available in the browser console. The method described below is the way that we used to collect data. Now only the enemy total health is exposed, but it's a very necessary piece of data for KO thresholds and I'm grateful that it's still there!

Viewing and submitting data
  1. Open an up-to-date Google Chrome browser.
  2. Press F12 to make the Browser Console visible. You must perform this step before visiting the Coliseum.
  3. At the uppermost section of the Browser Console, select the Network tab if you haven't already. (Other tabs may include Elements, Console, Sources, Performance, Memory, etc.)
  4. To view the next desired options, you may or may not need to click to toggle your Filter button. It looks like a tiny red funnel icon. See screenshot.
  5. If your Filter button is toggled correctly, the menu below it will be visible. (In the screenshot, it's the list of options saying All, XHR, JS, CSS, Img, Media, Font, WS, Manifest, Other). Make sure you select the WS option.
  6. Click the Coliseum link. You should now be able to see an entry pop up in the Websockets window. See screenshot. Click the link.
  7. Clicking the long websocket link should bring up an additional section. See screenshot. Make sure the Frames tab in the new section is selected. (In some versions, Frames is called Messages instead.)
  8. Enter the venue in question. You will notice the Frames keep updating (tab is called Messages in some versions); scroll up through the entries until you find something that looks like this screenshot. It's usually the line in which you can catch a glimpse of the Coliseum venue name. You can click to expand the little downward arrows to get some of the nested information to display. Sometimes you won't get this start-of-battle data. If you seem to not have received it and feel like you're just scrolling through an endless list of incomprehensible numbers, either move on to a new battle or cast a buff like Haste to get a similar data block that contains "instance id" and some info, copying that instead. (The info won't be as comprehensive but it can still contain health amounts.)
  9. Right click on the main line in the frames section and click Copy message. You must use this feature instead of attempting to use your computer shortcuts such as Ctrl+C. See screenshot. You may get something like this:

    42["5717b911e268bcc37c78f76a2a6f4b0d197edebea411e115b9d0f8d897c8d5bf",["thunderhead_savanna",[[513,[435,60],408,"Flesh Forager",14,"2",9,14,1000,0,false,false],[91,[495,140],405,"Dire Vulture",14,"2",0,14,980,0,false,false],[339,[555,220],408,"Flesh Forager",14,"2",9,14,1000,0,false,false]],[ [846,2519972,"Elrethyl",1526383,[119,5,8,6,72,5,5],[[495,1],[1193,53],[498,4],[526,32],[521,27],[674,0],[674,0],[674,0],[687,57],[687,57]],false,9,[870,870,0],25,"dragon",8]],false,21] ]

Paste this message for me into this thread and you're done! The idea is to encounter the different enemies in the packs, that way we have full coverage of the monsters. It would be awesome if you could label each message with the pack that you encountered (for quicker browsing), but the participants can be read from the full message.

What the data contains

We seem to receive a few more stats just enemy Health, but the arrays for your own dragons vs. the arrays for the enemies are populated slightly differently.

For comparison:

Your dragon's array

0: 846
1: 2519972
2: "Elrethyl"
3: 1526383
4: [119,5,8,6,72,5,5]
5: [ [495,1],[1193,53],[498,4],[526,32],[521,27],[674,0],[674,0],[674,0],[687,57],[687,57] ]
6: false
7: 9
8: [870,870,0]
9: 25
10: "dragon"
11: 8

0: Instance ID, each participant in the battle has its own to remain uniquely-identified
1: Dragon ID
2: Dragon Name
3: ?
4: Array of dragon stats, listed as STR, INT, AGI, VIT, QCK, DEF, MND
5: Something to do with coordinates / animation frames maybe?
6: Some flag / property boolean
7: Your dragon's Element ID (0 = Neutral, 9 = Arcane, etc.)
8: Something to do with health?
9: Level
10: The type of battle participant
11: ?

An enemy's array (both normal and boss)

0: 513
1: [435,60]
2: 408
3: "Flesh Forager"
4: 14
5: "2"
6: 9
7: 14
8: 1000
9: 0
10: false
11: false

0: 650
1: [416,65]
2: 419
3: "Rockback Charger"
4: 14
5: "2"
6: 1
7: 14
8: 5640
9: 0
10: false
11: false

0: 343
1: [465,100] in one possible Training Fields pack, [435,60] in one possible Woodland Path pack
2: 93
3: "Crimson Emperor"
4: 14
5: "2"
6: 6
7: 2
8: 180
9: 0
10: true
11: false

0: Instance ID, each participant in the battle has its own to remain uniquely-identified
1: Position coordinates
2: The enemy's Real ID
3: Enemy name
4: Unclear. Woodland Path enemies have shown values of 12 and 14. Thunderhead Savanna has also shown values of 14. Could be some art type or something.
5: Perhaps "type of participant", like index 10 of dragon array
6: Element ID (0 = Neutral, 1 = Earth, 9 = Arcane, etc.)
7: Enemy Level
8: Total Health
9: ?
10: Whether the enemy floats in the air
11: ?

You'll notice that unlike the dragons, the enemies don't seem to send all their stats.
Bonsai pixels (tofu and tea motif) by miirshroom
Reserve.
Reserve.
Bonsai pixels (tofu and tea motif) by miirshroom
Reserve.
Reserve.
Bonsai pixels (tofu and tea motif) by miirshroom
Reserve.
Reserve.
Bonsai pixels (tofu and tea motif) by miirshroom
1 2 3 4 5 6