Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

What would you have done differently?

A topic by Sundler created Mar 31, 2024 Views: 438 Replies: 23
Viewing posts 1 to 18
Submitted (2 edits)

Now, that the jam is over, perhaps we could reflect a little on our projects.

I spent a lot of time making my game endless, in keeping with one of the themes.  But, I later realised that the recommendations insist that each entry have an ending.  So, I scrapped it all and switched to using set maps with some procedural generation, to ensure each play through is different.  Had I known, I would have avoided wasting so much time on making an endless 3D open world.

What would you have done instead?

Submitted(+1)

The finale of our game expects the player to make a leap of faith.  Already saw one player say "Oh, I guess I can't go this way" and turned back around.  Should have added extra hints or blocked their path behind them.

Submitted

your endless 3d open world can still have an ending i.e. giving players the choice to end the game

I could have spent more time researching on the genre. I thought I have a unique concept but it turned out several people went for almost the same idea lol

Submitted(+2)

i would've not wasted a whole day trying to learn 3d with no prior experience and another whole day trying to code fancy enemy AI

Submitted(+1)

We had a testing build on Tuesday but it didn't test 100% of the features of the game. This ended up biting us later on the last day because there were several features that worked well in their own environments but needed additional adjustments to work together. I knew the risks going in but we made all of our assets during the jam and some of them weren't ready for testing until later in the jam.

Submitted(+2)

Checking for a working VPN Access to my NAS before going on holiday with my laptop on tuesday and dont have access to the blendfile and prepared assets. 馃槄

And dont plan on submitting while on a train. The upload took ages and I was really dieing inside. Getting the submit through 3 Minutes before the end was just lucky. Not again. Too much stress. 馃槀

But all in all I am quite pleased with my first itch.io Jam. 馃檭

Submitted(+3)

Not fully play testing a complete playthrough. All my maps played correctly but string them together with a little vestigial code acting up and now I'm not sure my game is even completable. It really sucks because I could very easily patch it out, but now every one who plays is going to quit for having absurdly high random encounters.

Submitted

I was using Godot with GDScript and it bit me a couple times in the a** while trying to refactor something, so that was no fun. And not having a fully typed Language made it also more error prone to use. So next time I will trying ont Godot鈥檚 c# support and hope for the best. ;)

I also lost focus of what is important and whats not gameplay wise, thus I often found myself focused on tasks like generating assets but not having actual gameplay. So next time I鈥檓 focusing on getting gameplay done first and assets / polish last!

Submitted

Did you set up VS Code with Godot? I found that helps a ton with gdscript.

Submitted(+1)(-1)

Yes I actually did and yes it helped, but refactoring over Script borders did not work very well for me and IntelliSense wasn鈥檛 helping 50% of the time, unfortunately. So ya, Ill try c# next time, maybe the experience is a better one :)

Submitted(+1)

Just one important thing to know about C# w/ Godot: You cannot build for web yet. They plan to revisit this in November when .NET 9 is released.

Submitted(+1)

Ah that鈥檚 good to know, thanks! Unfortunately the web build didn鈥檛 work very well with standard fog (I don鈥檛 know why) and mouse capture did鈥檛 work either, so those two things hindered my using the web build anyways :/

Submitted(+1)

You can't build for web with GDScript either on the newest 4 versions, you get the ShadedArrayBuffer error, which itch,io has a fix for when you upload, but there's also a "Cross Origin Isolation" error that as far as I can tell can't be fixed for web yet either.

(+3)

most important thing i've noticed is modularizing your code, in our case using unity. The bigger your files become, more cluttery and difficult it will become to modify or implement more features. Adapting an early "its ok to do it like this and will fix it later" can snowball and end up doing everything the easy way and making everything down the road harder and slower.

Submitted(+1)

I would have done map testing days earlier. I ended up scrapping the dungeon generation system I was working on, and instead I had to deal with grid issues down to the deadline. I also would have ironed out animation bugs with the enemies from the very beginning. More knowledge for next time I suppose!

Submitted(+2)

I ended up sticking a lot of the functionality into the FPS controller rather than abstracting it properly. I think with game jams you tend to throw a lot of stuff into the easiest place because... Well, because you don't have a huge amount of time to architect it properly.

It resulted in some right old spaghetti signals back and forth to get some of the features working for me!

Submitted

Haha, the amount of children I have telling their parents what to do is crazy! Give me all the ../../../'s.

Submitted (1 edit) (+1)

I've done a "fake" 3D game like EOB before but this time I wanted to do an actual 3D game. In the end I realized that the benefits are less than the new complications that a real 3D dungeon crawler brings to the table. Should have sticked with the fake 3D.

Submitted(+2)

I really really wish I had done some basic sound effects. In the dash for final submission, I cut sound effects from the plan; in retrospect, I wish I had still done like one chop for hits and one swish for misses and just cut everything else.

Submitted(+1)

Must admit, lot of things worked smoothly as intended, but beside the overscope - which partially was calculated in the first place - I lost a lot of time by bringen realtime enemies into the mix. My expectation was to do turn based battles in a seperate screen, but after switching to a very different them铆ng after a few hours, realtime confrontation seemed a much better fit. Further, I should have sticked to the smaller designs of the maps, but that felt to uncrawly. Anyway, although the game is very unfinished in its set dressing and lacks multiple enemies, I'm still happy with what I achieved in that time frame.

https://sunsailor.itch.io/litany-from-beyond-dcjam24

Actually made something lol. Unpredictable healh issues block a lot of my plans but I was really hoping to get some time to join this as it's one of my fave genres and I've had some ideas kicking around for a while.

Submitted (1 edit)

Nothing actually, I litteraly did everything I could in the few days I had, this gives me the rare feeling of "being completly happy with your Gamejam Game" haha, I know my game is missing a lot and has a lot of flaws but I really feel like I directed my energies very well this time and feel like I matured, dunno this is getting deep anyway this is my game I need to do some advertising otherwise I'll come back here to write "Wish I advertised more" lol

https://itch.io/jam/dcjam2024/rate/2616531

Submitted(+1)

I ran into an issue of not making enough time for the jam throughout the week or so either due to things that came up or just not working on it, so better time allocation would definitely have made it better (I definitely would've had more time to bug fix then lol). I also probably could've gone a lot harder on the theming because right now it's sorta kinda related but it's not great (in my opinion)

Submitted(+1)

I had too many planned things during the weekend that took away the time i had available. Basically both weekends were booked up with prior commitments, and the only free time i had was after my already full time job. I still managed to put 56 hours into the game (Thank you steam for tracking that) This lack of time introduced some heavy crunch and caused a lot of corners and play testing to be cut.