Ok so I was extremely confused while playing this, then I read the comment you made and a lot of stuff cleared up, like the web towers only working if they had another one connected; I thought they just weren't working or something.
I kept getting cards to upgrade the chain towers while I only had cannons and weren't sure if they were the same or different ones before I got the web tower and then realised there were more towers in the game and I just had a bunch of actually useless cards in the deck just taking space.
Also the fact that the cannon uses projectiles instead of hitscan was extremely annoying at times when I thought I couldn't possibly lose and they completely missed all their bullets, I probably should have positioned the cannons better but some maps you just have to rely on rng entirely.
I did have fun in the end either way even though I didn't understand what was happening a lot of the time, the visuals look nice, audio is great, I especially like the game over screen; really cool looking!
I think it would've been good with some sort of tutorial to explain how the game works.
I do think you should keep working on the game since it has great potential and I would like a more polished version.
Play game
Server Knights's itch.io pageResults
Criteria | Rank | Score* | Raw Score |
Audio | #14 | 2.648 | 3.375 |
Visuals | #14 | 2.942 | 3.750 |
Theme | #16 | 2.746 | 3.500 |
Overall | #18 | 2.435 | 3.104 |
Innovation | #19 | 2.059 | 2.625 |
Replayability | #19 | 2.255 | 2.875 |
Fun | #19 | 1.961 | 2.500 |
Ranked from 8 ratings. Score is adjusted from raw score by the median number of ratings per game in the jam.
Comments
I was very confused the first few minutes I started playing this game, from things such as wondering why the long range tower I built didn't seem to do anything, to why I could complete the first 3 levels without building a single thing, or why enemies sometimes seemed to just vanish.
Even as I figured things out, more things kept eluding me. Many of the problems stem from a lack of feedback from the game.
Like, the AoE towers (presumably) hurt the enemies, but there was no visual indication other than the enemy suddenly disappearing after the tower made a beep. I had no clue why I couldn't play any cards after a bit, or what the blue chip with a number meant. Again, I did figure it out in the end, but I don't like that it had to take me that long to do so.
I wasn't even sure where I could place the towers at first. It took a wave to understand what was a path and what wasn't.
The idea was good, but it was the lack of visual feedback that killed it for me.
Lastly, and this is a question for tower defence games in general. Why a wave timer?
Thanks for the feedback! The artists did make a death effect, I just didn't have time to put it in. They made quite a few fx that didn't get time to be put in. Explaining the mechanics was also something that just didn't have time. I usually do shorter jams, 12 hours - 2 days, this was the 1st 2 week jam I did, and thought I could tackle more than I was able to. I pulled 2 all nighters at the end just to get it even playable with the mechanics we intended. Such is the nature of overscoping.
One thing I think wasn't explained well enough at all was the resource system. We call those "Threads" you start with 4 of them. While they are gold, they are available for the player to use. Each card has a Thread Cost in the top left that says how many Threads they'll use. When a Thread is spent, it turns gray until the next wave, where it becomes available again. Some cards have 2 numbers in the top left, the 2nd number being how many turns a Thread is used for. When such a card is played, the Threads it used turn blue, and designate how many waves left they have in such a state. Blue Threads are busy working and can not be used to play cards until they are gold again. There are 2 different types of Thread Reservation, one performs the action every turn (a buff card for instance will provide it's buff for every turn the thread is blue), others perform their action when the Thread completes its job, turning gold again (Overclock is an example of this). Some card animations and icons would go a long way in explaining a lot of this.
I think there are some balancing issues early game, you can get RNG'd out of being able to do much (your example of long range tower not attacking is one of these, as is only having 1 web tower in your opening hand, as a web tower requires another web tower to create a web.) Unfortunately I didn't have enough time to play test this to even notice that until post-jam, and would be something I fix if I put more work into the project. As for the long range towers, their radius really needed to be a ring, not a circle, every little thing takes time.
I think the lack of displaying the deck, discard, and trash piles also creates some confusion. Your starting deck is 5 cards large, and it's pseudo-randomized at the start of the run. When you defeat a level and add a new card, it adds it to your deck as an option to play. When you draw your cards each wave you draw from the deck, not the complete list of cards. Meaning if you get unlucky with card picks and have very few tower cards in your deck, the game can get very hard. I would make the cards you have a choice from a bit smarter if I work on it more, favoring to usually put a tower card there, maybe tapering off to equal chance in the later game as you start to need less of them.
Its unfortunate, but I don't think anyone will even see the boss we worked on. We built the game completely level-less to test specific things really easy and fast, so it wasn't in until the last few hours, they really needed to be done earlier.
As for your question about timers, it keeps the game moving, it forces the player to make a choice and play. Tower defense games can really drag on, especially in longer waves and later levels. I'd remove it for this game completely going forward because I feel like it clashes with the card game aspect of this game because it ends up removing your cards while you're in the middle of trying to play them.
Leave a comment
Log in with itch.io to leave a comment.