Posted May 03, 2021
PR improvement suggestion: instead of saying "/feature_here/ will be released by /specific date here/" or similar - always (always!) say something like:
- "we want to release /feature_here/ by /specific date here/"
- "our hope is to release /feature_here/ by /specific date here/"
- "if all goes to plan, /feature_here/ will be added by /specific date here/"
etc.
I.e., without complete certainty about it. Even when there is such certainty in practice, at the time! Why? Because it is not impossible for certain things to end up not happening, when something impossible to predict - delays or cancels them.
The point of this suggestion - is the "always" word, above. As of now, things about the future are already said (by Rockfish staff) often in this "not completely certain" way - but not always. And i think that this is important to do it always - at absolutely all times.
And it's not just me. Michael himself said in the stream chat 30.04.21, 58:47 mark in the stream - quote: "nothing is a 100% promise during EA". Which, of course, is very true - due to the unavoidable bit of unpredictability, which any early access process comes with. And this, i think, supports my suggestion.
To illustrate how completely certain it can get at times, here's a recent example when a feature was sort of "promised" in a completely certain way, just to illustrate which particular types of sayings this is all about:
https://youtu.be/TyUbpIGZGTY?t=5312 - quote: "there will be ship customizations in the future where _you_ will be able to do something very similar to this", while rapidly changing specific modules of a ship, complete certainty about it. There are more such examples, most notably the certainty with which Vanguard release was announced for May update about a month ago.
I think it's best for both Rockfish and ES2 fans if this (above) suggestion about certainty - would be formalized and strictly adhered by Rockfish. I think that doing so - will allow to create a bit better game (which fans would love), and to have much better process of creating it (which Rockfish team would love). Win/win.
- "we want to release /feature_here/ by /specific date here/"
- "our hope is to release /feature_here/ by /specific date here/"
- "if all goes to plan, /feature_here/ will be added by /specific date here/"
etc.
I.e., without complete certainty about it. Even when there is such certainty in practice, at the time! Why? Because it is not impossible for certain things to end up not happening, when something impossible to predict - delays or cancels them.
The point of this suggestion - is the "always" word, above. As of now, things about the future are already said (by Rockfish staff) often in this "not completely certain" way - but not always. And i think that this is important to do it always - at absolutely all times.
And it's not just me. Michael himself said in the stream chat 30.04.21, 58:47 mark in the stream - quote: "nothing is a 100% promise during EA". Which, of course, is very true - due to the unavoidable bit of unpredictability, which any early access process comes with. And this, i think, supports my suggestion.
To illustrate how completely certain it can get at times, here's a recent example when a feature was sort of "promised" in a completely certain way, just to illustrate which particular types of sayings this is all about:
https://youtu.be/TyUbpIGZGTY?t=5312 - quote: "there will be ship customizations in the future where _you_ will be able to do something very similar to this", while rapidly changing specific modules of a ship, complete certainty about it. There are more such examples, most notably the certainty with which Vanguard release was announced for May update about a month ago.
I think it's best for both Rockfish and ES2 fans if this (above) suggestion about certainty - would be formalized and strictly adhered by Rockfish. I think that doing so - will allow to create a bit better game (which fans would love), and to have much better process of creating it (which Rockfish team would love). Win/win.
