Funcom. Please. For the love of the Gods please stop “fixing” the UI.
Stop.
Undo everything from Ch4.
I’m so close to literally starting a petition.
9 Likes
It would be so funny if it weren’t so sad
1 Like
Their playerbase is so miniscule as it is! What on earth are they thinking?? They’re just running everyone off of their game. It’s ridiculous.
LISTEN TO YOUR PLAYERS FUNCOM.
WE ARE YOUR PAYING CUSTOMERS.
4 Likes
The old system is gone. Doing a several month rollback would incur losses of manhours that would likely result in sunsetting of development (meaning it would get stuck on what we have now), closure of all FC servers, and the closure of FLS, destroying the ability to play multiplayer until a crack is developed.
Its not as simple as control-z (which causes wonderful headaches in the devkit I might add), and would require a full redevelopment. Which would result in even more bugs then you see now. No, the only way to go is forward and bear with the issues until they are fixed, or find something else to play.
You do at your option (if on Steam-PC) the ability to play an earlier version of the game. But of course you would need to do that with dedicated server software that matches and play with other like minded individuals. But don’t let that dissuade you, you all are a sizeable chunk that want to play that way right? Get together in a conversation and play the game the way you want to. You don’t need the rest of us right?
You’re arguing about a technicality that doesn’t matter.
It doesn’t have to be a literal roll back of the code, FunCom can use whatever method they want to use in order to restore the functionality. It could be a literal roll back of specific modules, it could be re-inserting the old code into a future pacth or writing new code that re-enables the functionality.
You’re arguing about method when no one but you cares that method is used. People don’t care whether the code is rolled back or moved forward, what they want is the game functionality to be restored to a better state.
5 Likes
Having been in several arguments about this, no they’ve literally said they wanted a full rollback and said it was ‘simple to do in Steam’. They want a button combination to be pressed that makes their issues go away now.
Not develop. Not fix. That’s not quick enough. Just a windows undo function to fix all their issues.
This isn’t an argument of whether or not they should restore functionality. No one said they shouldn’t. Its an argument about how that comes to be.
You’re right, I overstated my case and I understated the language that many people use. Therefore I apologize, allow me to take a step back try again.
So… on the day an update is rolled out, yes it is absolutely possible to simply roll it back. This is a basic, standard feature of modern software development.
Mind you, it’s not as simple as clicking one button, but it is standard functionality for software roll outs. It also becomes increasingly difficult as time progresses, it takes a more work to roll back a deployment after 24 hours, 2 days, 5 days, etc. because so much of the data that the application manages has changed. But even then it’s not impossible, and depending on the specific software in question it may or may not even be particularly difficult.
The problem in these discussions is that you continually talk as though it’s not possible, or it’s mind-bendingly difficult. To put it simply, you’re wrong. I don’t know where you’ve gotten this idea from but it’s factually incorrect.
I’ve done dozens and dozens of software deployments in my career (almost enough to say, “hundreds”, but not quite). I’ve done deployments that took 5 minutes all the way up to a 24 hour maintenance window, depending on the size and complexity of my application. But in every deployment no matter how large or how small, in addition to practicing the deployment in a test environment we also test doing a rollback in that same environment. If we can’t get it right the first time, we reset the test environment and deploy/rollback again, until we get it right so that we know in advance it can be done in production before the production system is ever touched.
This is how professionals deploy software.
Building a rollback plan is a basic, standard element of any software deployments in a professional environment. This is not something people learn about in school, it’s not part of taking any computer science curriculum or programming class and there are no classes in “how to do rollbacks”, but it happens in every software company that is run by professionals.
And, more importantly, once you learn how to do it, it’s just not that hard. If a deployment team knows how to do their job, doing a rollback takes only slightly more time than the original deployment did (about 10% more time on average). It does not require and extended outage nor does it require the entire company to go into emergency mode.
Anyone who argues that they’re excessively difficult, or even worse “not possible”, does not know what they’re talking about. I don’t mean this as an insult, but that includes you, you simply don’t understand how software deployment works. For the record, I’m not suggesting you don’t understand development, that’s a different skill, what I’m saying is specific, you don’t understand deployment in a professional environment.
That’s the end of point #1: Rollbacks are a basic, standard feature of modern software development, they’re not as hard as you think they are.
Now on to point #2…
In that case you need to improve your messaging to people. What you could be doing is saying, “They’re not going to roll it back, but if we lobby them hard enough they might restore it in the future.” But instead what you say is, “It can’t be done, everything can only move forward.” It shouldn’t be hard to see what is different about those two messages. Whether you realize it or not, the message that you repeatedly send is, “It can’t be done, shut up.” I’m guessing that’s not your intent, so maybe spend some time thinking about how you present your responses.
3 Likes
You are so right. Im glad you love Funcom. Lets join forces in defending the multibillion company against the heathens!
3 Likes
I don’t believe in rolling it back though. I want to move forward and see everything improved. Going forward and having an improved experience is not mutually exclusive. Some may disagree but I really like the building system introduced in Age of Sorcery for example. That streamlined my building in nearly exponential ways. And it took a bit to get it to what we saw released. Just like the stuff with this chapter, there was a ton of rough edges many of this community didn’t even see. Though personally I would have liked to see them work it out a bit more before releasing. I do think they should divorce some of these fixes away from the release schedule. But part of that is because of outside schedules (not FC) unfortunately, and they don’t have the pull that other devs have with those timelines (speaking of Sony and Microsoft here in case it wasn’t clear).
Behave yourself, Deacon.
1 Like
<3
Start one. I’ll sign it. I’m 100% on board with a full Ch4 rollback.
2 Likes
Not me, I have a fanatic.
1 Like
I am 100% onboard too.
Regardless on what I say on my main account. I dont wanna look like Funcom shill.
Remember the times you and I played age of conan?
There were no times when you and I played Age of Conan.
Not true. 2014. Remember.
Nope. Never played AoC with you. Didn’t play in 2014 either. Last time I played AoC was in 2013.
2013 and 2014 are same years actually. Forgot to mention that.
I remember your long red hair. We had to destroy some bosses fast.
Ah, fun days. I was full of ideals and thought Funcom team is good. Remember?
I had white hair. Like the one Im wearing now.
LOL, you got me.
dude, you are arguing with a spoof account.
I am talking to my thralls every day. We interact. We play. Even when im not in game.
Also, dont try to pretend you never played age of conan with me.
It hurts.