Hm…. I hadn’t thought about a full game, but you’re making me consider it for sure. I’ll spend some time in the lab with it, haha. Thanks for all your feedback!
This is genuinely great feedback, thank you for playing the game, and I’m glad you enjoyed it!!
WaMa was conceived from the “oh no i’m stuck!!” meme that went around a couple years ago. I was surprised that nobody’s done it as a game, other than as a visual novel. Since the joke is so simple, I wanted to get the player in and out as quickly as possible, so it didn’t overstay its welcome.
A more complicated disassembly system would be a great basis for a full-fledged game. Your ideas with the levers and commands in level 3 in particular work with that really well. The same goes for the player control being improved - maybe the character is a robot and can move their legs up and down hydraulically.
But, for a game I threw together in 3 months (I wanted it to be 1!!!), I think it’s ok enough to at least get the point across, and deliver the punchline.
Thank you again for the feedback, I will definitely keep it in mind for future projects!
(and the standing stance bug - I probably should do that. this game runs on shitcode because of the timeline I made it in haha)
Did it only happen during long sessions, or during short sessions as well? What team were you bringing into the mission? What is your computer’s CPU model?
The through-line in all this is NVIDIA GPUs; all three ppl who have reported it use an NVIDIA card. Unfortunately, it’s an engine problem, and I can’t fix it myself. I’ll let you know when a new version of the engine is released, and will do a new build then. Sorry about that.
If you DO want to find the logs, they’re in %APPDATA%/Wrangler/logs
prototype used Godot 3.5, full game uses Godot 4.0.2, so there’s an entire rewrite in-between
the fact that the prototype worked fine does suggest to me it’s an engine problem, the code used for the startup screen absolutely was present in the prototype.
cursory searches say that error comes from C++ pointer problems, which definitely means it’s on the engine side. nothing i can do about it until it gets fixed upstream, sorry about that
this is an incredibly detailed bug report and i appreciate that. i’ll give ‘er a look, might be out of my control if it’s an engine bug (i really hope not)
I’m not sure! I’ve considered DLC - my only problem is, whenever you add 1 creature and 4 moves, you have to add bottom animations for all the ones it can be paired with. So right now, that’d add at least 50 new animations to do, and that number grows exponentially with each new creature.
I’m torn, honestly - I do understand where you’re coming from. It’s a strategy I borrowed from demos I used to play. I have a vested interest in having you get the full game, and that’s what the popup is intended to do. I don’t think I will remove this, sorry.
Thank you! I’m not sure about that, I do like the straightforward-ness of the mission selection screen, and an overworld map wouldn’t fit the motif of the game.
Shoot. I’ll have to look into it further, then. I’ll let you know if and when I can reproduce it. I have a theory where the issue is, I guess my fix wasn’t enough, sorry about that
Sure! Your information was definitely a help. I think I found what was causing that issue - it has to do with the elite enemies’ script, it should be fixed in the next version (1.0.3).
