Hey all we've spent a good amount of years attempting to filter through the issues CCS has by ear/word of mouth/randomly helpful forum post and largely as the system gets older, larger and has more players it gets harder to relevantly identify actual bugs and balance issues over the general white noise of player base opinions.
So in that effort we've removed the CCS Bugs/Suggestions forum....because it simply was not helpful. If you wish to simply discuss how you feel about CCS you can use the CCS General Discussion Forum to do so.
But for bugs and suggestions we've now implemented Mantis Bug Tracker into the website, allowing for more accurate reporting of bugs and issues with the CCS system which will allow us to actually track the issues with the system more effectively and address bugs and issues that actually have good reporting data in regards to them, rather than continuing to try to work out what the issues are amidst a stream of arguments and opinions.
You can access the new CCS BugTracker by clicking the link here in this news post. Or you can find the CCS BugTracker available under the Community Combat System menu on the main page.
Only registered site member may use the BugTracker. And please keep in mind that reporting a new issue and simply typing "CCS R BROKE MY XPS" into the description field is not going to end up getting a resolution. We need as much data as you can give us on what the problem is. So please provide the following data when reporting issues.
Hopefully with this new system in place we'll actually be able to drill down and solidify our view on system affecting issues so we can more respond to bugs and issues with the system more efficiently.
Also in regards to CCS 1.0.5 there are test meters in play, we've eliminated several reported bug issues but there are a couple that are still outstanding that we need to work on. So now would be the time to get some practice with the CCS BugTracker, if you want to give us any data you may have on bug or balance issues for the next upcoming release!
Thanks all. Appreciate your time.
So in that effort we've removed the CCS Bugs/Suggestions forum....because it simply was not helpful. If you wish to simply discuss how you feel about CCS you can use the CCS General Discussion Forum to do so.
But for bugs and suggestions we've now implemented Mantis Bug Tracker into the website, allowing for more accurate reporting of bugs and issues with the CCS system which will allow us to actually track the issues with the system more effectively and address bugs and issues that actually have good reporting data in regards to them, rather than continuing to try to work out what the issues are amidst a stream of arguments and opinions.
You can access the new CCS BugTracker by clicking the link here in this news post. Or you can find the CCS BugTracker available under the Community Combat System menu on the main page.
Only registered site member may use the BugTracker. And please keep in mind that reporting a new issue and simply typing "CCS R BROKE MY XPS" into the description field is not going to end up getting a resolution. We need as much data as you can give us on what the problem is. So please provide the following data when reporting issues.
- Helpful Reporting Data:
- Your SL/CCS Player name, and the names of any other players that experienced the bug when it occurred.
- What the bug appeared to do, a descriptive account of what occurred and how it occurred and the consequences of its occurrence.
- Please supply, if you can, a method of reproducing the bug you are reporting. If you have encountered a bug, please attempt to reproduce it again so you can tell us exactly how you made it happen. This helps immensely in regards to allowing us to focus on what parts of the system may be responsible for the problem you are experiencing.
- Please supply the Second Life viewer version you are using, this will not always be relevant but can help us to determine if there is an issue with a viewer as compared to other viewers if any arise.
- DO NOT report bugs with CCS 3rd Party Developer weapons on this tracker. Bugs with API Developer Weapons should be reported to the designer themselves, this system is only for tracking and attempting to more accurately identify bugs with the CCS system itself.
- DO NOT report "cheaters" via the CCS BugTracker, as that is not the purpose of this tracking system. If you suspect someone is cheating please contact your local GM staff in the sims you're in or a member of the CCS administrative staff.
- You may use the CCS BugTracker to report perceived issues with CCS combat mechanical balance issues, but keep in mind that these reports will not be treated with the same level of importance as actual bug reports, they will be assigned to me or Melanie to review in hand with the system's overall balance and will be applied during system updates if found to be relevant reports.
Hopefully with this new system in place we'll actually be able to drill down and solidify our view on system affecting issues so we can more respond to bugs and issues with the system more efficiently.
Also in regards to CCS 1.0.5 there are test meters in play, we've eliminated several reported bug issues but there are a couple that are still outstanding that we need to work on. So now would be the time to get some practice with the CCS BugTracker, if you want to give us any data you may have on bug or balance issues for the next upcoming release!
Thanks all. Appreciate your time.
Hey all I worked some bug issues with Melanie over the weekend and we're working on getting the 1.0.5 update out as soon as possible.
I also stated in the forums that I expected to have the 1.0.5 update out no later than Tuesday of this week and then was politely reminded by my family that its Thanksgiving and they sort of expect me to show up for dinner.
So as you might expect as much as I'd love to knock out a meter release on the date I stated in the forums, you might understand that I don't have any intentions of spending a 14 hour day in SL dealing with post release support work when I'm supposed to be spending time with my family. And I don't expect this of CCS Admins or GMs either.
So I'll be releasing the 1.0.5 update after Thanksgiving, no specific date specified but fairly soon. I've got a fair block of free time to finish polishing off the fixes we did and do a nice full race/class balance analysis after Thanksgiving, so going to hold off for a little bit on this release til then.
Appreciate your patience and understanding on this matter. And have a happy holiday for those of you celebrating one this week.
I also stated in the forums that I expected to have the 1.0.5 update out no later than Tuesday of this week and then was politely reminded by my family that its Thanksgiving and they sort of expect me to show up for dinner.
So as you might expect as much as I'd love to knock out a meter release on the date I stated in the forums, you might understand that I don't have any intentions of spending a 14 hour day in SL dealing with post release support work when I'm supposed to be spending time with my family. And I don't expect this of CCS Admins or GMs either.
So I'll be releasing the 1.0.5 update after Thanksgiving, no specific date specified but fairly soon. I've got a fair block of free time to finish polishing off the fixes we did and do a nice full race/class balance analysis after Thanksgiving, so going to hold off for a little bit on this release til then.
Appreciate your patience and understanding on this matter. And have a happy holiday for those of you celebrating one this week.
Hey all just an update since people are apparently reading our posting from September and drawing direct hard line dates of release from it.
My approximation of completion for API 3.0 and CCS 1.0.5 by October has been offset by some unforeseen events in Real Life™. Melanie has had some issues with time and availability over the last several months, Maldoror has completed most of API 3.0's system interface and we're currently waiting on input on that from Melanie.
I have implemented several fixes in for CCS 1.0.5 but I am also holding on Melanie to do a summary overhaul based on what I've fixed and to address a couple of issues with how the meter intepreter talks to the CCS database.
Overall while I was hoping for October, we've slipped past that and it was due to situations beyond our control. Please remain patient while we continue to work on getting these updates finalized. And please keep in mind that I'm also working on a major technical revamp of the CoLA sim while doing all this plus taking care of the community in world. Its a busy end of the year all around, so please understand that while I may have been hopeful we'd have completed our intended updates by the end of October, the updates will take a bit longer before we are ready to push them live.
My apologies for any inconvenience. And thank you for your patience and understanding.
My approximation of completion for API 3.0 and CCS 1.0.5 by October has been offset by some unforeseen events in Real Life™. Melanie has had some issues with time and availability over the last several months, Maldoror has completed most of API 3.0's system interface and we're currently waiting on input on that from Melanie.
I have implemented several fixes in for CCS 1.0.5 but I am also holding on Melanie to do a summary overhaul based on what I've fixed and to address a couple of issues with how the meter intepreter talks to the CCS database.
Overall while I was hoping for October, we've slipped past that and it was due to situations beyond our control. Please remain patient while we continue to work on getting these updates finalized. And please keep in mind that I'm also working on a major technical revamp of the CoLA sim while doing all this plus taking care of the community in world. Its a busy end of the year all around, so please understand that while I may have been hopeful we'd have completed our intended updates by the end of October, the updates will take a bit longer before we are ready to push them live.
My apologies for any inconvenience. And thank you for your patience and understanding.