Collectible Card Game Headquarters

Are serialized forge.Deck instances (the old deck format) still in active use, or can we assume that they have all been converted to the new text-based format?

I am trying to move quest deck metadata (deck name, description, difficulty, etc.) into the .dck files so that code changes are no longer necessary to add quest opponents. This task is going to be much more painful if serialization compatibility is still necessary.

Fnoed wrote:Are serialized forge.Deck instances (the old deck format) still in active use, or can we assume that they have all been converted to the new text-based format?

I am trying to move quest deck metadata (deck name, description, difficulty, etc.) into the .dck files so that code changes are no longer necessary to add quest opponents. This task is going to be much more painful if serialization compatibility is still necessary.

No decks appear in the game that are not in text form. If decks are loaded they are not used. So yes, please move the quest deck metadata, Fnod!

I think that this is a good idea. We will not miss editing the buildDeckList() method.

Will this bring back the ability to import decks into quest mode?

What do you mean by import? Copying AI decks into the quest deck folder?

Fnoed wrote:What do you mean by import? Copying AI decks into the quest deck folder?

`
We used to be able to import a serialized .deck file into our questData file. This would add the cards from the imported deck into our existing card pool. It would also add the pre-constructed deck itself and allow us to play a quest with the pre-constructed deck.

It is something of a cheat but it can also be a lot of fun for some people.

Ah. My changes will not affect that potion of the code.

Perhaps we should support it officially, instead of importing using a hack? Perhaps allow the user to optionally import a single deck on new quest start?

Fnoed wrote:Ah. My changes will not affect that potion of the code.

Perhaps we should support it officially, instead of importing using a hack? Perhaps allow the user to optionally import a single deck on new quest start?

As long as any deck can be imported it will always be cheating. But there's no reason not to allow it if it's not too much work. We can just make clear that this is not intended to be the way quest mode is to be played.

Sloth wrote:As long as any deck can be imported it will always be cheating. But there's no reason not to allow it if it's not too much work. We can just make clear that this is not intended to be the way quest mode is to be played.

Probably the best way to handle it is to open a Quest Mode option where you choose your starting deck (instead of having one generated for you) and play through that way.