No Quests Are Broken!!

So on this thread im making, im trying to tell everyone that quests arent broken in gavel. how do i know that? its that they had 3 testers, 10+ mod testers, 30+builder testers and countless more, when they started making gavel, the first thing they did was make the gate, then the map, but thats building. more like the first thing they implemented was the quests, they took about 10 weeks testing the same quest 10 times over and over again. so whoever thinks the quest was broken, must've missed something. for example, my friend said he cant enter the factory on the iron heart part 2 when he had all the items, but i fixed it by just saying to him, "try reading the quest book". so quests aren't broken, they are just rarely glitchy. bugs will come, but bugs dont break.

 

First of all, I'm not saying you're wrong. A large percentage of the time, it is as you said; people are simply missing a part they were supposed to do or they are in the wrong place to begin with. However, you said they had 43+ testers. Let's assume they had fifty-five testers, just to increase the number. That provides many opportunities to test each quest and feature somewhat extensively. This does not compare, however, to the 1150-3000+ players that are now playing Gavel at any given moment. Even if all fifty-five beta testers finished a quest with no issues, that does not guarantee that the quest is without issues.

The larger a project, the more issues there are likely to arise. The larger sample group, the more issues there are likely to be found. In many cases, the sample group is not big enough, and thus not enough bugs are discovered. This is why many games instantly release many patches soon after release: to fix the bugs and glitches found by the general public. Beta testers find many things, but especially when the size between groups is so great, they cannot catch every detail.

Why else would we now have three different patches within a week of Gavel's release, with more already in development? Once again, in many cases, you are correct, it is the player at fault in misunderstanding what he or she is supposed to be doing. But in the future, please do not make absolute claims. I appreciate your desire to protect the server and its developers, but there are times when they truly are at fault. I am not blaming them for this, nor am I upset. In a project as large as Gavel, some features and sections not functioning properly is to be expected, and this is an accepted part of coding. Especially in the technology department, things rarely go exactly as planned. Many things often require fixing, even if it seemed perfect beforehand. As skilled as the Wynn staff are, even large corporations struggle with preventing problems with coding. This is unavoidable, and we must accept that there will be bugs and glitches now and then. I appreciate the testers' willingness to participate in the beta and catch any potential issues, but it is no fault of theirs, nor anybody else's, that some issues escaped notice. This is why beta exists: not to catch all of the problems, but to weed out the most notable and most easily fixed.

Thank you, that is all.

 

I think saying that "No quests are broken" is a bit too far. I mean sure, with 50+ testers, you are guaranteed to catch bugs and glitches, but I highly doubt you'll be able to find every single bug or glitch in the game. Take a look at battlefield 4, it had a multiplayer beta, but on release the game was broken and nearly unplayable (Not saying that wynn is unplayable, just making a point that having a beta doesn't mean a game will be 100% fixed). But when you have a lot more players involved, undoubtedly something is going to happen. There's a lot more people going around, which means someone is bound to encounter an error that the beta testers missed.

 

Thank you for summarizing. When I go off on a tangent I tend to overexplain and leave a wall of text so long that nobody actually reads the full thing :3
You even provided an example :D

 

Bugs and glitches aren't the only things that can make a quest 'broken' or barely/un-playable.

In several quests, the player triggers do not actuvate when needed, and in quests where you cannot go back to trigger these, the only way is to glitch back or /kill.

So not 100% of quests are not broken. In terms of bugs and glitches in quests, I have not encountered any negative ones (in perspective of profit to the player). However in a mischievous context, there are glitches and bugs that do allow players to cheat, and not only by using the usual, movement glitches.

 

As was said above there are still bugs in glitches, but the problem with most people is that they miss a region and don't understand it so they freak out and don't know what to do. If there are any problems in quests all you really need to do is read your quest book, and possibly backtrack in-case you missed something.