Nonbasic land (and other mana-producers) updates
Posted: 17 Jan 2017, 14:02MM = Manual tapping for mana
We have been improving nonbasic land functionality (thanks to code from Xander9009).
As of the next CW update, most dual lands will function a little differently. This only impacts lands that do NOT have MM in the filename.
If the player is AI, the auto-tapped color will randomly change frequently, so that the AI has a better chance of being able to use the mana. (Previously, the AI couldn't use it at all or could only use one of the two colors offered by the land.)
If the player is human, the player can click on the ability and do several things:
-- Set it to auto tap for the first color (can be changed by the player at any time)
-- Set it to auto tap for the second color (can be changed by the player at any time)
-- Produce the first color
-- Produce the second color
-- Turn off auto-tapping
The above gives the player more options. Perhaps you don't want it to auto-tap because you want to make sure that the land's other abilities are more available. Or perhaps you are playing a card that triggers when a land is tapped for mana, so you want to turn off auto-tapping (because those abilities don't trigger with auto-tapping).
If you plan to share your decks in the CW or play against AI, I highly recommend switching the lands in your deck to the non-MM versions. By non-MM, I mean that in the deckbuilder, the card's filename does NOT contain MM in it. Eventually some or all of the MM versions will be removed from the CW, so it is a good idea to switch your lands any way.
Tri-lands and any color lands are still in development. However, all Tri- and any color lands do have non-MM versions that offer the AI at least one color of mana to work with. These versions will be updated with the new code as it is developed, so again, I recommend choosing the cards with filenames that do not include MM.
The list below contains the 47 lands that do not currently have a non-MM version. For these, you will need to continue using MM versions (for the time being).
The rest of this thread will document the states of various lands for future development.
- With the exception of the above list of non-MM lands, all dual lands that have a only one mana ability (to produce one of two colors) have been updated to include the new code.
- Lands that have multiple mana abilities, have had their first ability updated. Typically, this is an auto-tap for
and the second ability remains MM. Often with these lands, there is an additional cost or restriction to the second/third abilities, so auto-tap code would need to be more involved. For example, Sulfurous Springs does damage to the player when tapped for its second ability. We can't just make that auto-tap without additional code. And, we may choose not to make them auto-tap for that second ability. It's TBD.
- All single color producing lands have had their non-MM version either checked, updated, or created so that all should now function via auto-tap.
- Tainted Isle contains code that appears to provide some auto-tap functionality when 2 mana abilities are present. Perhaps it can be used as a starting point to develop code for other multi-mana ability lands.
- I didn't update Nimbus Maze as the code appears to be an early attempt at making auto-tap (or something) happen. In any case, it offers multiple mana abilities, so I would have only updated the first one.
- The following spreadsheet contains a list of all lands that I believe will require some additional coding. With the exception of those in the list above (no non-MM versions), these lands have been improved with some auto-tap functionality, but as you will see in the spreadsheet, there are secondary abilities that could benefit from some additional code. For example, the any color ones that are listed do have the previous auto-tap code in place, but they will need updated once the new code for any color auto-tap is available.
https://docs.google.com/spreadsheets/d/ ... sp=sharing
I will update this thread as things develop.
Please feel free to share feedback, bugs, etc.
We have been improving nonbasic land functionality (thanks to code from Xander9009).
As of the next CW update, most dual lands will function a little differently. This only impacts lands that do NOT have MM in the filename.
If the player is AI, the auto-tapped color will randomly change frequently, so that the AI has a better chance of being able to use the mana. (Previously, the AI couldn't use it at all or could only use one of the two colors offered by the land.)
If the player is human, the player can click on the ability and do several things:
-- Set it to auto tap for the first color (can be changed by the player at any time)
-- Set it to auto tap for the second color (can be changed by the player at any time)
-- Produce the first color
-- Produce the second color
-- Turn off auto-tapping
The above gives the player more options. Perhaps you don't want it to auto-tap because you want to make sure that the land's other abilities are more available. Or perhaps you are playing a card that triggers when a land is tapped for mana, so you want to turn off auto-tapping (because those abilities don't trigger with auto-tapping).
If you plan to share your decks in the CW or play against AI, I highly recommend switching the lands in your deck to the non-MM versions. By non-MM, I mean that in the deckbuilder, the card's filename does NOT contain MM in it. Eventually some or all of the MM versions will be removed from the CW, so it is a good idea to switch your lands any way.
Tri-lands and any color lands are still in development. However, all Tri- and any color lands do have non-MM versions that offer the AI at least one color of mana to work with. These versions will be updated with the new code as it is developed, so again, I recommend choosing the cards with filenames that do not include MM.
The list below contains the 47 lands that do not currently have a non-MM version. For these, you will need to continue using MM versions (for the time being).
- Lands that only have MM versions | Open
The rest of this thread will document the states of various lands for future development.
- With the exception of the above list of non-MM lands, all dual lands that have a only one mana ability (to produce one of two colors) have been updated to include the new code.
- Lands that have multiple mana abilities, have had their first ability updated. Typically, this is an auto-tap for
and the second ability remains MM. Often with these lands, there is an additional cost or restriction to the second/third abilities, so auto-tap code would need to be more involved. For example, Sulfurous Springs does damage to the player when tapped for its second ability. We can't just make that auto-tap without additional code. And, we may choose not to make them auto-tap for that second ability. It's TBD.- All single color producing lands have had their non-MM version either checked, updated, or created so that all should now function via auto-tap.
- Tainted Isle contains code that appears to provide some auto-tap functionality when 2 mana abilities are present. Perhaps it can be used as a starting point to develop code for other multi-mana ability lands.
- I didn't update Nimbus Maze as the code appears to be an early attempt at making auto-tap (or something) happen. In any case, it offers multiple mana abilities, so I would have only updated the first one.
- The following spreadsheet contains a list of all lands that I believe will require some additional coding. With the exception of those in the list above (no non-MM versions), these lands have been improved with some auto-tap functionality, but as you will see in the spreadsheet, there are secondary abilities that could benefit from some additional code. For example, the any color ones that are listed do have the previous auto-tap code in place, but they will need updated once the new code for any color auto-tap is available.
https://docs.google.com/spreadsheets/d/ ... sp=sharing
I will update this thread as things develop.
Please feel free to share feedback, bugs, etc.
where it should have had 
.
because the extra 
cost, add an availability block which calls a modified version of the above function. This modified version would check if the card being granted the ability is either a land or is in the list. If it is, then return true only if the cost plus the current production can be paid. Otherwise, return true (the normal mana cost block will take care of it).