Page 4 of 5

Re: Who is planning to do what?

PostPosted: 22 Sep 2011, 16:05
by Hellfish
jeffwadsworth wrote:
Hellfish wrote:Radiance should be good now. Those 7 extra cards pushed Ravnica over 70% :D
Rollin' rollin' rollin'...
Keep rollin! Dissension is now > 70% as well, making the entire Ravnica block > 70% :D

Re: Who is planning to do what?

PostPosted: 29 Sep 2011, 00:13
by Doublestrike
<announcement>
I'm working on combining the multiple rewards windows into a universal win/lose GUI, and at the same time making a common win/lose GUI that can be easily modified for various mode rewards.

I won't be making any commits to the core codebase for now, but if people could hold off on huge logic changes to the Gui_WinLose area for about a week, that would be nice.
</announcement>

Re: Who is planning to do what?

PostPosted: 11 Oct 2011, 00:03
by Doublestrike
<announcement>
I've started construction on the new in-game UI and it's going well. Every request made can be included.

At this point I'm predicting release in about 100 hours, which will take me about 6 weeks. So, if you don't hear about anything happening with the UI, don't worry, it's moving along.
</announcement>

Re: Who is planning to do what?

PostPosted: 11 Oct 2011, 14:17
by Rob Cashwalker
{2yo}6 weeks? :cry: But I want it nowwww.... :cry:{/2yo}

Re: Who is planning to do what?

PostPosted: 13 Oct 2011, 20:53
by Hellfish
Implementing Delve now. Tombstalker and Death Rattle are done. Logic Knot.... Knot so much (heyo! :mrgreen: ). That's the second time X-costs decide to stand in my way when implementing a new keyword. >_>

EDIT: Of course, just as I say this, Eclipse just up and shits itself. God damn it. (FAKE EDIT: Corrupted .project file due to... diffs? I wish I knew. I also wish I wasn't too lazy to set up IDEA again :P At least it's fixed now.)

Re: Who is planning to do what?

PostPosted: 13 Oct 2011, 20:57
by friarsol
Hellfish wrote:Implementing Delve now. Tombstalker and Death Rattle are done. Logic Knot.... Knot so much (heyo! :mrgreen: ). That's the second time X-costs decide to stand in my way when implementing a new keyword. >_>
Yea I feel like we need to redo Cost Change for better support in general. It should send a whole Object back stating how much "leftover" reduced mana there is so that can be applied to other Costs (X mana, or Kicker, or whatever)

Re: Who is planning to do what?

PostPosted: 17 Oct 2011, 05:31
by Doublestrike
Hellfish wrote:EDIT: Of course, just as I say this, Eclipse just up and (Word of Undoing) itself.
LOL I'm glad it's not just me. My relations with Eclipse and Subclipse are apparently directly and inversely proportional to the phase of the moon, the price of tea in China, and the seal population within the Arctic circle.

BTW your joke was knot half bad.

Re: Who is planning to do what?

PostPosted: 17 Oct 2011, 18:44
by Hellfish
Doublestrike wrote:
Hellfish wrote:EDIT: Of course, just as I say this, Eclipse just up and (Word of Undoing) itself.
LOL I'm glad it's not just me. My relations with Eclipse and Subclipse are apparently directly and inversely proportional to the phase of the moon, the price of tea in China, and the seal population within the Arctic circle.

BTW your joke was knot half bad.
I only switched back to Eclipse because of our brief stay on gitorious. Once I get some extra time I am soo moving back to IDEA. *shakes fist*

I just started working on generalizing StormCount into something a bit more detailed, similar to ThisTurnEntered. This will enable, among others, Ethersworn Canonist (With big thanks to Sloth for CantBeCast mode :D ) Storm Entity script-only,Vengevine script-only and possibly Twinning Glass.

EDIT:Ichneumon Druid will also be possible scriptonly.

Re: Who is planning to do what?

PostPosted: 17 Oct 2011, 23:20
by jeffwadsworth
Definitely some interesting cards there. Perhaps we can slip in some Abeyance. That is a sweet card.

Re: Who is planning to do what?

PostPosted: 18 Oct 2011, 06:13
by Hellfish
. Abeyance is definitely helped by Sloth's CantBeCast mode. I think the only other thing needed for it is for Effects to remember Players.

EDIT: BTW, ThisTurnCast is implemented now, for those Steamcore Weird of you who don't read the svn logs ;)

Re: Who is planning to do what?

PostPosted: 18 Oct 2011, 06:26
by Sloth
Hellfish wrote:EDIT: BTW, ThisTurnCast is implemented now, for those Steamcore Weird of you who don't read the svn logs ;)
Nice work Hellfish. I just thought yesterday "if only the spells cast this turn would be accessible in detail". Arcane Laboratory, Rule of Law, Mindbreak Trap are scriptable now I think. I will try to implement stuff like Talara's Battalion.

Re: Who is planning to do what?

PostPosted: 18 Oct 2011, 07:00
by Hellfish
I don't think we can exile spells specifically for Mindbreak Trap yet. The others I see no problem with. :)

Re: Who is planning to do what?

PostPosted: 04 Nov 2011, 22:56
by Hellfish
Tinkering with Convoke. Got a pretty good system going for the human, now to implement a decent AI strategy...

Re: Who is planning to do what?

PostPosted: 05 Nov 2011, 09:01
by moomarc
Hellfish wrote:Tinkering with Convoke. Got a pretty good system going for the human, now to implement a decent AI strategy...
Oooh! There's 2 more on my list of token creating cards scriptable. Thanks!

Re: Who is planning to do what?

PostPosted: 13 Nov 2011, 21:59
by Hellfish
New project: Costs. First up, I was thinking of rewriting the cost parsing in a way that doesn't choke on nested costs. This would in turn, enable an Or<{any cost}|{any cost}> construct for use with cards such as the reveal/discard-or-pay-extra cards (Flamekin Bladewhirl, Goldmeadow Stalwart, Lightning Axe, Silvergill Adept, Squeaking Pie Sneak and Wren's Run Vanquisher) and possibly even the and/or kicker cards (The Planeshift/Planar Chaos Battlemages and Apocalypse -volvers).

I've actually got it working for the reveal/discard-or-pay-extra cards, but it's pretty terrible. The parsing is changed from the greedy matching it currently is to a token-based system, and the Or-CostPart object has to register an override CostPart (itself) for which CostPart to set as paid for in the CostPayment object. (That's the terrible part, and it's worse than it sounds)