Forge Android App: 11-13-2016 Alpha 1.5.58.002

[Traldar]

Thank you very much, Dan!

This release is wonderful!

Just a small suggestion, since Commander and Tiny Leaders decks are so different, it seems on the Desktop Forge the Tiny Leaders decks are stored in a different folder, instead of decks/commander they are in dekcs/tiny_leaders. Looks like the folder is even created when you install Forge Android. Do you think it's easy to change that so tiny_leaders is the default folder?

Cheers,
traldar

[drdev]

Thank you very much, Dan!

This release is wonderful!

Just a small suggestion, since Commander and Tiny Leaders decks are so different, it seems on the Desktop Forge the Tiny Leaders decks are stored in a different folder, instead of decks/commander they are in dekcs/tiny_leaders. Looks like the folder is even created when you install Forge Android. Do you think it's easy to change that so tiny_leaders is the default folder?

Cheers,
traldar

I actually thought it made more sense to store both in the commander folder since Tiny Leaders are just a subset of Commander decks. I can add a conversion to transfer any decks from the tiny_leaders folder to the commander folder and delete the old folder so they work. Is that ok or do you need them to be in separate folders?

[drdev]

For those who may not remember, last holiday season I was hoping to get Planar Conquest released, but a redesign set me back, and a busy year since then has kept me from getting back to it. That said, I think it's about time to take another crack at it, and I've had lots of times to rethink the design and start up the implementation over the Thanksgiving holiday. I'm still very early in the implementation, but here's a teaser screenshot of the redesigned planar map to get things started.

Once I have a bit more done, I'll post some additional screenshots as well as an explanation of the game mode for this new design. I'm hoping it will be an exciting addition to Forge when it's finally done.

Thanks to those who've waited so patiently. Here's hoping you won't have to wait too much longer.
-Dan

[jureidinim]

For those who may not remember, last holiday season I was hoping to get Planar Conquest released, but a redesign set me back, and a busy year since then has kept me from getting back to it. That said, I think it's about time to take another crack at it, and I've had lots of times to rethink the design and start up the implementation over the Thanksgiving holiday. I'm still very early in the implementation, but here's a teaser screenshot of the redesigned planar map to get things started.

Once I have a bit more done, I'll post some additional screenshots as well as an explanation of the game mode for this new design. I'm hoping it will be an exciting addition to Forge when it's finally done.

Thanks to those who've waited so patiently. Here's hoping you won't have to wait too much longer.
-Dan

Looks great! I'll take it now.... lol
Happy to see you pick it up again to develop and definitely looking forward to it.

[Agetian]

Thanks for not giving up on this, Dan! Personally I think it'll be a great addition to Forge when it's ready!

- Agetian

[lefty]

Description: Went to unlock "Starter 1999" set in Quest Mode. Boom, crash. Also happened trying to unlock Starter 2000, but forgot to snag the crash report.

NullPointerException | Open

Code: Select all

Forge Version:    1.5.48.006
Operating System: Linux 3.10.61-5358024 aarch64
Java Version:     0 The Android Project

java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String forge.item.SealedProduct$Template.getEdition()' on a null object reference
   at forge.card.BoosterGenerator.getBoosterPack(BoosterGenerator.java:69)
   at forge.card.UnOpenedProduct.get(UnOpenedProduct.java:61)
   at forge.quest.QuestUtilUnlockSets.doUnlock(QuestUtilUnlockSets.java:200)
   at forge.quest.QuestUtil.chooseAndUnlockEdition(QuestUtil.java:506)
   at forge.screens.quest.QuestMenu$8$1.run(QuestMenu.java:90)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
   at java.lang.Thread.run(Thread.java:818)


[drdev]

I just released 1.5.48.007 which contains a couple card fixes and a fix for a bug where the Load Quest screen would crash if you pressed Start too fast.

[1mrlee]

Drdev

Great work on the app. Love it.

Any chance on how I can fix the skipped files that I need to download for card artwork?

It's still saying skipping 1400 files ish. Ask the new set I'm artless .

I play this app so often. I just cracked 500 wins... Lol

[sorinmarkov]

I just released 1.5.48.007 which contains a couple card fixes and a fix for a bug where the Load Quest screen would crash if you pressed Start too fast.

Big thank you for this. Been a lurker for a while. Just wanted to let you know that all your efforts are greatly appreciated! I am constantly amazed at how great Forge is thanks to you (and everyone who contributes)!

S.M.

[drdev]

Ready for another Planar Conquest teaser? Here's a look at the screens you'll be using to create new Planar Conquests.

Rather than have a single screen with a bunch of combo boxes like for Quest mode, I wanted to give these screens a little more character, which required creating a multi-step wizard flow. Note that for the plane select screen, the art shown in the monitor will change on an interval, going through a little slideshow of all art that appears on plane cards associated with that plane. I'm also planning to add a way to view the card pool for each plane since it may not be immediately obvious in all cases what cards are associated with each plane.

I'll provide more information about the structure of this mode soon, but for now you'll have to speculate based on these screenshots.

Stay tuned.
-Dan

[drdev]

I've spent today working on the collection and deck editor screens for Planar Conquest, and I'm excited to share a couple more screenshots along with some important information they reveal.

The first screenshot reveals an important difference between Planar Conquest and Quest mode. Instead of being able to build any number of constructed decks as in Quest mode, you'll only be able to build one deck for every commander you unlock, but each commander/deck will have his or her individual record tracked. This is why you choose a starting commander when creating a new Planar Conquest. As per the Commander format, you'll only be able to include cards from that commander's color identity in the deck.

That said, I should note that this doesn't mean every game is going to be a Commander game. As promised, Planar Conquest will feature various game types including Constructed, Commander, Planechase, Archenemy, Vanguard, Draft, and Sealed. While the commander structure of the decks isn't relevant to the limited formats (since you'll be creating a new deck for those), it will also not get in the way of playing non-Commander games, since your Commander will simply sit on the sideline for those games (since he can't be part of his own deck). On a related note, commanders can be included in the decks of other commanders in addition to being able to have their own deck.

I will also mention that unlike Quest mode where you start with a generated sealed pool and need to build a deck before you can get started, in Planar Conquest you will start with a generated deck based on your starting commander and plane. This way, you can jump right into playing and simply upgrade the deck as you unlock more cards. Though one upgrade you can make right away if you desire is to add your chosen Planeswalker to your deck (assuming it falls within the commander's color identity). In other words, your chosen Planeswalker starts out as an unlocked card in addition to being your avatar for the map screen.

The second screenshot reveals a couple more important pieces of information. The first is that one of the goals of Planar Conquest is to collect all the cards from each plane, hence why the Collection screen shows cards you haven't unlocked faded out. This allows you to quickly search for both cards you have unlocked as well as those you're looking for.

The second is that Planar Conquest is a Singleton format (which would probably be more obvious if I posted a screenshot of the list view that has no numbers in front of the card names). This means you don't need to collect 4 of each card, just 1. It is also inline with the focus on Commanders, which is primarily a Singleton format as well. That said, Planar Conquest will not require 100 card decks like traditional Commander, which can take a long time to build. Rather, the minimum will be 40 cards, which does not include the Commander. Although that's the same limit as Quest mode has, I think you'll find 40 card singleton decks play quite differently than 40 card fine-tuned Quest mode decks.

Obviously there are still additional details of Planar Conquest I have yet to reveal, such as the structure of the events associated with each square of the map, traveling between planes, and the reward structure for wins. Some of that I'm still working out, so feel free to chime in if you have ideas I could incorporate.

Lastly, please let me know if you have questions or concerns about the details I have revealed so far. It's not too late to make some tweaks if people have objections or other ideas. Just keep in mind that one of my primary goals is to provide a different experience than Quest mode currently offers.

Thanks.
-Dan

[Agetian]

This is shaping up to be a really interesting and unique game mode, I like your ideas, Dan! Keep it up!

- Agetian

[Krunk42]

I have a feature request for Forge on Android. I play a lot of constructed deck games, and I would like to (possibly automatically) save the state of the game when I am in the middle of a match. I can't always complete my match because I get interrupted, and when Android shuts down the App (which happens frequently because of memory use) then my game is lost. Would this be difficult to code? I see save games are possible for other modes, but I haven't been playing them so I don't know if they are saves from the middle of a match, or for progress between matches.

Either way, thanks for an awesome program.

[drdev]

I have a feature request for Forge on Android. I play a lot of constructed deck games, and I would like to (possibly automatically) save the state of the game when I am in the middle of a match. I can't always complete my match because I get interrupted, and when Android shuts down the App (which happens frequently because of memory use) then my game is lost. Would this be difficult to code? I see save games are possible for other modes, but I haven't been playing them so I don't know if they are saves from the middle of a match, or for progress between matches.

Either way, thanks for an awesome program.

Hopefully once we get online play figured out, the ability to save and reload a game state reliably will be doable. As it stands, that is a tall order however.

[RedDevil13]

I have no idea where to post this, but here goes:

I play this on a Kindle Fire (also have it loaded on my Samsung Note 4). It has worked well on both devices. I recently broke my Fire and bought a new one. The new Fire is a Kindle Fire HD 8 (5th Gen). In the process of me installing the Forge apk on the new tablet, you also released the 1.5.48.007 version. The app is completely unplayable on the new tablet. I have no idea whether it is your new release or the different operating system on the newer Fire, but it crashes constantly during constructed gameplay, most often on the first turn of the game, occasionally I am able to complete a game but it is very rare, always this is accompanied by a crash report. Additionally, when trying to create a deck in the deck manager, while scrolling through the search results and adding cards to the deck it will just randomly turn off the app, and return to my Fire homescreen, no crash report or warning of any kind. None of these problems have happened yet on my Note 4, so I must assume your new release is ok and it is the operating system of the Fire.

As far as I can tell, the Android operating system on the device is an Amazon proprietary software as follows "Fire OS 5.1.1 build date 12/2/2015"

This is by no means a complaint, technically your software is written for Android, not Amazon's bastardized version of Android, so I understand it not working properly. I am just letting you guys know about the problem and trying to give any other information you may need if you wish to correct it. I can try to upload or copy/paste one of the crash reports if you wish, just let me know how and where.

Also, is there any way that I can install a Beta, or "Official" version of this app without it upgrading to the latest Alpha? Maybe an official version would be more stable on my tablet?