All of my lol. Just... All of it. Tell me, how many years of Java experience do you have? When did you last work with C++ or Ruby? What are your thoughts on throwing exceptions versus returning nulls for errors?Sticky said:Thank you non-programmer for sharing your knowledge on this programming related matter.BreakfastMan said:This doesn't make any sense. Like, at all. Unless the programmers behind tomodatchi life are idiots, allowing gay marriage shouldn't require more code changes than a couple of lines here and there. Which is about as much as those other changes would require. I mean, it should just require a change to some if statements. That really should be it.Eve Charm said:Changing a bunch of mii's singing to a bunch of mii's doing a rap battle is changing a bunch of text boxes.Scrumpmonkey said:But the team was already adding development features :/ They already did what you said they never do.Sticky said:Snip
http://nintendoeverything.com/bill-trinen-talks-more-about-tomodachi-lifes-localization-changes/
They are changing mini games to entirely new ones. They are developing the game for a western audience. Your post makes so sense when this is the case.
Also changing two people dressed up in sumo outfits running into each other and pushing to two people in football outfits running into each other and pushing is just changing avatar outfits. ((also we know what sumo is out in the west nintendo ;p))
They aren't changing the hard code or core mechanics of the game, which what would be needed.
Also, oh no, rewriting logic! Changing data structures! How horrifying! Sorry, but if you are trying to make this sound scary... You are doing a real shit job. This might work on someone who isn't programmer, but it is doing nothing but giving me some laughs.No, it's not as simple as 'changing a couple of text boxes'. The game was randomly assigning genders to the characters, it just so happened that sometimes you could make two males marry due to the nature of the random gender assignment.
To make this game recognize gay marriage, you would have had to change the data structure which the game interprets in order to correctly have it identify any gender as marriageable. THEN you would have to literally re-write in the game's logic what it means to get married. To the game, who only deals in absolutes, marriage is only for two clumps of data structures that have opposite gender tags. The game is merely instructions that has no common sense to interpret it any other way.
Right... And where did I say the solution was to randomly assign gender tags, exactly?This isn't to mention the other problem: because the game was randomly assigning gender tags, this was resulting in crashes and hardware instability. Because a male having a female tag is unexpected behavior to the system and it doesn't know how to recover from this.
You are far over-selling what would likely need to be done. More complex changes have been implemented in patches.So no, it's not just "changing a couple of text boxes". We're talking an entire round of development just to change this one feature. Localization teams, once again, don't add features to games or to the original design document.
EDIT:
The question isn't whether or not it uses objects. It is whether it actually uses them well and the code isn't incredibly brittle.And no, you can't say "BUT IN MY DAY CHANGING SOMETHING LIKE THIS SHOULD CAUSE NO PROBLEMS AT ALL!" And still retain any credibility that you're a credible programmer. And then pretend that you know what MVC and OO has to do with this discussion. Or are you seriously trying to say that this game, likely written in C++, doesn't use OBJECTS?BreakfastMan said:Yes, I have. I have written quite a few programs in my day. If the programmers behind it weren't terrible, changing something like this should create few to no problems. Yes, changing a few lines can create unintended consequences... But that is why good programmers use techniques like MVC and OO, among others. To separate out functionality and logic so as to avoid most of that shit. If changing something so trivial completely breaks the game, there is likely something very wrong with the code.
Like, the professional game company, that writes dozens of games and millions of lines of code, doesn't know about the glories of object-oriented programming in the age of visual debuggers and the internet? That is really all I'm reading from your post: You somehow think that using 'OO' would have fixed a problem that is likely being caused by objects not being interpreted correctly in the first place. Then you turn around and say "I'm a credible programmer, honest!".
That is taking my words completely out of context. A change this trivial to code that is already working really shouldn't cause it to explode. Their code shouldn't be this fucking brittle.Also "Something so trivial shouldn't break the code if you do it right" is only something someone would say if they haven't ever had to pull their hair out trying to understand why a program refuses to compile.