Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"only one evoker, yonk bombardments ok" printout whenever combat starts with an Augmentation Evoker in group #862

Open
Baeligg opened this issue Nov 8, 2024 · 4 comments

Comments

@Baeligg
Copy link

Baeligg commented Nov 8, 2024

Game and Details! version
Retail, Details VTC 13819 release 11.0.5

Describe the bug

  • Steps to Reproduce (what did you do to make the bug happen): Enter combat in a group with an Augmentation Evoker, possibly only in instances
    Edit: Any evoker apparently, wasn't doing it at first on my devastation but now it is

  • Result (what happens when you follow the steps above): Printout "only one evoker, yonk bombardments ok: (Evoker's name) Player-(series of numbers and letters)"

  • Expected (what you think the expected behavior would be when following the steps): Not that

  • When the bug started (a date, wow path release, details update, etc)? Most recent update

  • Additional information: Tested with only Details enabled as well. Combat log included, dunno if it'll matter

Lua Error
Post here lua errors, if you aren't getting any, use /console scriptErrors 1
No LUA errors

Screenshots
WoWScrnShot_110724_201121

Combat Log
WoWCombatLog-110724_214756.txt

Other Information
If necessary, add more info here.

@pobiega
Copy link

pobiega commented Nov 8, 2024

The printout is here:

print("only one scaler commander found, yoinking bombardments damage for:", bombardment_stuff.evoker_name)

Seems like a debug-printout that was accidentally left in.

@raptormama
Copy link

raptormama commented Nov 8, 2024

It does it with only one preservation evoker as well. I've seen this with both myself and a friend.

Commented out line 5772 and 5810 last night to disable the message, and am surprised this got pushed to release.

@thefowles1
Copy link

thefowles1 commented Nov 8, 2024

It does it with any one evoker period. Did it while on my devoker in every instance without a second, and did it while on a non-evoker that had only one otherwise.

Maybe this will seem ignorant, but this hardly seems like something to be surprised about. Programming is a lot of work and even something simple as one singular character can make or break something.
No biggie. In fact, the phrasing makes me chuckle. Yonk.

@Tercioo
Copy link
Owner

Tercioo commented Nov 8, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants