Post by MetaMetaPuzzle in Feedback

Viewing post in Feedback

MetaMetaPuzzle158 days ago (3 edits) (+1)

Some observations/suggestions:

Maybe swap the effects of 47 and 53? In the endgame, being able to play 47 twice is very powerful, and a deck built out of 47 and 13 will easily beat the final boss.
The fhccerffrq ahyyfgbar says "Immune", but doesn't really seem to have that effect.
Since the effect of 7 doesn't stack, 49 has an additional special effect. However, 11*11 and 13*13 don't seem to have any additional effects.
7 is immune to 37-infect, but not 47-discard or 89-steal.
If fhccerffrq ahyyfgbar is stolen by 89 or copied by M-stone, it becomes unplayable again.
194 (2*97) doesn't have a similar effect to 34.
94 incorrectly states the order of its actions.
This is a great game :)

Edit: I also found a bug: If you win (or tie) a match and then press "Concede", it counts as both a win *and* a loss? I tied and pressed Concede and in my stats it said I had abandoned -1 games

Edit #2: I used 13 and X-stone on the final boss to obtain 323-stone, placed it on the board.. and apparently it doesn't work (17*19).

Playcebo156 days ago

Thanks! I did a small update addressing most of these issues:

Swapping 47 and 53 is a neat idea (47 might be a fun boss!), but for now I just tweaked the final boss instead. (He now has two 87 (sticky+cycle) and always starts with a 67.)
Not immune: Oops! Fixed. (It was immune on-board, but not when played.)
I doubled the effects of 11*11 and 13*13, and improved 194. Thanks for the suggestion! (I didn't make 11*11 and 13*13 very strong.)
Immune to 47/89: Ah, that's a tricky one. For now, I've kept it as-is. (My logic for excluding them was that 47 and 89 only affect the card, while 37 affects the 7-stone itself (in a sense). Plus, I'm unsure how to make immunity to 47/89 feel right. I might change it so that attempting to steal or discard a 7-stone simply turns it face-up and plays a sound effect.)
89 unplayed / M unsuppressed: Hopefully fixed... I have total spaghetti code here, because two different stones share the same number.
94: Discarding will now occur before burn, because automatic actions should always go first.
Concede bug: Fixed.

Omshinwa156 days ago

omgg you made stones higher than 100? daang gotta play that again sometimes

Playcebo156 days ago

FYI, there is not much support for stones 101 - 200. They all have the same sprite, and they're hard to use since you're still capped at 100 Energy. They are unlocked by completing the mining levels M1 - M10. (Composites only. Primes above 100 don't have any effect.)

Completing M10 does give an additional reward, which you might want to use for some of the Ribbon challenges in the tournament (if you haven't done those already).

Omshinwa156 days ago(+1)

alright, yea i dont think you need stones above 100 lol, your game was already really well tightly designed ( i still love how you used the concepts of primes and composites for mixing up powers together lol )

MetaMetaPuzzle153 days ago(+1)

89 unplayed / M unsuppressed: Hopefully fixed... I have total spaghetti code here, because two different stones share the same number.

It's totally broken please help it's not unplayable at all with X

Playcebo153 days ago

Thanks! It's fixed now (apart from a visual bug with M-stone).

Deleted post152 days ago

Deleted 152 days ago

MetaMetaPuzzle151 days ago(+1)

I think doubling the effect of 13*13 broke regular 13. It's starting to steal more energy than the opponent has...

Playcebo151 days ago

Sorry about that! Fixed now. Turns out it was an order-of-operations issue!

if(  stoneNumber % DRAIN_FACTOR * DRAIN_FACTOR == 0   )
      { drainMultiplier = 2 }

MetaMetaPuzzle150 days ago(+1)

I don't see how this is related to these bugfixes, but enemies burning multiple tiles will burn only one.

Playcebo150 days ago

Thanks so much for all the bug-finding! Fixed.

(nerdy details: When improving 194, I added code to abort the tile-burning process early upon failure [i.e. tilesBurned == 0], but it turns out I never coded the AI to increment tilesBurned as it burns tiles. So it burned 1 tile and then said "welp, I burned 0 tiles, so I guess I'll give up now".)

itch.io

Viewing post in Feedback