Forge version 1.2.4

[friarsol]

Quest opponents aren't refreshing after you finish a match until you goto a different screen and come back.

[Chris H.]

We also got a report that the avatar that we choose are assigned to the other player.

[Max mtg]

I confirm. I've seen both problems.

[Chris H.]

I moved the precon messages to the shapshot bug board, should not be too hard for you all to find. I am glad that things worked out.

[Doublestrike]

OK guys sorry for radio silence over the last few days but I've been working madly on the constructed submenu rebuild.

I've been screaming along but it won't be ready by Monday, but it will be ready Tuesday or Wednesday.

I wanted to keep it a surprise but the cat's out of the bag now - it's the final incarnation of the home screen, pretty much everything that should be happening there.

So, I can fix the bugs mentioned above in the current version if we want to release immediately, or I can have them addressed in the cutting edge stuff if we can afford the few days delay.

All of the recent codebase optimizations have finally come to a head in this design - full singleton pattern, room for expansion, improved optimization on 800x600 res, and fixes a few display problems discussed in the past (including the constructed one), with better performance and a few more functionalities - e.g. deck editor returned to main menu.

Here's a screen shot. I'll be able to commit very soon, it's about 90-95% finished, and should be reasonably stable since there's no features that haven't been tested before.

[friarsol]

OK guys sorry for radio silence over the last few days but I've been working madly on the constructed submenu rebuild.

I've been screaming along but it won't be ready by Monday, but it will be ready Tuesday or Wednesday.

I wanted to keep it a surprise but the cat's out of the bag now - it's the final incarnation of the home screen, pretty much everything that should be happening there.

So, I can fix the bugs mentioned above in the current version if we want to release immediately, or I can have them addressed in the cutting edge stuff if we can afford the few days delay.

All of the recent codebase optimizations have finally come to a head in this design - full singleton pattern, room for expansion, improved optimization on 800x600 res, and fixes a few display problems discussed in the past (including the constructed one), with better performance and a few more functionalities - e.g. deck editor returned to main menu.

Here's a screen shot. I'll be able to commit very soon, it's about 90-95% finished, and should be reasonably stable since there's no features that haven't been tested before.

I think it'd be smarter to get the issues patched above, and get a release out then have the commit come in with the new fun stuff. We've had a few recent releases that something big went in just before. I'd rather we get back to a real stable release. This way your big code change can have lots of eyes (and a few weeks) to work out all the kinks.

[Chris H.]

I would like to vote for Friday March 3rd or Monday March 5th.

This will allow Doublestrike the time that he needs to finish his work. Max might want a few more days of play testing to finish off his contribution.

While we are at the decision making stage, do we want to call the upcoming beta version 1.2.4 or 1.3?


Oh, and a big thank you to the wonderful work recently done by Max and Doublestrike. We all appreciate your contributions.

[Max mtg]

ATM my part is working (i fixed the bug mentioned yesterday). I suspect only boosters generated in draft mode to repeat. When it's checked, my work is over.

I have no idea how you assign minor versions. 1.2 should have been assigned when deckeditor was 1000 times accelerated by lightweight cards, so I just lost any idea of what is sufficient to increase minor version.

DoubleStrike is making something different than we originally suggested

[friarsol]

While we are at the decision making stage, do we want to call the upcoming beta version 1.2.4 or 1.3?

I think 1.2.4 should be fine, if you really want to skip something we can go up to 1.2.5. I think we should try branching for the next version. Basically once things are relatively fit, we branch and no new features go into that branch. If there are any bugs that exist in that version, they can be fixed in that branch. Once everyone thinks things are stable enough to move on it's released, but we aren't held up for people who want to push their new toys out the door. After release, the branch is locked (or maybe deleted, depending on how we want to handle it) and focus shifts to the next release. Thanks to Roujin for suggesting it earlier in the thread. Since we are on a much quicker release schedule than other projects, it's probably not as big a deal for us, but hopefully this will improve the consistency of our releases.

[Sloth]

So, I can fix the bugs mentioned above in the current version if we want to release immediately, or I can have them addressed in the cutting edge stuff if we can afford the few days delay.

I think it'd be smarter to get the issues patched above, and get a release out then have the commit come in with the new fun stuff. We've had a few recent releases that something big went in just before. I'd rather we get back to a real stable release. This way your big code change can have lots of eyes (and a few weeks) to work out all the kinks.

I vote for releasing a beta asap and testing new stuff afterwards.

Here's a screen shot. I'll be able to commit very soon, it's about 90-95% finished, and should be reasonably stable since there's no features that haven't been tested before.

How do i play with a random deck against the computer using a quest deck in this design?

[Doublestrike]

I vote for releasing a beta asap and testing new stuff afterwards.

That gives us a majority. Fixes will be coming down the pipes soon, although it sounds like the constructed-tab issue will be a source of problems for this release.

How do i play with a random deck against the computer using a quest deck in this design?

Just select "Quest Event Decks" (under "Constructed Modes", and you'll see the quest event decks, then whack on the "random" button.

[moomarc]

Quite often I test new card scripts (custom constructed) against theme decks because they make it easier to test some situations, but with this layout it looks like I'd have to make a constructed deck for the AI as well for each of these scenarios. Am I right?

Edit: And I think Sloth had a scenario in mind similar to mine. I understood it as he want to play with a random deck from "Random Color Deck" against a "Quest Event Deck", not a random quest deck vs quest deck.

[Doublestrike]

Ahh, I see. Thanks for the explanation, Max's mockup makes a lot more sense now. I'll look again with that in mind.

[Doublestrike]

Bugs should be fixed:

- Avatar index bug (moomarc)
- Quest opponent refresh (friarsol)
- Avatar switch bug (Chris H., bug thread)
- Win streak (stats) not refreshing (bug thread)

[Chris H.]

It looks like we should release the next beta on Friday March 3rd. DoubleStrike can add in his new UI work on the following weekend.

We will make the next beta version 1.2.4. I was wondering if the change in how our decks files are stored in the decks folder (the subdirectories) might be a good place for a minor version number update.