I’ve told this story countless times, but I think it’s the perfect example of why I’ll always choose Godot given the chance.
Do you know when you’re playing a single-player game and you have to switch controllers and now your new controller doesn’t work? Or when the menu can only be navigated by Player 1? Well that happens because the game is only looking at input for the first controller. Story time, a few years back I was playing around with making a single-player game, I tried Unity and Godot, both suffered from this, you had to duplicate the input for any controller you wanted to make sure worked for all of them. So I took a look at Godot’s code, and in a couple of hours I had an “all controllers” option in the combo box to select which control to get input. I opened a PR, maintainers thought it was a neat feature, and now everyone can use this, and afaik Unity still suffers from this and there are dozens of assets on the store that try to fix it in different ways.
Best I’ve got doesn’t have to do with Godot, but I think its neat.
The year is 2003 or 4, and I am beta testing the 0.5 release of Project Reality, which later more or less evolved into Squad.
I know nothing about coding at this point being still in middle school.
What I do possess is apparently pattern recognition.
We are in a last minute waaay overextended beta testing session trying to iron out a mystifying bug:
The whole new feature of implementing squad specific kit bags that are only obtainable at certain in game locations is working.
But… sometimes it is not. At all. Sometimes you can grab an unlimited number of kits without restriction, sometimes you cant and have to follow the newly coded rules that limit kits by being in a squad, and having a total pool of requestable kits per squad and per your whole team.
We get in vehicles, we get out of vehicles.
We go to different parts of the map.
We die then respawn via suiciding.
We die then respawn via being shot, killed as infantry with different weapons, killed inside different vehicles.
We join and leave amd create and disband squads.
We die on the water, we die on the land.
We die on islands, we die on beaches.
We shall never surrender!
Er, well the goof off testers wont, the devs are getting frustrated.
Absolutely none of this has any discernable effect on the problem.
After what must have been about 3 hours… we are basically just fucking about as testers as the actual devs including the one who actually coded the new system is in despair, we are gonna have to push back the massively advertised release date of about 8 hours from now.
Fucking about a bit and watching random zany attempts at most impressive suicides with those who we are at this point joking are just the chosen ones able to spawn unlimited specialist kits with c4 and anti tank weapons…
Something clicks.
I hold down the tab button to bring up the scoreboard with player names.
I start telling a few of the testers who have not already left to try spawning kits at various locations.
Everyone goes sure man why not.
After doing this with myself and 5 other people… I have a theory.
Everyone who has non alphanumeric characters in their name is able to break the kit limitation rules, everyone else is bound by them.
The lead dev is skeptical, but checks the code again anyway.
About a minute later he screams over the mic on teamspeak.
About 10 minutes later, he has fixed what was probably a really simple but easily overlooked bug in how early python parses string values and passes them to other functions or data types.
The server is back up, everything works correctly now, and Project Reality 0.5 is released only a few hours behind schedule, instead of the next week or two when the team would be able to organize another large scale testing bout.
Lol and thats the story of how i saved a mod release date wooo!
I’ve told this story countless times, but I think it’s the perfect example of why I’ll always choose Godot given the chance.
Do you know when you’re playing a single-player game and you have to switch controllers and now your new controller doesn’t work? Or when the menu can only be navigated by Player 1? Well that happens because the game is only looking at input for the first controller. Story time, a few years back I was playing around with making a single-player game, I tried Unity and Godot, both suffered from this, you had to duplicate the input for any controller you wanted to make sure worked for all of them. So I took a look at Godot’s code, and in a couple of hours I had an “all controllers” option in the combo box to select which control to get input. I opened a PR, maintainers thought it was a neat feature, and now everyone can use this, and afaik Unity still suffers from this and there are dozens of assets on the store that try to fix it in different ways.
That is a neat story, thanks for sharing!
Best I’ve got doesn’t have to do with Godot, but I think its neat.
The year is 2003 or 4, and I am beta testing the 0.5 release of Project Reality, which later more or less evolved into Squad.
I know nothing about coding at this point being still in middle school.
What I do possess is apparently pattern recognition.
We are in a last minute waaay overextended beta testing session trying to iron out a mystifying bug:
The whole new feature of implementing squad specific kit bags that are only obtainable at certain in game locations is working.
But… sometimes it is not. At all. Sometimes you can grab an unlimited number of kits without restriction, sometimes you cant and have to follow the newly coded rules that limit kits by being in a squad, and having a total pool of requestable kits per squad and per your whole team.
We get in vehicles, we get out of vehicles.
We go to different parts of the map.
We die then respawn via suiciding.
We die then respawn via being shot, killed as infantry with different weapons, killed inside different vehicles.
We join and leave amd create and disband squads.
We die on the water, we die on the land.
We die on islands, we die on beaches.
We shall never surrender!
Er, well the goof off testers wont, the devs are getting frustrated.
Absolutely none of this has any discernable effect on the problem.
After what must have been about 3 hours… we are basically just fucking about as testers as the actual devs including the one who actually coded the new system is in despair, we are gonna have to push back the massively advertised release date of about 8 hours from now.
Fucking about a bit and watching random zany attempts at most impressive suicides with those who we are at this point joking are just the chosen ones able to spawn unlimited specialist kits with c4 and anti tank weapons…
Something clicks.
I hold down the tab button to bring up the scoreboard with player names.
I start telling a few of the testers who have not already left to try spawning kits at various locations.
Everyone goes sure man why not.
After doing this with myself and 5 other people… I have a theory.
Everyone who has non alphanumeric characters in their name is able to break the kit limitation rules, everyone else is bound by them.
The lead dev is skeptical, but checks the code again anyway.
About a minute later he screams over the mic on teamspeak.
About 10 minutes later, he has fixed what was probably a really simple but easily overlooked bug in how early python parses string values and passes them to other functions or data types.
The server is back up, everything works correctly now, and Project Reality 0.5 is released only a few hours behind schedule, instead of the next week or two when the team would be able to organize another large scale testing bout.
Lol and thats the story of how i saved a mod release date wooo!