View Full Version : Reviewing Combat Revamped Skills

06-21-2005, 01:50 AM
<DIV>When SOE releases the new Combat Revamp skills to the test server, I think they should release a complete list of every skill, apprentice I to Master I.</DIV> <DIV> </DIV> <DIV>This would allow players who do not play on the test server to review the changes so that glaring oversights can be caught before they leave the test server.  Often times a skill is not really bugged, it just has a design flaw, and design flaws can often be quickly picked up by a human reviewer.  You can hardly blame them for flaws like this occuring when you have the number of skills they do, compared to the number of eyes they have to review those skills.  (24 sub-classes x ~50 spells x 6 spell grades (app I - Master I) = Too many skills to review by a small team).  </DIV> <DIV> </DIV> <DIV>If SOE doesn't release this information, it will take the playerbase a while before the information is extracted from the test server.  That is why I think SOE should take the initiative and release this information themselves so that they can get the eyes of the entire community looking at these lists for flaws.  I am suggesting this now, long before the combat revamp release because this may require a web dev depending on how they go about it.</DIV> <DIV> </DIV> <DIV>SOE, Help us... help you.</DIV> <DIV> </DIV> <DIV>- Dehah</DIV>

06-21-2005, 01:58 AM
This is an interesting idea actually.  I wouldn't mind helping with the necromancer spells.  It might be a lot of work to just compile the data though into a form we could all read.  I don't see SOE doing this but it could be cool. <div></div>

06-21-2005, 02:01 AM
<P>You mean they should.... shudder... document the changes???</P> <P> </P> <P>Don't hold yer breathe... take a look at both the origional manual and online manual that came with the game... EQII does not have a very good track record about documentation...</P>

06-21-2005, 01:46 PM
I love this idea.

06-21-2005, 07:23 PM
I actually think we on Test would like to have a hard list, when the changes come down.  It's a lot easier for us to make accurate reports when we can compare the before and after, and not just say, "I seem to remember it working like this, and now it kind of seem to be working like this instead."  Because that's what we do for a lot of changes and bugs, and it's less useful than being able to match actual documented changes. The good news is, in the last month or so the devs and QA team at SOE have gotten much, much more communicative with testers, so we may actually get info this time. <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /> <div></div>