General Suggestion - Community Beta-Testing for Updates - Denied - Denied

[Ein]

What are you suggesting?

I'm suggesting that a select group of people from the entirety of the server (Not just SMT / HCMD) are selected to be private "beta testers" for upcoming updates to the server. This would include things such as map changes, feature implementations (such as the breach system), and a variety of other things.

The issue a lot of people seem to have on Gaminglight SCP-RP as of current is the fact that updates come out unpolished, and in many cases unfinished. The new map is an excellent example of this, not only was there no mega-event for the map change (which is shocking, considering one was actively in the works), but it was implemented on a Monday. I feel like releasing it at the end of the week after a period of polish and review would have absolutely saved this map from some significant criticism. I understand that it was purchased from Atlas Uprising, but map edits are possible. We're seeing several major SCPs (Such as 610) without a specialized containment chamber when they should obviously have one. The new map has various easy-to-spot & easy-to-fix errors, such as signs being mislabeled or railings randomly cutting off.

Another example is the breach alert system, which on release had a generic stock alarm sound effect. We're seeing the same issue in Gaminglight as with the rest of the gaming industry, instead of releasing a completed product, we're releasing a half-baked mess and then day-1 / day-2 patching it, and it leads to a lot of the complaints.

I hate to compare to Civilnetworks, but whenever Civilnetworks releases an update, I have never seen major bugs and it's obvious that extensive testing is done. Civilnetworks ERT didn't release with broken spawns, guns that don't work, and completely unusable features due to bugs. Yet you see these exact issues on Gaminglight (New map had broken SCP & class spawns, original A-1 guns were completely unusable) They release complete packages, not half-polished messes.

By selecting a group of beta-testers from the Gaminglight community to view, ask questions, and make suggestions for changes to upcoming updates, then you allow for the major constructive criticisms to be addressed before they're released.

How would this change better the server?

Community Feedback is one of the most crucial parts of developing anything, and obviously SMT understands that because they (and Zeeptin) come to us about upcoming / proposed updates and changes, especially with the new channel in the command discord. If you have a team of even as little as 5 community-picked beta testers, then these people could easily bring up their own concerns for the map and address issues like this before they're released for the entire server to complain about.

Are there any disadvantages of making this change to the server? If so, explain.

The potential leaking of information, but with literally anything there's always a chance of getting leaked / a trust factor involved. Just don't pick people who are gonna leak things.

Who would this change mostly benefit?

Everyone

Please link any workshop content, screenshots, or anything that you think may be helpful to those who view this suggestion

N/A

[Vuitheirt]

fantastic idea, massive +support

[Tazza]

15 minutes ago, Vuitheirt said:

fantastic idea, massive +support

 

[Antonio]

1 hour ago, Vuitheirt said:

fantastic idea, massive +support

 

[Boesermaster]

+ Support we Definitely need more testing done before releasing something new. Or doing something, the increase of the TTK is another example, it took s an suggestion to increase SCP HP, while that suggestion was in progress SCPs where barely an annoyance. 
 

Then the two recent SCPs, both models of them, where not put into the content pack a few Days after release. And even now, they don’t have any rules. 
 

[Ectoplasm]

+Support

This would prevent repeats of the shitshow that is new map (no disrespect intended to anybody who worked on it)

[Piller]

SMT generally utilizes HCMD+ and JMT for beta tests when needed. However, not every implementation requires a beta test. We've been doing the same system for years and it's been working well. Changing the entire thing because some people are unhappy with the map rollout would not be beneficial to the server or future developments.

[Piller]

Denied. The SCP-RP SMT has decided against adding this suggestion for performance reasons, the benefit to the server, or another unstated reason.