#Firestone idle rpg sucks Pc

Where my brain throws a BSoD is when someone doesn't allow you to access critical settings (such as dark mode, or to turn off sounds) until you get far enough in the game Like, the 'yeah, you have to hammer your mouse like a motherfucker for a few hours before you can have automation, and btw, we ban people for using autoclickers' thing is pretty obnoxious as someone with hand problems (i personally actually require automation frameworks to play minecraft, let alone incrementals), but i can sorta kinda understand where that comes from (although i consider it unconscionable) a fun variant on that i encounter sometimes in incremental games: locking qol features necessary to play the game comfortably behind progression. (i've run into this a few times)ġ00% concur. If you lock QoL features that would allow people with disabilities to comfortably play your game behind a paywall, you have not only failed as a developer but as a human being as well. the distinction is important for evaluating the nature of the problem, and for pursuing solutions with people in the future. I still consider it a dick move, but it was a dick move born of 'meh, this isn't a real problem, but whatever' not 'fuck you for wanting things to be better'. there is a degree of neglect and apathy at work here that far outweighs the malice that easy easy to assume absent context. The person didn't understand that there was a meaningful accessibility concern. The problem was renaming resources for holiday events, and the idea that arbitrarily renaming resources based on calendar date could at all be confusing to someone who is nominally a native speaker was essentially incomprehensible. Now, in the interest of fairness, as the person with the complaint being shared here, i feel it's important to limit the appraisal of hostility:

If you can't make your game accessible to people with disabilities and it is of a genre where it would not significantly impact gameplay, you have failed as a game dev. Annoyingly i can't test it because they have hard programmed the game not to even load on mobile devices, which was my original point, they had to go out of their way to do that. If you have any particular game in mind, i don't mind testing it.Īs for Peter Talisman, tbh, it just sounds like the game is poorly optimised. The hardest part about 4 of the games were that they were hosted on Kong, which has a 'doesn't work on mobile' splash, but once i worked around that the games worked fine on mobile.Īs expected, the only issue was resolution as there is just no way to force them to match the resolution of a mobile screen, so you generally just using 80% of the screen so you can see the whole game window. I tested 6 others in total before i got bored and every single one of them worked fine. Tbf, one game had a perfect resolution and seemed to be designed specifically to be played on mobile so I'll ignore that one. I randomly googled 'idle webgl games' and got and started testing the games in order. I don't pay enough attention to know what games are running on, so i decided to test this. To your credit though, it would look pretty fucking cool on an iPad. An iPad would definitely just lock up for 30-40 seconds when that happens. When you break through a wall of wheat, it seems to recalculate all of the pathing and it torches the CPU.

#Firestone idle rpg sucks Pc

Even if they allowed it on mobile though, they'd just be getting a bunch of angry feedback about how broken it is.Īlso fwiw, I JUST bought a brand new PC with an i7, 3080, and 32Gb of RAM and the game still chugged for me at certain points. In short, it might run on an iPad, but probably not well. Can't tell you how many sites I've seen that have a custom handler for scrolling that just completely fucking breaks the auto-hide on the Safari toolbars. Not to mention that you have to account for portrait resolution, differences in drag and drop behaviors, and the whole disappearing address bar nonsense. Dunno what games you're playing, but I've only seen a handful of WebGL games that actually worked in a mobile browser.

I do web and mobile development and I can tell you that Peter Talisman is using WebGL and support for that on mobile Safari and Chrome has been straight garbo forever.