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

🐛 Map crash after recent gambit changes. #6974

Closed
3 tasks done
Samantharia opened this issue Feb 6, 2025 · 5 comments · Fixed by #6986
Closed
3 tasks done

🐛 Map crash after recent gambit changes. #6974

Samantharia opened this issue Feb 6, 2025 · 5 comments · Fixed by #6986
Labels
bug Something isn't working

Comments

@Samantharia
Copy link

I affirm:

  • I understand that if I do not agree to the following points by completing the checkboxes my issue will be ignored.
  • I have read and understood the Contributing Guide and the Code of Conduct.
  • I have searched existing issues to see if the issue has already been opened, and I have checked the commit log to see if the issue has been resolved since my server was last updated.

OS / platform the server is running (if known)

Windows 10

base

Steps to reproduce

Call a trust that uses best against target magic and as soon as they cast, map server crash.

#6967

Expected behavior

Trust can cast best against target without a crash.

@Samantharia Samantharia added the bug Something isn't working label Feb 6, 2025
@WinterSolstice8
Copy link
Contributor

Confirmed with Lehko, looks like he's trying to cast spell id 0 for some reason?

@Samantharia
Copy link
Author

I know people are gonna jump on the butthurt train for this - but please playtest changes. This one was easy.

@WinterSolstice8
Copy link
Contributor

Image

@WinterSolstice8
Copy link
Contributor

Comments like that make me not want to fix it anymore, fyi. enjoy your butthurt btw

@LandSandBoat LandSandBoat locked as too heated and limited conversation to collaborators Feb 6, 2025
@zach2good
Copy link
Contributor

I know people are gonna jump on the butthurt train for this - but please playtest changes. This one was easy.

I've been umm-ing and ahh-ing about whether or not I should reply to this also. It is unreasonable for us (the group of maintainers) to pull down and hand-test every submission that comes in. We have CI to style-check, build on all platforms, look for obvious code errors and common bad patterns, and run a basic suite of smoke tests - but that doesn't capture every aspect of things that might be changing. We have to have faith in the contributors that get off their butts and send in code to us and jump through all the quality gates we set - which are already quite high for this sort of project.

For a reference of how fast the repo is changing, here is the velocity of the repo over the last week:
Image

Your bug report absolutely would have been fixed quickly and without fuss, probably within an hour or two, if you hadn't decided to be derisive for no reason.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants