# FFLogs huge bug?

**URL:** https://forums.combatlogforums.com/t/fflogs-huge-bug/1574
**Category:** FF Logs
**Created:** [October 26, 2016, 9:01pm UTC](https://forums.combatlogforums.com/t/fflogs-huge-bug/1574 "2016-10-26T21:01:31Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Aya](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@Aya](https://forums.combatlogforums.com/u/Aya)
#### Post date: [October 26, 2016, 9:01pm UTC](https://forums.combatlogforums.com/t/fflogs-huge-bug/1574/1 "2016-10-26T21:01:31Z")

</div>

[https://www.fflogs.com/reports/Z7JKqTGcjNmgwrMn#fight=8](https://www.fflogs.com/reports/Z7JKqTGcjNmgwrMn#fight=8)  
It looks like all of their casts are doubled. The encounter was 9:42. Dragonfire Dive is on a 120 second cooldown, so a max of 4.85 casts. Blood for blood is an 80 second cooldown, so they would have gotten 7.27 casts of blood for blood. On their parse, they did 8 casts of Dragonfire, and 12 blood for blood. There isn’t an astrologian, so no spear.

The deaths are also doubled.

If you compare the total casts of these two parses:

[https://www.fflogs.com/reports/Z7JKqTGcjNmgwrMn#fight=8&type=damage-done&source=7](https://www.fflogs.com/reports/Z7JKqTGcjNmgwrMn#fight=8&type=damage-done&source=7)

[https://www.fflogs.com/reports/k7m9FARdLwzaZNhC#fight=5&type=damage-done&source=4](https://www.fflogs.com/reports/k7m9FARdLwzaZNhC#fight=5&type=damage-done&source=4)

It should actually be impossible to cast double in just two more minutes.

Could this be affecting their total damage output?

---

<div class="post-metadata">

### Author: ![Hoshi](https://avatars.discourse-cdn.com/v4/letter/h/bbce88/32.png) [@Hoshi](https://forums.combatlogforums.com/u/Hoshi)
#### Post date: [October 27, 2016, 12:13am UTC](https://forums.combatlogforums.com/t/fflogs-huge-bug/1574/2 "2016-10-27T00:13:01Z")

</div>

There was a similar bug on a few logs I saw last tier, if you look at the events tab everything is indeed doubled.  
[https://www.fflogs.com/reports/Z7JKqTGcjNmgwrMn#fight=8&type=damage-done&view=events](https://www.fflogs.com/reports/Z7JKqTGcjNmgwrMn#fight=8&type=damage-done&view=events)

---

<div class="post-metadata">

### Author: ![Aya](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@Aya](https://forums.combatlogforums.com/u/Aya)
#### Post date: [October 27, 2016, 3:31am UTC](https://forums.combatlogforums.com/t/fflogs-huge-bug/1574/3 "2016-10-27T03:31:20Z")

</div>

Does that mean the DPS would be doubled as a result? Or does that simply mean things are registering twice as a weird bug? This could cause some really big issues for all star points and similar things if it’s the former!

---

<div class="post-metadata">

### Author: ![Kihra](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.combatlogforums.com/kihra/32/1116_2.png) [@Kihra](https://forums.combatlogforums.com/u/Kihra)
#### Post date: [October 27, 2016, 5:04am UTC](https://forums.combatlogforums.com/t/fflogs-huge-bug/1574/4 "2016-10-27T05:04:20Z")

</div>

It’s a bug with the logging itself, not with FFLogs. It’s very rare. Just let me know when it happens and I will blacklist.

---

<div class="post-metadata">

### Author: ![Aya](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@Aya](https://forums.combatlogforums.com/u/Aya)
#### Post date: [October 27, 2016, 5:44am UTC](https://forums.combatlogforums.com/t/fflogs-huge-bug/1574/5 "2016-10-27T05:44:36Z")

</div>

Oh alright! Thank you for the response!  
It looks like all three of these parses:  
[https://www.fflogs.com/reports/vWhGcYgLr8pTR6qd#fight=28&type=damage-done&view=events](https://www.fflogs.com/reports/vWhGcYgLr8pTR6qd#fight=28&type=damage-done&view=events)  
[https://www.fflogs.com/reports/vWhGcYgLr8pTR6qd#fight=30&type=damage-done&view=events](https://www.fflogs.com/reports/vWhGcYgLr8pTR6qd#fight=30&type=damage-done&view=events)  
[https://www.fflogs.com/reports/vWhGcYgLr8pTR6qd#fight=33&type=summary&view=events](https://www.fflogs.com/reports/vWhGcYgLr8pTR6qd#fight=33&type=summary&view=events)  
have that bug.
