Skip to content
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

Adding new json cards, nor deleting cards changes cards existing in simulator client #388

Open
MattCutler opened this issue Mar 11, 2019 · 1 comment

Comments

@MattCutler
Copy link

MattCutler commented Mar 11, 2019

I've built an ontology modelling different types of cards in Hearthstone for my UG project. In Java, I'm then parsing the ontology individuals into POJOs, then serialising them into JSON identical to the format of the equivalent cards currently in Metastone.
When I assemble and run the game after either changing existing cards - Stonetusk Boar from BEAST to DRAGON etc., removing, or adding new ones, the same exact set of already existing cards load into the simulator and deckbuilder without any changes made to the set of card json files.
I've noticed development as stopped, however I would greatly appreciate if I could email or chat with someone who may help solve this? Perhaps forking from an older commit? It seems as if the cards are being loaded from a predetermined existing .jar I cannot find.

@MattCutler MattCutler changed the title Adding new json cards, nor deleting cards changes cards in simulator Adding new json cards, nor deleting cards changes cards existing in simulator Mar 11, 2019
@MattCutler MattCutler changed the title Adding new json cards, nor deleting cards changes cards existing in simulator Adding new json cards, nor deleting cards changes cards existing in simulator client Mar 11, 2019
@webadict
Copy link
Collaborator

Where are you modifying the cards?

If I'm getting this right, you are compiling the source, which won't update the cards unless you update the card versioning (which is, itself, a problem that needs fixing eventually) or you force them. Alternatively, you can set your Metastone dorectory to the source directory, but that has to be done carefully.

Also, I'm slowly working on getting some updates, but I've been here and there, and everyone that used this before has moved to other branches, so there's been no real push to get them done.

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

No branches or pull requests

2 participants