Skip to content

GameStateConverter: Add some extra information about cards #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

cdaymand
Copy link

All these new information are needed to create a card description for slaythecli

All these new information are needed to create a card description for slaythecli
Copy link
Owner

@ForgottenArbiter ForgottenArbiter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the pull request! I agree that these are some good things to have. Originally, the description, damage, block, and magic number were left out because it was possible to determine them from the rest of the game state, and I wanted to keep the state representation small. However, in the interest of not adding too much extra information to the game state (especially considering a large portion is often taken up by card objects, and it all needs to be transmitted over stdout), could we reduce the number of new fields? I was thinking:

  • baseHeal, baseDraw, and baseDiscard are not used by the game, so they could be removed, along with heal, draw, and discard
  • I don't believe base_magic_number and magic_number are both necessary, since I'm pretty sure they are always equal. I'll leave this one up to you, though.
  • While you're at it, do you want to add ethereal? I've had that requested before, and for some reason I added exhaust, so ethereal is definitely in the same vein.

I do see why users might want both base_block and block though (same with damage). Also let me know if you think my concerns are completely unfounded.

@cdaymand
Copy link
Author

At first when I did these changes, I was not completely sure about the information needed, now I am a bit more confident about the game source code and I agree for baseDraw and baseDiscard (not needed)
For the card feed, I will check if baseHeal is used or not.
Someone contacts on reddit about ethereal and yes it might be interesting to add.
Yes base_block and base_damage is needed when displaying deck or card reward because then damage and block is at value -1.
I will modify my pull request.

In fact at the moment, after reading a post on reddit (regarding accessibility) I changed a bit my mind and I am completely doing the server part in java which handles all the game logic and send back a nice output.
This way the installation will be easier for people (just a mod) and the game will be playable by any tcp client, telnet, socat, nc , ...
I think I might have something soon to share.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants