madebynoxc / amusement-club Goto Github PK

When you run ->list and then accept a direct card sale, the bot post for list gets deleted. The same happens with ->diff and ->auc

HI,

would be nice that the cards command return the list of the cards, and each card contains a link to the image of the card.
In order to use less the summon command, because now the claim (N) command is useless, because you have to run the summon command N times to view all the summoned cards.

Best Regards,
Nyryus

This may have been mentioned somewhere already, but I decided to inform you of this anyway.

Currently, a daily claim gives 300 Tomatoes.
A quest either rewards 400, 500 or 650 tomatoes by default. (minimum reward is 800)
Chinatsu boosts quest rewards by 80%, making her minimum quest reward 720x3 (as she receives an extra quest as well), so 2160.
Yui's effect gives +100 daily tomatoes for every card previously claimed.
Akari's effect makes claim cost 65% of original price.

Claim costs are 50 times number of cards previously claimed + 1.
So you get a table like this.

When I commented on the debt, I mean when at minimum quest reward, people would claim more than they can affort (when their tomato stock is empty) Yui scores second highest because of her +100 per card. The difference between Yui and Chinatsu's debt is also interesting.
Trying to claim the 10th card, chinatsu would be 290 tomatoes short. Trying to claim the 9th card, Yui would be 250 tomatoes short.

I understand Kyoko's cost is lower because of her two other effects, making her a more strategic auctioner hero, but considering Akari only has the effect of reducing claim cost, it's strange that she is only one card better off than Kyoko. Yui also has the second effect of making all effect cards have half their cooldown.

So, to conclude: With Yui, not only can you reliably claim a large amount of cards with her while still holding on a nice stockpile of tomatoes for later bidding on the auction, the reduced time for an effect card's activation makes her pretty much overpowered compared to the others. It effectively makes her the best choice for hero and to such point that there seems to be little reason to pick another one. Perhaps chinatsu to more quickly stockpile tomatoes, but Akari is practically useless this way and Kyoko is more for those who are already rich.

I was wondering if you could rebalance things a bit. At least between Yui and Akari. You could consider to decrease the card cost for akari even further so she has better benefits or add a second hero effect for her. It would result in more players pick her and I mean not just for the looks.

I recently bid over 8k on a card called chuuni 02 from darling in the franxx, and when I try to summon it, it doesn’t work and it tells me “Can’t find card matching that request” and I even copied it from the card title itself. Is there any way to fix this?

The description says "Get 20% more 🍅 when you sell a card" but only affects when selling to the bot and not to another user. I would suggest changing the wording to specifically say selling to the bot. Wasted 50k tomatoes getting the cards for this.

I already mentioned this on the discord. Basically what happens is that when a hero is changed, the hero name and image are replaced, but the subname is not. The result is that you get strange combinations like: Dark Priestress Akaza Akari or Anti-Bully Ranger Yoshikawa Chinatsu,

I suspect this happens because of what the function "switchHero" does in
amusement-club/modules/heroes.js
It actively sets the new hero's name into the database replacing the older one, but this does not happen with the subname from what I can tell. Because of this, I think the database grabs the subname it was assigned to when the user obtained their hero for the first time. I figured at least that upon loading "getHero", the database, instead of heroes.json, is searched for the entries of hero.name and hero.subname.

To be fair, I do not have any programming knowledge. I used my head while trying to read and to understand a bit of the code and I made my conclusion here based on what I get from the entries you wrote there. Therefore I could be entirely mistaken as to how this works, but in any case I do hope it is helpful.
Actually, if I get it right, all you need to do is make a small change to the var entry there, adding something that updates the hero subname as well, like "hero.subname" : newHero.subname, or so I figured.