Glorious Alpha Two Testers!
Alpha Two Realms are now unlocked for Phase II testing!
For our initial launch, testing will begin on Friday, December 20, 2024, at 10 AM Pacific and continue uninterrupted until Monday, January 6, 2025, at 10 AM Pacific. After January 6th, we’ll transition to a schedule of five-day-per-week access for the remainder of Phase II.
You can download the game launcher here and we encourage you to join us on our for the most up to date testing news.
Alpha Two Realms are now unlocked for Phase II testing!
For our initial launch, testing will begin on Friday, December 20, 2024, at 10 AM Pacific and continue uninterrupted until Monday, January 6, 2025, at 10 AM Pacific. After January 6th, we’ll transition to a schedule of five-day-per-week access for the remainder of Phase II.
You can download the game launcher here and we encourage you to join us on our for the most up to date testing news.
Comments
If the developers think they will save a lot more time they would do it if its a tool they need.
Anything can be a what if though. What if people start have some reason to dislike something that happens and what if people start blaming it on how they develop the game and they aren't using the most up to date engine, and experimental features. Without understanding that wouldn't change anything.
LOL I don't think you understand the concept of white knighting my friend
telling you to let others express their concerns and stop trying to dismiss others feedback is white knighting...? you can't just use the "No, You!!" card in any situation
You are very much white knighting right now "LOL". I'll ask again at what point have they ask about technical help of their game, and do those people understand IS challenges and problems and how they are currently using UE5. You are stretching the use of feedback in a way i have not seen it being asked before but if you can provide context where it has been a actively asked thing I'd be happy to see it.
Feedback is now telling someone how to develop a game now while not understanding the studios issues, how their development works, or how unreal engine works?
I'm unsure what kind of job you have, but if it is technical enough I'm sure you can imagine someone coming up to you and not understanding issues and assuming what is best for your development / software and trying to start trains on the internet on what you should be doing would be quite patronizing.
I said it before, the developers know what to do with their own game the best when it comes to the technical challenges with their development and tools they feel are beneficial. If it is something that is good and not "experimental features" they most likely will use them after testing.
Having a bunch of people yelling on forums you should use these tools sounds innocent at first, but knowing the internet things can get skewed and anything used as a complaint to dislike something. Developers will know the new stuff out there, consumers being interested and saying its cool is fine. People saying they should be upgrading as much as possible is one example of what I'm talking about.
That is my piece on, but my following question will be is what concerns are people online suppose to be making. When we are talking about technical challenges since you seem to want to defend people making this claim in what my post is referencing.
Simply because someone has a concern doesn't mean its always warranted (granted I'm trying to see the concern you are talking about??)
Concern over their compatibility to develop a game sounds pretty silly based on what they have shown clearly knowing what they are doing. You can have concern if their ability to develop something, doesn't mean you are backing it up with any actual facts at the end of the day, leave it to the professionals.
what you are doing is being a Karen, go get a snickers bar. He/She stated their opinion, nothing more, whether you agree with it or not. Just move on and focus on other conversation. While I agree with expressing concern, calling someone a white knight is cringe and pointless, other than looking to be a dick.
@novercalis So, you agree with me, but you wanted to leave a pointless comment for a discussion that ended days ago. Nice virtue signaling bro
You literarily are being a karen and won't detail "your concern". Your own fault for throwing off the discussion. And also refuse to answer questions for clear reasons because they don't exist when I was talking about technical side of things.
Here, let me help, you are the winner of this discussion! I lose, hooray! let's move on frand
To be fair, that doesn't really put you in a position to be able to talk about their internal development practices or development issues they might be running into. You can't actually know what problems they might be having, so you can't actually know if any advice you think you're giving is actually useful.
And honestly the chances are good that even if you did know what issues they might be having, you probably won't have any feedback that hasn't already been discussed internally.
Yes, we can, we know how to analyze and design many things at high level without having to know the low-level details. But we have a lot of knowledge about best practices, server architecture, server jobs, custom managers running in the servers, programming in multiple languages, project management, estimations, effort quantification, and more. A game is just another system.
We know a lot, if AoC ever receive a port or an interface or anything for community creations, get ready to see some wizardry from the community.
Additionaly, if I am not saying something like "this takes 13 days and 7 hours with 5 people working in this", then you can't say all those things... you weren't even in the conversation and only meant to disqualify others.
Exactly this, that s why I asked for a cause there is always a chance i might have missed something said. The fact they are using the term "we" sounds like a great way to start up some trains and use numbers and per pressure its all a dangerous path imo knowing exactly how the internet can be.
@Arya_Yeshe Please go ahead and analyze their issues in updating constantly to new versions and the effect it has on their development and what challenges they have to overcome to do it with their custom code. I'll be happy to hear.
Though if your answer is you don't know, how exactly are you going to offer technical feedback on their development process, how are you going to know the time it takes, their goals or what exactly they need and what they can make use of tool wise based on their development?
No. You really can't. You have no way of knowing what issues they might actually be running into. You might be able to make educated guesses based on previous experience but since you have no knowledge of what is actually happening internally at Intrepid you cannot say for certain that you could provide useful feedback to them on their development practices or issues.
I'm a senior software engineer for a consulting firm that's worked with companies in essentially every tech or tech adjacent industry by the way. I would never assume to be able to just provide useful feedback on a company's development practices without any working knowledge of what they're doing internally.
Just going to make sure you realize my point is in relation to people saying they should be updating as often as possible and not realizing the work that goes into it or that every update might not even benefit the project based on work required.
My point is devs will be fully capable to know what is going on with their engine and its updates. Just cause consumers see something cool and in their mind ( not the devs) think it will benefit the project needs to be considered more than just wanting to think updating over cool things will be beneficial vrs time/cost.
I guess if you can't reply with an actual argument then resulting to insults works too. All I did was point out that you can't know what's going on internally so you really can't provide meaningful feedback on their processes or issues. That isn't an insult and it isn't "bringing nothing to the table" either. It's just simply stating the reality of things. And if you think you can tell what they should be doing differently from watching their streams and the next to nothing they've stated publicly about their dev processes and the problems they're having, and I'm not talking about things like "work more on LODs because the transitions looked bad in a stream" because that isn't actually helpful or constructive, then you don't actually know anything about software development.
If you can provide some sources where they've talked about specifics regarding their dev processes and the issues they've run into then by all means, post them. Otherwise, don't presume to know that you can provide anything of worth from a development process standpoint just because you claim to work in the game industry.
You didn't come here to discuss and just became a Mag7spy alt