Droid Engineer Archive
Thread: Here they are, TC changes so far (all schematics available now!)
Jenden wrote:
Ok, resource spreadsheet is up, many thanks to Bumbles for the contribution.
Many thanks to *you* Jenden ![]()
Audio
Drashk wrote:
Shian,
Basicially it comes down to this. Each Major Publish produces X amount of pages of code changes, where X is usually at the very least 100 pages of code change descriptions. (I believe Q-3PO mentioned 300+ pages for Publish 3 or 4).This is the master copy of items that would include everything from 'Changed punctuation in Nym's Quest dialog.' to 'Added secondary pass on /tip verification.' There will also be tons of information that the DEVs would not want the game users to know, especially if it was Jedi related, such as 'Added Politician to the list of possible profession needed to unlock the FSS.' There is also the problem of items on the Master list being removed before the code even touches Test Center, because it did not pass a check on the Internal Test Server.
Where patch notes are concerned, we have to consider the amount of changes that occur during each and every the programmers change a small part of the game code. The vast majority of the changes that take place are back end changes that the general public would not understand. Can you imagine the huge volume of questions that would arise if the DEVs listed each and every change that was made during a Publish cycle? What you are asking for would make the process of adding Patch notes a long and tedious process that would only cause more questions than we currently see.
Something else to consider is that listing all the changes to each profession would take away a part of the games mystery and challenge factor. It would be like handing someone a thought puzzle along with a detailed description on how to solve the puzzle. Part of the draw with playing a crafting profession in a MMORPG is trying to figure out what makes the profession tick and how to go about making the best possible good. If the DEVs handed us a manuel that discribed every single aspect of a new feature, wouldn't the prospect of trying out the new feature be diminished?
I can see the point of wanting a 'Master List' of items to test out, however the Patch notes that the DEVs are giving to the TC community have come along way from the earlier publishes. Publish 7 appears to be the best user end documented Publish so far and maybe at some point down the road we may see a more indepth list of changes, but I don't think that we will. (Personal opinion)
Drashk my Dove
Don't even TRY to tell me anything about software development, elsewhere you can read that I know a whole lot about it.
You are making excuses for the Developers, and there are none. Current procedures are un-professional, and just because the patch notes have come a long way does not mean it is acceptable.
Listing what has changed spoils the game does it? Bull. Listing what has changed is the ONLY way to ensure that what has changed gets tested. If you want mystery, let them say 'change to Droid Storage Compartment Schematic' and let us work out what..but I do not want to supply 50 crates to an Architect ever again with the crap that the last patch brought about because nobody knew.
I know what Technical Change documentation looks like, and I know I'd be fired on the spot if I ever let a software release out of my IT department without User Change documentation..end even then it would only be to a test environment. As an aside, it would only ever get to live with all the heads of department signing off the changes (perhaps you corresondents could do that *chuckle*)
So, dont talk down to me as if you know better..keep spouting the party line why don't you. I swear I don't understand you supporting this unprofessional approach to change control.
The Easy Way is NOT the Best Way
Message Edited by Shian_Tavkin on 03-04-2004 08:18 PM
From today's TC notes
"Droids: Fixed a 0% crafting attribute bug!"
Finally, but what does durability actually do to a droid? I could never figure that out.
Jenden,
Is this a list of all the New Resources we will need to collect to make the new Droid Modules?
Can you post a link to it, thanks.