|
Author |
Thread Statistics | Show CCP posts - 56 post(s) |
MailDeadDrop
Rage and Terror Against ALL Authorities
342
|
Posted - 2014.06.10 14:52:00 -
[1] - Quote
Does that mean that, exempting decryptor effects, it is no longer possible to get multi-run T2 BPCs from invention? Currently (Kronos) max-run T1 module BPCs yield 10-run T2 BPCs. If invention only yields 1-run T2 BPCs then there will be *many* more invention jobs in Crius. Am I misunderstanding something?
MDD |
MailDeadDrop
Rage and Terror Against ALL Authorities
342
|
Posted - 2014.06.10 15:02:00 -
[2] - Quote
CCP Greyscale wrote:MailDeadDrop wrote:Does that mean that, exempting decryptor effects, it is no longer possible to get multi-run T2 BPCs from invention? Currently (Kronos) max-run T1 module BPCs yield 10-run T2 BPCs. If invention only yields 1-run T2 BPCs then there will be *many* more invention jobs in Crius. Am I misunderstanding something?
MDD All invention jobs will spit out a max-run blueprint. Sorry, should've mentioned that, lots of plates spinning today :) Whew! Yes, that makes things better. Thanks!
Edit: Of course that means decryptor overhaul is even more pressing!
MDD |
MailDeadDrop
Rage and Terror Against ALL Authorities
342
|
Posted - 2014.06.13 14:14:00 -
[3] - Quote
CCP Greyscale wrote:Regarding the state of the build: - This is the earliest something this large has been on SiSi in a very long time. As Nullabor said, SiSi was made available almost immediately after Kronos, and we wanted to start collecting public feedback as fast as possible - The code running on SiSi is our nightly development build. It's not a sanitized, polished setup, it's literally "what we did yesterday". Internal testing is happening in parallel to stuff being deployed onto SiSi - We are (I believe!) still comfortably confident that everything will be ready in time for the scheduled Crius release; a lot of things are broken right now but they are in general superficially broken and comparatively easy to fix. We don't have any big, risky features to implement or fixes to work on. - The proof will of course be in the pudding, but given the current situation we do not feel it is productive to spend time discussing whether or not we will be ready in five weeks in these threads, so we ask that you focus your feedback on the specifics of what features are working how on SiSi right now rather than expressing your professional judgements as to the likely state of our codebase in five weeks' time. Thanks :) Noted. But please take away from this the realization that you (CCP) failed with "expectation management" of the (current) state of Crius on Sisi. I haven't spent any time analyzing that failure and therefore don't have any advice for you.
MDD |
MailDeadDrop
Rage and Terror Against ALL Authorities
342
|
Posted - 2014.06.13 14:33:00 -
[4] - Quote
Uncle Funklestien wrote:Quote: Noted. But please take away from this the realization that you (CCP) failed with "expectation management" of the (current) state of Crius on Sisi. I haven't spent any time analyzing that failure and therefore don't have any advice for you.
MDD
Then why are you in here bitching? Seriously, you aren't giving any feedback on anything at all and said yourself you haven't bothered looking at things. Go play TQ for a bit, chill, relax, have a great day, then come back here when you have thought of something to test and try and report on. And on another note, try and have a good day MDD. Sorry if my reply came across as "bitching"; that wasn't the intent. I was merely illuminating the expectation management failure, with a thought towards the releases after Crius. What I intended to point out is the next time CCP puts a largely unfinished, full of "superficially broken" things, onto Sisi and asks for feedback, they need to carefully consider how to widely and clearly communicate that state so that fewer people are shocked (& distracted) by how "bad" it is. My comment about "not having advice for CCP" was directly related to how to accomplish the "widely and clearly communicating that state."
MDD |
|
|
|