Mocam
EVE University
Ivy League
134
   |
Posted - 2012.06.05 13:34:00 -
[1] - Quote
Luis Graca wrote:CCP Goliath wrote:Anna Shoul wrote:Early dev blogs about what's going on with Singularity would be nice, so that people who go there remember to log in and test the problems out of the new stuff -- but I would very much love to see a changelog with every Singularity patch, so that if I do go there, I can mess with everything in detail.
There should be less worry about public opinion about what might happen, and more emphasis on actually setting up an experimental feature -> test server -> bug reports -> final feature cycle, and getting things done properly by the time they hit production. Rough plans are rough plans, everyone should be able to grasp that much. Rough plans remaining rough by the time they actually go live irks far more people. Patch notes for Sisi is impractical, but I write a list of features that are on Sisi on the forums - do you think that making this list into a devblog would be more appropriate? i don't think a dev blog would work however you guys could do a sticky/closed threat were you guys could simple write what's being tested and the date of singularity serv, after you guys are done with the tests and start a new one simply update that post. This way people would know what testes are being conducted and the date of their skills in a single place without have to search 1 by 1 Even better create a EVE sisi folder like "EVE Information Center" "DUST 514 Information Center" about sisi test this way you will gain more input information instead of chat with some players
I agree a resource thread in the test server forum would be the best place to list changes - in that forum . The old keep it simple stupid approach of centralized communications.
The time-stamps on edits should show lesser changes have happened, with a title change with clear/replace when a major change occurs. Such will keep the changes info in the same forum as feedback from the community.
The less places you have "non-team members" hunting around for what should and shouldn't be done, the less screw ups and missed testing you'll run across. I just don't think an actual changes log is needed. Some of the internal junk that gets fixed isn't obvious and some probably shouldn't be published in such a fashion at all (such as anti-bot updates and such).
The focus being on what is desired to have tested.
As to the OP: It kind of sucks going to sisi to "mess around" sometimes. I find myself testing stuff just visiting there at times.
Latest example: Destroyers had that 1.25 ROF fix implemented. Interdictors still have that 1.25 ROF in place. I checked with a Thrasher vs a Sabre - the Sabre fires the same gun 25% slower.
It's a hidden attribute of the Interdictors that was there before but never really published, though I do vaguely recall it being discussed when the destroyer changes were on sisi. As such, a dictor will do less DPS than the T1 version of that hull. I'd thought that had been fixed/removed at some point but it hasn't. A "wait and see" but not a major issue really.
Such "I wonder" stuff crops up and gets tested here or there, even when not directly applicable to a current testing situation. |