Forge Beta: 02-07-2014 ver 1.5.12
Moderators: timmermac, Blacksmith, KrazyTheFox, Agetian, friarsol, CCGHQ Admins
Re: Forge Beta: 02-07-2014 ver 1.5.12
by drdev » 20 Feb 2014, 16:11
What about mana dorks (like Llanowar Elves)? I feel like a preference will resolve this concern by having different options about what mana sources to include. The default would be, as you said, to include lands and artifacts that have no ability besides being a mana source. We could then offer options to allow auto-tapping creatures with only mana abilities, lands with non-mana abilities, artifacts with non-mana abilities, etc. I agree one-shot mana effects should probably never be included.
How does that sound?
How does that sound?
- drdev
- Programmer
- Posts: 1958
- Joined: 27 Jul 2013, 02:07
- Has thanked: 189 times
- Been thanked: 565 times
Re: Forge Beta: 02-07-2014 ver 1.5.12
by friarsol » 20 Feb 2014, 16:31
Personally I would say creatures shouldn't be auto-tapped at all. And certainly they'd be very low priority for anyone who wants to auto-tap them. There are plenty of scenarios where creatures are needed, and plenty of odd scenarios where accidentally tapping them costs you a match, cards like Gemhide Sliver causing creatures to tap that you don't expect, etc. If auto could be re-checked in between each mana payment that would probably be the best way to handle a hybrid. "Ok I sac my Lotus for Green, now I auto tap the rest of my lands"
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: Forge Beta: 02-07-2014 ver 1.5.12
by drdev » 20 Feb 2014, 16:48
I suppose for simplicity, at least for now, we can avoid adding a preference. We'll just change it to skip mana sources that aren't lands/artifacts without non-mana abilities, and then make it so the Auto button enabled state is updated anytime you manually activate a mana ability.friarsol wrote:Personally I would say creatures shouldn't be auto-tapped at all. And certainly they'd be very low priority for anyone who wants to auto-tap them. There are plenty of scenarios where creatures are needed, and plenty of odd scenarios where accidentally tapping them costs you a match, cards like Gemhide Sliver causing creatures to tap that you don't expect, etc. If auto could be re-checked in between each mana payment that would probably be the best way to handle a hybrid. "Ok I sac my Lotus for Green, now I auto tap the rest of my lands"
Max, is this something you can do, or would you like my help?
After that, how hard would it be to update the logic that determines which mana sources to tap if we have more than we need and multiple colors available? Ideally we should try to leave mana open that optimizes the number of known spells/abilities that we could cast/activate later that turn, though a simpler implementation would be to just try to leave the same number of sources for each color open.
- drdev
- Programmer
- Posts: 1958
- Joined: 27 Jul 2013, 02:07
- Has thanked: 189 times
- Been thanked: 565 times
Re: Forge Beta: 02-07-2014 ver 1.5.12
by SIXTY » 20 Feb 2014, 18:39
Tell me plz, wtf?
Why i can't download pictures? Who have all pictures, plz send a zip file to me, or upload to dropbox or another similar service. Sorry for my bad english. Big thx guys for your work, You the best ;D
Why i can't download pictures? Who have all pictures, plz send a zip file to me, or upload to dropbox or another similar service. Sorry for my bad english. Big thx guys for your work, You the best ;D
- Attachments
-
Sorry for my bad English 
-
SIXTY - Posts: 33
- Joined: 20 Dec 2010, 19:43
- Location: Krasnodar
- Has thanked: 9 times
- Been thanked: 0 time
Re: Forge Beta: 02-07-2014 ver 1.5.12
by Grim Rowe » 20 Feb 2014, 20:56
Got a weird case,
I attacked with a Black Cat and a Typhoid Rats. AI casts Dazzling Beauty, targeting my Reassembling Skeleton, which actually was in my graveyard. I copy the log :
Match result: Sinister Grim: 0 Crystal: 2
Game outcome: Crystal has won because all opponents have lost
Game outcome: Sinister Grim has conceded
Damage: Black Cat (23) deals 1 combat damage to Crystal.
Damage: Typhoid Rats (17) deals 1 combat damage to Crystal.
Phase: Sinister Grim's Combat Damage
Phase: Sinister Grim's First Strike Damage
Resolve stack: Dazzling Beauty ability fizzles.
Add to stack: Crystal cast Dazzling Beauty (109) targeting [Reassembling Skeleton (26)].
Mana: Swamp (82) -
: Add 
to your mana pool.
Mana: Plains (95) -: Add 
to your mana pool.
Mana: Plains (94) -: Add to your mana pool.
Combat: Crystal didn't block Typhoid Rats (17).
Crystal didn't block Black Cat (23).
Phase: Sinister Grim's Declare Blockers
Combat: Sinister Grim assigned Black Cat (23) and Typhoid Rats (17) to attack Crystal.
I attacked with a Black Cat and a Typhoid Rats. AI casts Dazzling Beauty, targeting my Reassembling Skeleton, which actually was in my graveyard. I copy the log :
Match result: Sinister Grim: 0 Crystal: 2
Game outcome: Crystal has won because all opponents have lost
Game outcome: Sinister Grim has conceded
Damage: Black Cat (23) deals 1 combat damage to Crystal.
Damage: Typhoid Rats (17) deals 1 combat damage to Crystal.
Phase: Sinister Grim's Combat Damage
Phase: Sinister Grim's First Strike Damage
Resolve stack: Dazzling Beauty ability fizzles.
Add to stack: Crystal cast Dazzling Beauty (109) targeting [Reassembling Skeleton (26)].
Mana: Swamp (82) -
: Add to your mana pool.Mana: Plains (95) -
: Add to your mana pool.Mana: Plains (94) -
: Add to your mana pool.Combat: Crystal didn't block Typhoid Rats (17).
Crystal didn't block Black Cat (23).
Phase: Sinister Grim's Declare Blockers
Combat: Sinister Grim assigned Black Cat (23) and Typhoid Rats (17) to attack Crystal.
Re: Forge Beta: 02-07-2014 ver 1.5.12
by Luxis » 20 Feb 2014, 21:34
Ho! I'm sorry. : |drdev wrote:Can you be more specific and provide a stack trace please?Luxis wrote:Hoooouh, hell, guys! Fix the crash that happens when you alternate between a game tab and other tabs!cmon..
I thought it was a very common error.
It was just create a game, passed a few turns, conceded, created a new game, click on any other tab, then back to the game tab, crash.
Good luck.
- IllegalArgumentException | Open
Re: Forge Beta: 02-07-2014 ver 1.5.12
by Fizanko » 20 Feb 2014, 23:54
Got an error message on the AI turn, it just setup its attackers (those annoying cards with horsemanship)and there was this error popping up :
Description: [describe what you were doing when the crash occurred]
Description: [describe what you were doing when the crash occurred]
- ConcurrentModificationException | Open
probably outdated by now so you should avoid : Innistrad world for Forge (updated 17/11/2014)
Duel Decks for Forge - Forge custom decks (updated 25/10/2014)
Duel Decks for Forge - Forge custom decks (updated 25/10/2014)
Re: Forge Beta: 02-07-2014 ver 1.5.12
by Bundy » 21 Feb 2014, 14:54
Description: Don't know why i got this error report. Computer casts Nekrataal and destroys one of my creatures (Llanowar Elves with some +1/+1 counters on it). Then attackers are declared, Nether Traitor and Ohran Viper. Before the declare blockers step this error pops up. The game continues like normal.
- ConcurrentModificationException | Open
- Bundy
- Posts: 348
- Joined: 17 Dec 2010, 17:32
- Location: The netherlands
- Has thanked: 23 times
- Been thanked: 3 times
Who is online
Users browsing this forum: No registered users and 17 guests