Kreolix / CovenantMissionHelper

10 stars 8 forks source link

Wrong prediction - easy way to upload combat logs: #32

Closed zalewskigrzegorz closed 2 months ago

zalewskigrzegorz commented 3 years ago

Hi, it's happened for me today two times in a row: image image It's hard to compare combat logs because I can t copy text from this window. There is a way to optimize the process of reporting this kind of bug? (eq. save combat log / simulated combat log output to some log file) I believe this happened because simulation doesn't match the current game state, but it's hard to found differences just by screenshot.

DaemoniKira commented 2 years ago

I'm having exactly this same issue as well.

No screenshots, but I just had 2 out of 7 missions fail when the AddOn said they would win. Yesterday I had 1 mission out of ~5 that failed when the AddOn said it would win. And I've had it happen once in the last couple days on another character in another Covenant as well... so it's not just one Covenant/Companion group. The character on which I had 2 missions fail in one "session" is Necrolord. The character on which I had 1 mission fail recently is Venthyr. I have not logged into my Kyrian or Night Fae characters in a while, so I don't know if they are having issues too -- but I'd imagine that they are.

I am sending out my missions the same way I've always sent them out, using the same methods I always have. Since I installed this AddOn near the beginning of Shadowlands, I have never had an issue like this before now -- I've never had a single mission come back as a Loss, when it said it would be a Win.

And I don't send out the mission if the AddOn has an Orange-text "approximately this percent ("~xx%") chance of a Win" prediction. I make sure it is Green and 100% a Win. So I don't understand how these can be coming back as Losses... and so frequently.

Please address. It's frustrating spending time on the Table only to have them come back as losses, inexplicably.

zalewskigrzegorz commented 2 months ago

I'm closing this issue due to inactivity. If further assistance is needed, please feel free to reopen or create a new.