2.50 star(s) 97 Votes

-CookieMonster666-

Message Maven
Nov 20, 2018
12,122
18,004
No the programming is awful. Maybe a first year student might find it good. It can't even handle the base cases for most functions let alone any edge cases which is why the ikea bs bugs out and needs restarting why theres no autosave, why theres no basic mouse functionality for the idiotic minigames nor highlighting. Thats's why you can accidentally click home without any prompt during crappy minigames and lose all progress and have the mouse set invisible. That's why when loading in fullscreen it will randomly go to a small window with the buttons offering to minimize since it thinks it's still fullscreen. It's beyond amateur. The only people who would call this good are the sort of people who expect me to do their entire job when they ask a question on stack overflow.
But like Sir Anal said, you're conflating programming with game design. Those aren't the same thing.

Programming Issues
  • Have the mouse set invisible — I haven't seen this once, but if it's suddenly disappearing like you describe, that would definitely be caused by a bug in the code.
  • Full screen mode randomly switching while loading to a small window while thinking it's still full screen — Another bug, but another one that I haven't seen once. The game never starts in full screen mode for me, but I haven't seen the switching / dropping out bug myself at all. It sounds like a driver issue, especially because I don't see anyone else in this thread mentioning a bug like this at all. But it could be an issue with the programming, so I'll give you that one.
  • Ikea bugs out — Obviously, if this is actually bugging out, that could be a programming issue. But again, never seen that happen, so it doesn't sound like a flaw in the game's code.
Game Design Issues
  • No autosave — That is a developer choice. Games don't always have autosave functions programmed into them, but that's not bad programming but bad game design. Compare a variety of games on Steam, for instance: some games have autosaves only, some have both autosaves and manual saves, and some only have manual saves. It's something a programmer has to specify, which makes it game design (i.e., a choice about what's available in the game).
  • No basic mouse functionality — Another choice by the developer. While there will typically be some built in, generally most gaming engines don't have clearly defined actions tied to keyboard keys, mouse buttons, etc. Those usually have to be assigned by the game developer; Ren'Py (which this is not, ofc) is an exception to that rule.
  • No highlighting — This is definitely a game design issue. Again, in most gaming engines, there is no automatic highlighting for an on-hover event. On-hover will be detected, but the results of that detection must be specified by the game developer. That's not a flaw in programming, but an oversight or choice by the developer (i.e., game design).
  • No prompt to avoid losing progress when returning to the main title screen — Another choice by the developer. A programming issue would be if Nerdworks tried to have the game warn but an error resulted (or the method was never called). This seems pretty clearly a choice / oversight by the developer instead in designing the user experience during the game.
You might do both game design and coding when developing an application or whatever, but those are absolutely not one and the same.
 
2.50 star(s) 97 Votes