turn of phrase. Bond villians generally have some weird philosphy that guides their actions, like this attacker who is using a cyberattack to push a goal of threatening a company to make their stuff open source.
“Drats! My evil schemes are thwarted yet again by reason and sensible suggestions! When will this citric tyranny end?!?! Curse you, Lime! !!!”
Mr. Hacker falls to his knees, releasing a primal scream towards the heavens, torrential rain soaking his purple tuxedo, turning brackish as it mixes with his salty tears of rage.
I was once building a game where a dinky little neon space fighter zips around the field shooting down enemies that spawn in until the boss. Everything was going great, the engine was handling large number speeds, the parallax background I custom coded with an rng star map worked perfect, right up until I tried to implement enemy tracking of the player: that shit would not work no matter how hard I tried.
I was about to share the old demo for you dudes to try but looks like I’ve lost the .pck file associated with the Godot executable or the embedded pck is no longer recognized.
Sure it is, you just implement depth map deformation into the static terrain, totally doable! Then you just tie in a strain system to all the game’s models so they fall when they don’t have enough support, then add destruction animations for every static model and falling animations for every character. Totally easy, they had that back when the original Red Faction came out for PS2, the devs are just lazy! /s
I built an API connector for work (I’m a hobbyist, not a pro) to download what is the most common cargo transported by trucking companies from the DoT database. Everyone complained because they had to enter the company names correctly into a CSV as it wouldn’t accept typos or do fuzzy matching, nor could it automatically determine which was the head office of a company, only return a list of all of the offices.
UI is incredibly complex under the hood. Cryengine is also difficult to work in. There are tons of reasons games with distinct outstanding features don’t switch engines, though, and it’s usually due to the specific features said engine provides, no matter how difficult it becomes to work with as a legacy system over the years.
There is NO reason for hunts UX to as fucking terrible as it is. They literally took it from bad to straight up awful. Believe me, I know how hard to design and implement a good UI can be, I’m a software engineer. I’m not just handwaving “make it better, duh”. It’s flawed from the user requirements up. It’s like they never used their own ui before. It’s stunning how thoroughly they don’t comprehend how people have a terrible time navigating the game menus.
For Palworld, a new island takes 6 months, per the article. Probably talking about Sakurajima and the big southern one. That makes sense, since it’s not just putting stuff there and calling it a day on the first finished thing, some level design has to happen so the place makes sense and doesn’t feel super boring to explore.
So then why don’t they have regular bulletins in their games showing ‘Look, look! These features will be coming by xx/xx/xxxx!’ ?
Things set the timeline back? ‘Oh no! Looks like we won’t be releasing this on that date, it will actually be this date!’
Seems like a non issue for anyone with a 6th graders capacity for interacting with other humans. These are IT folks, with the added layer of gamers to boot — though. Anticipating motivations and responding to others input isn’t exactly a strong suit.
Edit: oh, beyond that — I have very little sympathy for a developer of a content drip. You’re out for the money, don’t whine when people inevitably get sick of waiting for a little more of something they’ve already gotten maximum enjoyment out of.
It would also be great if devs added things during development that should simply be there at launch. Instead of that, shit gets rushed out the door with promises of future fixes and updates. And then devs get all huffy when people rightfully ask for things to be added that are supposed to be basic launch features…
There’s a strong argument that the server architecture needed to be better at launch, but then the game sold more than an order of magnitude better than it was expected to, so no one would have noticed that it scaled badly had the player count been in line with their design and testing.
Ah yeah that’s a tricky one. I guess as developers we’d all like to be ambitious and plan for millions of users but that sort of hardware and architecture takes time and money that might not be realistically in the budget/scope.
I’ve also not really got insight as to who would have a say on that kind of hardware, whether that’s PMs or devs. Probably higher-ups, right?
I think for something like this, you’d rent cloud servers as you’d expect the number of concurrent users to change over time and ideally would be able to spin up more capacity when you need it without having to have those machines available all the time. You still need some kind of system that decides when to order more capacity with enough warning that it’s actually available (you can tell AWS you want a VM immediately, but it still takes a couple of minutes to transfer your data onto it and boot it up, which is longer than people want to sit in a loading screen) and decides which servers to assign to which users.
Fair! I’m in web so wouldn’t know either. What kind of software do you work in? I’ve been thinking about jumping careers lately after realising that I quite like architecting a more complex system, and sort of hate working with front end web dev😂
Well, the fact is that there are also a LOT of dumb customers willing to buy crap. God knows why.
Just look at the trending / best selling lists on Steam. There’s shit on there that I wouldn’t play if you paid me. Yet somehow there’s enough of a customer base for that that they sell it.
Honestly, Steam should look into setting a minimum quality level for things sold on the platform.
Well, the fact is that there are also a LOT of dumb customers willing to buy crap.
As much as everyone love Oblivion…it all started from there with the $9 horse armour DLC.
God knows why.
Yet somehow there’s enough of a customer base for that that they sell it.
Kids. Fucking kids. Thankfully I am never that stupid to buy individual DLCs even when I was a child, which is compounded by familial circumstances and education, but kids will be kids. Either they stole their parent’s credit card to pay for useless virtual items, or they were spoiled and never taught with financial literacy.
Yess. I boggles me that the narrative is still “devs this, devs that”. It doesn’t take becoming a game dev to understand that actual software developers are not calling shots on plot twists, monetisation model and so forth. Like, what the hell is wrong with people babbling about devs?
Mostly agree, 98% of requests are unrealistic. Most of these requests are not even simple.
But many times, things ARE fucked. And when that happen - dear gamers, don’t curse devs, as a team. There was shitty ceo, who couldnt make a straight decision or changed them 200 times a day, because felt some popular new feature totally must be in the game, that ruined whole concept. Many times, the concept were shitty from the start, then blame director of that. Even more often, publishers pushes their financial decision over dev team (hello Helldivers2 vs Sony). Yet another time, some lawsuit shitstorm happens, that makes devs scrap something (hello Palworlds vs big_n). And many times, its all together.
Gamers who don’t know any programming, or maybe made a little utility for themselves. Looovee to bring out the old “just change one line of code”, “just add this model”, etc. to alter something in a game.
They literally do not understand how complex systems become, specially in online multiplayer games. Riot had issues with their spaghetti code, and people were crawling over eachother to explain how “easy” it would be to just change an ability. Without realizing that it could impact and potentially break half a dozen other abilities.
In the wake of all the layoffs and such I don’t know if any former employees have (as vaguely as possible) discussed the codebase yet. It seems like such an absolute nightmare.
Absolutely, it’s impossible to know how much. But it’s a lot easier to grasp that it’s rarely just “changing a few lines” when it comes to these types of situations.
Specially since many programmers have encountered clients, managers, etc. who think it’s that simple as well.
And even then it’s sometimes impossible because how much can you keep in your head at once. Everybody specializes on these large projects. I may have 30000 ft view of how things operate but getting down into specifics can be hard. I have some intimate knowledge of the learning management system we develop for, which is way less complex than most games, and there are always little gotchas when you make code or architecture changes.
When a dev with game dev experience says something should be easy to fix, it’s under the assumption of a reasonable code base. Most games are built off of common engines and you can sometimes infer how things are likely organized if you track how bugs are introduced, how objects interact, how things are loaded, etc…
When something is a 1 day bugfix under ideal conditions, saying it will take 6+ months is admitting one of:
The codebase is fucked
All resources are going to new features
Something external is slowing it down (palworld lawsuit, company sale, C-suite politics, etc…)
Your current dev team is sub par
Not that any of those is completely undefendable or pure malpractice, but saying it “can’t” be done or blaming complexity is often a cop out.
Can’t be done is usually shorthand for the cost massively outweighs the benefits. No different from remodeling a building. Like coding, literally anything is theoretically possible but sometimes you’d have to redo so much existing work it’s never going to be worth it.
In the real world there is no entirely reasonable code base. There’s always going to be some aspects of it that are kind of shit, because you intended to do X but then had to change to doing Y, and you have not had time or sufficient reason to properly rewrite everything to reflect that.
We tend to underestimate how long things will take, precisely because when we imagine someone doing them we think of the ideal case, where everything is reasonable and goes well. Which is pretty much guaranteed to not be the case whenever you do anything complex.
I agree, real code always has tradeoffs. But there’s a difference between a conceptually simple change taking 3 weeks longer than planned and 6 months. The reality is game code is almost always junk and devs have no incentive to do better.
Getting a feature functional and out for launch day is the priority because you don’t have any cash flow until then. This has been exacerbated with digital distribution encouraging a ship-now-fix-later mentality.
This means game devs don’t generally have experience with large scale, living codebases. Code quality and stability doesn’t bring in any money, customer retention is irrelevant unless you’re making an mmo.
The correlation between code quality and game quality is almost negative. When you’re doing groundbreaking stuff or going for your own artistic vision it’s tough to code well, even more so when you hit a jackpot and have to expand quickly (e.g. League spaghetti, Palworld)
Diablo4 has memory leak issues. As a software engineer myself, I just don’t see any excuse for a game this long in production to have memory leak problems.
There is no doubt that a lot of games are getting rushed without being properly tested.
Tbf memory leaks can be very hard to diagnose and can also be hard to avoid in any software written in a language like C++, which is probably what Diablo 4 is written in.
In large scale online games you have issues ranging from obscure things causing memory leaks based on drivers, hardware combinations, etc. and all the way to basic things getting overlooked. One of my favorite examples being GTA5 online.
They forgot to update a function from early testing, and it was in the game for about a decade before someone else debugged the launch process. And then realized that it was going through the entire comparison file for each item it checked on the local list. So “changing a few lines” ended up reducing initial load times by up to 70% depending on the cpu and storage media.
That’s kind of a funny example because, on a quick skim, nothing he did was exceptionally clever or unusual (other than workarounds for not having source code). R* basically paid him 10k for some basic profiling that they never bothered to do.
Well why didn’t you start 6 months ago. It’s not my problem. I paid full price. If you wanna be left the fuck alone sell games for $15 and take your time no one will bother you. When you start asking $80 a game the price sets expectations. Devs lack of planning is not my problem as a consumer.
Gamer who doesn’t understand how gamedev works gets mad at guy telling them they don’t get how gamedev works, demanding their treats get here, right now anyway after being told it actually takes a bit to make. News at 11.
Yeah, you’re probably right, the video game you personally made is probably better and we’re just lazy. BTW I demand 20 hours of brand-new content to be released next week, and it better be cutting-edge, uniquely interesting and creative, bug-free and $4.99, or else you’re a lazy dev, too.
It’s genuinely funny watching these people learn absolutely nothing when slapped in the face with hard facts.
pcgamer.com
Najnowsze