About Fanatrick

Entries

 
Ludum Dare 35
 
Ludum Dare 34
 
Ludum Dare 33
 
Ludum Dare 30

Fanatrick's Trophies

Fanatrick's Archive

Slimon Sways playthrough video

Posted by
Sunday, May 1st, 2016 9:06 am

Far later than usual, but yeah D:

Play it here:
http://ludumdare.com/compo/ludum-dare-35/?action=preview&uid=39646

Oklahoma Tempest [END]

Posted by
Monday, December 14th, 2015 10:53 pm

Oklahoma Tempest

Posted by
Saturday, December 12th, 2015 8:01 pm

ColoradoTempest

You are the Munchster – development aftermath

Posted by
Wednesday, August 26th, 2015 8:54 am

 

This is our submission, yay :>! After 72 hours of coffee, energy drinks, bare necessities of sleep and thousands of lines of code I can safely say I’m proud with what we could come up with considering this was the first time we teamed up. We got it finished 10 minutes before the clock, the last 8 hours of development were really stressful, but through mutual moral support we somehow made it.

You can check the game here:
http://ludumdare.com/compo/ludum-dare-33/?action=preview&uid=39646

So. Onto the aftermath!

The Good:

The brainstorming. We brainstormed very rapidly and didn’t have to change many things as we proceeded to add more stuff. This is generally what we agreed to enforce from the beginning, since my  previous ludumdare entry suffered from feature creep and costed me around 5 hours of development time that could’ve been spent elsewhere. For You are the Munchster this creeping was nonexistant and while we couldn’t manage to add everything we wanted we did succeed on adding most of the planned gameplay elements.

Bunch of playtesting. I playtested pretty much every 10 minutes. The compilation times weren’t long which helped a lot, the code management was tidy this time and all the systems implemented were working as expected. There were some minor hiccups with the AI where the AI felt very overpowering for the player, but with this constant playtesting I could easily distinguish what would work, what was balanced and what would feel dull.

*Teamwerk*! Like I said through moral support and not becoming bored with each other’s constant presence either in chat or voice we could work more rapidly. Even when screwing around our cooperation had a very big impact in the stress relief, and while other members couldn’t feel the difference since this was their first time developing a game, I could tell right from the day 2 that I couldn’t finish the coding part without the stress relief the gang brought. In the more technical department, I feel each of us played a very impactful role in the final result. The pixel artist made some kickass animations, furniture and, oh god, that menu background sealed the deal. The composer managed to blow our mind with how fitting the track was and the sfx was neat and fitting. We all knew what we had to do and that we had a long way to go from the start, there were really no setbacks when it came to teamwork. The atmosphere was laid back and we all did our responsibilities well.

The coding. I did the programming and I believe I did a good job overall. Having the most expertise on the team I could lead the team to the result and implement systems that would support everything they made. The AI was the hardest part, as the enemies had to move around the house with stairs and the pathfinding was a bitch to make. The dynamic lighting took a chunk of time as well, since I didn’t really want to use any shaders in this project so the older machines can enjoy it as well. Figuring out how to detect if the player was in shadows was cake, even though at first I thought it would chunk some time too. The platforming, ghost jumpthrough slopes, etc. was implemented very quickly as well.

Trello worked wonders! We used trello as our resource base and couldn’t be happier with it. Nearing the completion of the project we steered off the planning part of the platform and only used it for file management and uploading, but in the first 2 days I don’t see how could we ever keep track of our progress without trello or some similar platform. It gave us a very good chart of how we were progressing.

The Bad:

Figuring out the winning condition. We changed the winning condition on day 2, originally the player had to scare the little kid instead of eating the residents. On day 2, this whole concept seemed dull and not satisfying, so we decided to make one last change to the core mechanics. This required more work for the pixel artist, the hardest part being the bite animation of the main character. This set us back a fair bit but wasn’t something we couldn’t handle.

The level design. We didn’t leave much time for levels, the game only features 3 in the entry build and even that was enough for few misplaced tiles and objects. The switches and lighting works and every enemy has it’s own set of things he does at random, the wallpapers are rendered properly and most of the stuff works fine. When we decided 3 levels were enough we were coming from a standpoint that people need an experience in a matter of 15 minutes at most. This proved to not be the case and some people were left unsatisfied after completing the game.

The difficulty. The levels are exponentially harder, as adding another enemy in the house makes sneaking and hiding much more challenging, especially when choosing your time to bite. During the playtesting I naturally got very good at the game, obviously I knew all the game mechanics and how they worked from the very moment they were implemented. I was aware of that, and I didn’t want the difficulty to annoy the player too much. In the end it seems the difficulty part of the game is a well fit for more casual gamers who get hooked on it and are willing to spend some time studying mechanics, but most of the community loses interest if they continually rush the level and die. This game is purely stealth based and I believe we didn’t stress this enough. If we had more time this could’ve been easily solved by making the levels easier, but making around 3 more hard levels so everyone can enjoy.

 

That’s it for the development aftermath. This LD Jam was much more exciting than the last Compo I attended, I can’t stress enough how greatly the teaming up went. From now on I doubt I’ll ever play Compo again, the Jam is just so much more fun for me =]

Cheers,
Matthew K.

We’re in Jam!

Posted by
Thursday, August 20th, 2015 10:18 pm

Hey, I’m Matthew!… That should do for introduction.

I debuted in ludum dare compo with Ignis about a year ago, the game received most praise in graphics and theme which were the main focus of the project. Other scores were really mediocre but still the feedback was mostly positive. Insane difficulty of the game was heavily criticized, but people also praised the overall production value.

So this time, with precious experience attained this past year, I’m joining a Jam part of the competition as a coder with two partners that both kick ass in their own departments consisting of pixel art and music composition. This is the first time we’re teaming up so we certainly don’t hope of taking the community by storm, but we’ll humbly do what we can to make something nice.

We want to wish good luck to all the competitors, there is no doubt in our minds this jam will see some amazing submissions!

Matthew K

Ignis – score aftermath

Posted by
Tuesday, September 16th, 2014 8:25 am

Ignis score:

#140 91% Graphics 3.88
#179 90% Theme 3.76
#363 76% Overall 3.40
#552 64% Innovation 3.16
#564 63% Mood 2.98
#578 62% Fun 3.02
#581 61% Humor 2.28
#674 65% Audio 2.48

-The good-

Graphics:
I knew the graphics are gonna be my game’s strong point, around 30% of the time was spent on graphics, either coding or designing. People liked the intro screen and reflection effect a lot.

Theme:
It took me around 2 hours to brainstorm the idea of the reflected world platformer. In my mind it suited the nature of the theme really well, in the end I was sure I could make a game out of it. This was another part of my game I relied on the most.

Overall:
I polished as much as I could, maybe even went a bit overboard. I believe this score could’ve been higher if I had time to make a music track or two. People liked the concept very much.

Fun:
Considering how hard the game turned out to be I expected an even lower rating after getting some feedback. At first I wanted it to be hard since the time constraint wouldn’t let me make many fun levels, but in the end it made the game much less approachable. Apparently people quit far too early and didnt even give the game a closer look. At least 4 people who left a reply didn’t even bother to notice the main game mechanic being the reflection part of the level, thus leaving comments like “it’s buggy” or “Really love the reflection, but couldn’t get anywhere to experience what it does”. In the end I learned the best thing a game can have is approachability.

-The bad-

Innovation:
Obviously opting in for a platformer killed this score a bit. I still feel the reflection part of the game is fairly neat, however I think it could’ve been pulled off much better if I had the time to do so. I believe I tried to do too much for a 48 hour competition.

Mood and Humor:
I wasn’t doing much to immerse a player in the game. Ignis has nothing to offer when it comes to storywriting, it feels like an arcade game with non-developed character.

Audio:
The game only has around 5-6 sounds and no BGM. I was introduced to the tools people use to make music for jams like this only after the submission period. I expected this, and now I learned what to do in the future.

Too challenging?

Posted by
Monday, August 25th, 2014 7:51 pm

Apparently the (.zip) file of my submission Ignis was a build where the game levels were running around 20% faster due to a typo. I made it faster for debugging reasons and later due to rush forgot to comment that line out. This is definitely the reason why most of the feedback received was about how difficult the game is, which was a big downer for me. The .zip link has been updated.

Thank you based pixel gods!

This is my first LudumDare and I had a blast developing. The feedback this community provides is above every expectation.

Entry page.

Ignis Release!

Posted by
Sunday, August 24th, 2014 5:59 pm

screenie

3 minutes before the clock. Still has things I’d change a bit, but I’ll update this game in the future nevertheless.
http://www.ludumdare.com/compo/ludum-dare-30/?action=preview&uid=39646

Hope you guys had fun, I certainly did. This was my first LudumDare and I’m
sure we can redo thisin 4 months time!

Ignis Update

Posted by
Sunday, August 24th, 2014 10:29 am

Almost there!

Ended up calling the game Ignis. Here’s the main menu thing, just few more things and it’s finished.

Still no name Update

Posted by
Saturday, August 23rd, 2014 7:45 pm

 

More eyecandy and gameplay. The game is already hard.

I can’t figure out a good name, it’s preventing me from making main menu.

Feature-creeped

Posted by
Saturday, August 23rd, 2014 2:42 pm
Day 1 nearing its end :D

Day 1 nearing its end!

I’ll most likely code-lock it in 4-5 hours. Do you guys find it hard to stop polishing?

Mirror Update

Posted by
Saturday, August 23rd, 2014 7:54 am

Recorded a gif animation before going to sleep. More hype after that! 😀

Tired of coding shaders.

Update

Posted by
Saturday, August 23rd, 2014 6:59 am

It took me around 2 hours to brainstorm this up.
2D Platformer where the world behind the usual perspective helps you reach the goal. Think of it as Earth turning into one giant magical mirror! :)

screen2 screen1 screen3

Okay, I guess I’m in.

Posted by
Friday, August 22nd, 2014 6:33 pm

I was a bit reluctant at first, but I guess I’ll join. I wanted to join the Jam at first, but Monday just won’t work for me and I didn’t want to slow anyone down with my absence.

Tools of the trade:
Coding: C++, C#, GML
IDE/Engine: Custom, Unity, GM:S (Depending on the theme)
Other: Photoshop CS4, GraphicsGale, Bfxr, Skelly (My own 2d animation software, PM if you’re interested in using)

Lots of coffee prepared, no energy drinks tho :)

[cache: storing page]