-
-
Notifications
You must be signed in to change notification settings - Fork 567
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
broken Fiery Touch [$5 awarded] #968
Comments
@cxong I think one of the changes you made broke this specific ability, might be something simple. |
If that's true, then I think that's 👍 to setting up automated unit tests. Have you thought about what framework we should use? I think it comes down to Jasmine or Mocha. The sooner we start, the less we'll see bugs like this. |
Hehe, indeed. Like I mentioned before, I think Mocha does things better. Will do a little more research today though. |
Tested it and it works. Make sure you assign yourself to BS so I can award the bounty, @cxong . Can't go under $5 afaik for issues though xD |
Can't award the bounty cause you didn't submitted a patch after you "started working on it" on BS... @cxong sigh |
So what do I need to do? Submit a dummy patch? |
@cxong Yeah, I think so. Patch that other thing and it might work if you tag this one too; We'll have to see xD BS has a 5$ minimum per issue, so I might need to group the small "low hanging fruits" issues or leave them for coders who want crediting / experience only. |
This is a dummy patch just to get the bounty for #968
@cxong Guess you can try clicking the "Claim Bounty" button https://www.bountysource.com/issues/34492341-broken-fiery-touch |
Can't attack any more units using Abolished's Fiery Touch.
--- The **[$5 bounty](https://www.bountysource.com/issues/34492341-broken-fiery-touch?utm_campaign=plugin&utm_content=tracker%2F260151&utm_medium=issues&utm_source=github)** on this issue has been claimed at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F260151&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: