Until the thrall disappearing issue has been resolved. I’m asking because you have a habit of releasing these updates despite multiple bug reports but this time it’s different. The thrall rando-vanishing directly interferes with the whole idea behind this living settlement concept. Please, for once fix something we’re telling you is broken on the Beta before you bring this live.
hope they gonna fix it so its not gonna be like that in october when the update comes out
That’s my problem. On each of these public betas or testlives or whatever they wanna call it, there’s been severe bugs that were straight up ignored for the sake of meeting their release date. They wanna show they’re turning over a new leaf? Fix this BEFORE it goes live. I’m not in the mood to lose my main save thralls over an unpredictable bug that wipes them off the server.
i think they gonna fix something like this, but fix is not something their just happenden like when you clap in your hands
From what I understand, it has already been clarified that the purpose of Beta is to identify any issues and then address them in hotfixes and subsequent releases.
So if this clarification is what they’re sticking too it would stand to reason that nothing is going to postpone a release regardless of how impacting it is.
Not what I hoped to see BUT does explain why prior releases went out without much needed bug fixes.
One good thing is that they have only given “October” as the release month. There’s still hope since there’s no hard date yet.
This is truly game breaking, the “auto deploy” mode that sometimes happens with Wheels of Pain seems to teleport the thrall to a different base, and usually under the world, map shows thrall at the base with your bed, but they are never actually there.
Attempts to rescue from the thrall menu says they are in combat or that they cannot be found. If in combat after a day they get deleted, if not found they are deleted right then.
Also some thralls just drop under the world at random as they wander around the base, with the same result.
On a side note on a PvP server I just saw a thrall spawn in to visit the bar, and she opened all the doors on her way in! WTF is that supposed to happen?
hum in past i saw them released update with identified and reported importants bug, and applying patch just 3 or 4 weeks after the update have been released.
i hope they realized it was a very bad idea and finally understood that they should never release a version of game with gamebreaking bug especially when it has been reported in beta test by their players. but knowing the past the orignal comment of the creator of the thread seem to me wise
I did try asking directly for clarification of whether or not public beta was intended to be used for fixes in advance of release or only for fixes after release. The only response I could get was to be re-directed back to the section of the recent Q&A that doesn’t directly answer the question. I tried pointing out that not knowing this leads to frustration and testers giving up testing, but response came there none…
So, while I suspect that there will be no fixes, at this stage I can’t say what the actual intended policy is.
here is where carol talking about what the goal is for the beta test servers [quote=“Caroll, post:1, topic:260698”]
What’s the goal for Public beta testing?
Public beta testing helps us identify critical issues that can only be revealed in a live environment and adjust the player experience to align with the expected gameplay loop. In addition, feedback from players and content creators is vital in preparing for potential hotfixes and post-launch updates, shortening the time before they can hit live servers. It is also great to get additional bug reports, even for known issues, as they may contain various hints to help us fix them.
[/quote]
To me this sounds like beta testing serves to both fix things before release and deploy hotfixes post-launch? But Idk, maybe I’m just stupid.
Yes - that’s the same answer she gave me, that I had already seen then. It still doesn’t actually answer the question - “will any bugs found on public beta be fixed before release, or are all bugs saved for the subsequent hotfixes?”
This text does not answer that question. Asking the question directly does not receive an answer. Even if I had time for testing this month (I don’t), I would be unwilling to do it, because we cannot receive a straight answer to a simple question.
The reason they don’t fix beta bugs before live release is because the patch has to go through certification with Sony and Microsoft. If they patched it before release, they’d have to restart the certification process all over again.
In order words, patching it would delay the live release, at least to consoles, regardless what the patch entails (they can patch and release to PC immediately, as no certification process is required, but they are very reluctant to do asynchronous releases these days).
Having to push back the release and restart certification would be a huge headache, so they would need a really good reason to do so. Does thralls randomly disappearing meet such a threshold of being worth the headache though? It very well might, Funcom may have a meeting after the weekend to consider it.
Just demanding them to do it is probably not very persuasive though, documenting how often it happens and how severe the impact is would likely be far more useful.
Yes. And that is why I asked for an official statement to that effect. (Because, while I believe you are almost certainly right, we are still relying on opinion until Funcom is willing to make a proper statement.) Instead I was directed to the same bit of text Hiveshadow just reproduced, which does not state that. And when I clarified specifically what I was asking, I was ignored. All I have asked for is a statement exactly like you have just made, except from Funcom. With that we would have something to point to everytime people complain that nothing is ever fixed from public beta. Without it, we remain in a limbo of not actually knowing for sure, and we continue to lose testers.
(To put it another way - with a proper statement, I consider returning to testing for future releases (not this month, moving house), without a proper statement, I won’t waste the time or drive space.)
they have said we have a couple of weeks for me that sound like they wanna look into the bugs and try to fix it while we have the beta servers up and running, 100% they dont want this to com out when they com out with it on the live server and push back the releasse will not help they can delay the release if their still are ton of bugs they only one their can answer it is funcom
With all due respect, it does not matter what it sounds like. Others in this thread have suggested that it sounds to them as though Funcom’s answers mean there will be no fixes until after release. Who is right? We won’t know until we actually see it in action - will they fix, won’t they fix, I don’t know, nor (as proved by this conversation) does anybody else.
That is why the statement Funcom has given is useless, because it does not answer the key question (actually, it’s not ‘useless’, there is useful information there, it just doesn’t answer the most important point). That is why I have asked for a direct statement. Funcom has not made such a statement. Funcom refuses to provide a simple direct answer. They have the right not to answer. I have the right not to waste my time testing for them, for free, unless such an answer is provided.
if you dont want to use the time on the beta test then dont doit no one forcing you to do it, and its only funcom their can aswer your question but push back the release will be a bad idea becuse have used so many hours into this so fix the problem will be much better, we as aplayer cannot answer your question i do hope funcom fix the things we find to them when its around the contehnt they are giving us. and i just telling what i seing on how they communitatet to us i see this now we got a few weeks before the update comes out and we really dont know where in october it comes out im just tilling you this is the best sign they have givinmg us about the beta to have it our in so long so they can havea chance to fix the major bugs to the content so er dont end up having a cluster shock (that is how i see it) and the beta update is not even a week old allso you need to give them time a fix does not come at the same moment as the bug was found
Which is why I asked Funcom.
Which is who ignored me.
Which is why I won’t be testing.
As for the rest of what you keep typing, none of it is relevant. I have not at any point ever demanded that they ‘fix bugs now’ or ‘push back release’. I do not know why you insist on doing this every time I make the mistake of communicating with you. I asked for a statement. That’s it. Nothing more. Telling me I’m wrong for wanting them to ‘push back release’ or ‘fix bugs now’ is irrelevant, because I have never asked for or even suggested those things.
If past experiences says something…
They Will not.fix a thing on testlive. And it is quite possible the build that Will be sent to certification is not the same as the ones on testlive.
An untested different build Will come out with all the issues reported. And 2 to 4 week later a hotfix Will come , that hotfix Will Fix some of the issues that was reported, this hotfix Will of course break new things. And some of the reported issues Will be left in Game for us to workaround for who know how long.
This is not how a test platform should work.
Ok so I have something to report but it is still ONLY a suspicion.
I’ve submitted 14 bug reports so far for mostly pre-existing issues.
Yesterday the public server I am on went loopy and then shut down unscheduled. Since then I have not had the inventory problems apparent in Name, Heaviest First, and Type. My plan is once I am done the run around I’m currently doing to test it further.
But, if my suspicion IS correct, they’ve fixed it.
I’ll update once I know for sure. Fingers crossed.
Hmm did you download something ?
I don’t think this is server aide related.
But keep US posted
If they did , they should Say it.