I'm just going to post a reminder here...

The bug board is there so we can go through the 370 posts there and cherry pick the horribly broken or easy to fix bugs and get them fixed.

If you think something is over powered, or badly designed, or whatever, that's not what the bug board is for, and in the future I'm just going to delete those so I can wade through the mountain of bug reports a little easier. It's also a crappy place to have a back in forth discussion, because this forum software sucks, and I have to put a check mark next to each of those posts and scroll all the way to the bottom and submit them and then edit them if they have sensitive info, etc.

So in short:
You post bug, we post fixed or not a bug.
Something that is clearly broken and reproducible will get looked at first.
If your bug doesn't get a response, it's probably because it's a hard one to fix, or it wasn't reproducible easily, or something of that sort, and it's been skipped for something easier for the time being, but someone will come back to it.

Overpowered, underpowered, I don't get what this skill does, this ability blows, etc all goes in this forum here, gameplay... I'm sure there's lots of those now that a bunch of new shaman abilities are in.

Thanks!

We've got lots of programmers/developers who still play this game (myself included)... couldn't we just move this to like a bugzilla or trac public project and have people help wade through this for you or mark priorities? I never really understood the point of hiding every post either. If the forum software sucks... there's about ten million options out there that are better.

The even more crazy option would be to just post a file and say "fix this bug" and let people fix it. Kind of like how Netflix has a contest to improve their search engine... maybe post that thousands of line damage function and let us fix it so its not a pile of crap. Problem is someone would probably be paranoid about stealing the code or knowing the inner workings...

Just sucks you've got all this crap to deal with, and you're one of maybe two or three people total who would fix it (and probably code all the other awesome new things) when there's a whole lot of us on the other side.

Sucks too that you've got to basically decide if you want to play the game or not, never got why Immortal apps can't have mortals and have to write descriptions/area code when someone just might be a good coder.

CF imms realistically aren't going to track people down and sue them for copyright infringement or license violations. It's just not worth it - going to court is expensive and CF'ers live all over the world. That's why it has to be the trust system and given the nature of the player base, I wouldn't trust many people either.

In terms of some alternatives to that, Atlassian has a really nice suite of tools for dealing with code. I'd highly suggest swapping to Git/Stash + Fisheye if you guys haven't done so yet. I could walk you through a sample merge workflow with continuous integration that has saved our teams lots of time. With Atlassian you might be able to get open source licensing give you're a not for profit.

JIRA is obviously great but when it comes to untangling lots of code and managing code quality I'm a big fan of Fisheye and Crucible.

https://www.atlassian.com/software/fisheye/overview

I'm also a big fan of Git. What we do for our projects is create a "branch-per-ticket". What this allows us to do is have a local branch for any modification to the software. Once that is ready for code review, we submit pull requests and the dev leads review and approve or decline the code update. For some of our larger clients our teams are upwards of 30 people, 15 full time devs and we still get through our morning merges in about 30 minutes, so it's not too bad at all. Having a branch per ticket allows you to cherry pick what you want to roll out and when, pretty much push-button.

To apply this to the CF model, if you were able to get free Atlassian licensing, you'd use JIRA to submit bug reports. You could then edit your own bug reports, in case you mess something up. Internally or publically admins or players could vote up/down bugs. These could then get hacked up and sprinted out using Stash/Git/Jenkins etc for release automation and management.

Basically, using the tools to do as much work as possible and minimize your own time. This of course only applies if you can get free licensing, because the out of pocket costs are non-trivial for commercial licensing.

https://www.atlassian.com/software/views/community-license-request

From :

Death_Claw/Eskelian, part time CF junky, full time tech lead.