a question for the modders

[j6m6w6]

it seems some users that installed the mods i converted for ipad are having issues with the decks being locked. the weird thing is im not having this problem, all decks are unlocked and working fine for me. im using the same files i uploaded for all to use also. the only thing i changed from the original mods were the images which i converted to the ipad format, and the content pack number, ipad requires that be set to 0. and always avaliable is set to true. any input would be helpful as i would like all to be able to use these great mods with no trouble.

thanks, j6

Edit: it seems a user reinstalled the magic 2014 app and the mods are working for him now.

[RiiakShiNal]

This is probably related to the value set for the ios_id_1 attribute. In another post you said you unlocked the built-in decks using deck keys. If you check the deck XMLs from the mods they probably each use one from the list as most modders either copy deck XMLs and modify them or they generate them using my Deck Builder (which uses D14_DECK_UNLOCK_1 because an unlocked by default id is currently unknown).

• "D14_DECK_UNLOCK_1" - Garruk
• "D14_DECK_UNLOCK_2" - Humans
• "D14_DECK_UNLOCK_3" - Jace
• "D14_DECK_UNLOCK_4" - Jund
• "D14_DECK_UNLOCK_5" - Liliana
• "D14_DECK_UNLOCK_6" - Ramp
• "D14_DECK_UNLOCK_7" - Slivers
• "D14_DECK_UNLOCK_8" - Ajani
• "D14_DECK_UNLOCK_9" - Chandra
• "D14_DECK_UNLOCK_10" - Dimir

People who are having problems with the decks being locked on iPad probably do not have these IDs associated with their accounts and thus the decks for them are locked.

As for the always_available="true" attribute that only takes effect if it is the first time the deck with that id has been loaded. If the deck was loaded before the always_available attribute was set to true then the profile will need to be deleted before there is even a chance that this attribute will kick in.

If someone can figure out an ID that works to make decks available by default on iPad then they should post it so that we can update the best practices page with that information and I can update the Deck Builder to use that by default.

Edit: The reason the user was probably able to get it working after a reinstall is because the profile was deleted and the always_available="true" attribute was able to take effect.