I think I reproduced the eudaemon patrol bug described here: http://forum.r2games.com/forum/brows...-patrol-glitch
I was setting up a patrol needing 2000 dark resistance, when I noticed that one of my extra rangers had enough to cover the ~400 my blood demon was short, so I added them both and started. Immediately, the second and third level rewards turned red, and patrol time was only 3hrs (see screenshot #1)
The bug is that Ranger1 never had that much resistance (see screenshot #2 - no changes made between #1 and #2). I believe what happened was that Ranger1 was set as a sub-eudaemon earlier in the day, but was replaced (notice screenshot #1 shows an oracle as sub-eudy).
I'll have to test later when I have an open patrol if the active sub-eudaemon can be used properly with the added sylph resistance, but there's definitely a bug with the way the patrol screen is showing the resistance here.
Refreshing the game does clear it up, at least. But it seems to persist for every eudaemon assigned as a sub-eudaemon until you do refresh.
I was setting up a patrol needing 2000 dark resistance, when I noticed that one of my extra rangers had enough to cover the ~400 my blood demon was short, so I added them both and started. Immediately, the second and third level rewards turned red, and patrol time was only 3hrs (see screenshot #1)
The bug is that Ranger1 never had that much resistance (see screenshot #2 - no changes made between #1 and #2). I believe what happened was that Ranger1 was set as a sub-eudaemon earlier in the day, but was replaced (notice screenshot #1 shows an oracle as sub-eudy).
I'll have to test later when I have an open patrol if the active sub-eudaemon can be used properly with the added sylph resistance, but there's definitely a bug with the way the patrol screen is showing the resistance here.
Refreshing the game does clear it up, at least. But it seems to persist for every eudaemon assigned as a sub-eudaemon until you do refresh.
Comment