Play game
RAMpage(for Godot Wild Jam 96)'s itch.io pageRate this game
In order to rate this submission you must be logged into itch.io and have submitted your own entry. Anyone with an account can leave a comment.
Godot Version
4.7.1
Theme Interpretation
The player charges into enemies to kill them, the player is also a robotic ram(both relating to charge). Also you charge into castles
Source
https://github.com/Jagdoggo/Godot-Wild-Jam-Game
Discord Username(s)
Jagdoggo, TheSniperKing302
GWJ Participation Level
1
Team Size
2
Generative AI Disclosure
I confirm that this jam entry does not contain any AI-generated content
Leave a comment
Log in with itch.io to leave a comment.






Comments
I had fun, it worked for me after loading for ~1 minute, enemies were working and attacking me. I answered to another person's comment - you unfortunately have very unlucky key binding for web build, if you try to ram forward (up) using ctrl, you will close the browser window (ctrl+w closes current tab/window in most browsers) 😅 It is pretty nice game other than that :)
sorry about that it was a slight oversight for the web version and also the loading time seems to be navigation baking or somthing like that, im trying to fix some of the issues so i can fix the issues after the voting ends(i would change it now but were too late)
Interesting entry, the charging mechanic fits well in a stealth game. I feel like it could be expended, for example, charging in the chests instead of opening them, or more breakable walls.
These are all good ideas. Might try as a different game/mode
I encountered an unknown bug that caused the game to crash for me right at the beginning, and I couldn't access all of the content. Maybe you can open a ticket and upload a new version without the crashing problem?
were you playing in browser? if you used ctrl+w it closes the current tab/window :P I did sadly the same... retried with using the z/x buttons. To @Jagdoggo - this key binding combination could be disabled in web build and also not mention in the instructions screen, it is very... unfortunate :P The game was pretty hard to play in browser like that but I gave it 10 minutes and had some fun :) Don't know if it's a bug on my end or it's desired mechanic, but do I understand correctly that you only deal damage ramming into guards once you get some damage points from the chests in the castle? It made it really hard to beat them, yet still entertaining :) Didn't fully finish the first castle, but probably would if the key bindings were a little easier to play in browser. Nice game overall, just this unlucky key binding.
edit: i think it was probably ctrl+w charging you could try ctrl+x instead but i know its not as easy.
were you playing on web or did you download(also linux or windows), either way we tested on all and it worked but we can do some testing.
I would say giving feedback to the charge or ram would be nice and the music is good fits the vibe I also think the damage buffs should do more and the player should do more damage and lower the slowdown or just remove it. other than that, I loved the atmosphere and the ram still felt good, great job
Thanks for your advice. Even if we didn't make the best game ever we still had fun!
The difficulty seems a bit out of tune. I didn't seem to have killed any enemy even after getting a dozen chests and ramming into them a bunch of times. Also you are kind of done for if you ever run out of charge next to an enemy, which makes the game really punishing, especially at the start.
It can be quite fun though once you're "in the flow" but with the game freezing for a looong time at the start of each run (I assume while the procedural generation does its thing) it's a bit frustrating.
I will say, for the simplicity of the assets and audio, it works quite well altogether giving the game a nice punchy and silly feel.
Thanks for the feedback!
If you download the game then it doesn't take as long to load but, the thing is the enemies wont move toward you(until it loads). We think this is the navigation baking after generation but were still not entirely sure.