Forge Android App: 11-13-2016 Alpha 1.5.58.002

[friarsol]

The second bug: the keyboard automatically types a spacebar after each word, so when searching for a creature type (cavern of souls), it adds a spacebar after the word which I have to delete before it finds the creature.

These definitely sound like keyboard issues. Also, I'd call adding a space after a word not a bug, since it's not necessarily undesired behavior for the general audience. I have several apps that for some reason don't do this, and it's extremely annoying to use them to type things.

[drdev]

The second bug: the keyboard automatically types a spacebar after each word, so when searching for a creature type (cavern of souls), it adds a spacebar after the word which I have to delete before it finds the creature.

These definitely sound like keyboard issues. Also, I'd call adding a space after a word not a bug, since it's not necessarily undesired behavior for the general audience. I have several apps that for some reason don't do this, and it's extremely annoying to use them to type things.

I could at least work around this by trimming spaces from the end of all searches so that an extra space at the end won't screw up the results. Otherwise, there's not much I can do as I can only process the keyboard input I'm receiving.

[drdev]

Description: [In the quest deck editor, in the inventory tab with pile view sorted in color association the black was collapsed. I clicked the arrow to expand it and this bug report happened]

NullPointerException | Open

Code: Select all

Forge Version:    1.5.24.006
Operating System: Linux 3.4.5-1083225 armv7l
Java Version:     0 The Android Project

java.lang.NullPointerException
   at forge.itemmanager.views.ImageView$ItemInfo.draw(ImageView.java:943)
   at forge.itemmanager.views.ImageView$Pile.draw(ImageView.java:903)
   at forge.itemmanager.views.ImageView$Group.draw(ImageView.java:832)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.toolbox.FScrollPane.draw(FScrollPane.java:308)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.Forge.render(Forge.java:223)
   at com.badlogic.gdx.backends.android.AndroidGraphics.onDrawFrame(AndroidGraphics.java:414)
   at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1524)
   at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1248)


I can't reproduce this. If you can still reproduce, could you provide me with more specific steps and/or a before screenshot?

[drdev]

Bug/Exploit

In the quest deck editor, I added a card to my sideboard - clicked on it, then clicked on add - then clicked on the 3, and I had 3 more of the same card - which I could then move to the main deck.

I just released 1.5.24.007 which fixes this exploit along with a couple other things:

• Fix crash that could occur if you tried to edit a quest deck after previously editing a deck outside that quest.
• Text fields will now automatically trim spaces from both ends of the input text after accepting it, so searching won't require clearing spaces from the end for you anymore.
• Fix crash that could occur when applying filters on an image view before card images finished loading incrementally.

[kestell]

Description: [In the quest deck editor, in the inventory tab with pile view sorted in color association the black was collapsed. I clicked the arrow to expand it and this bug report happened]

NullPointerException | Open

Code: Select all

Forge Version:    1.5.24.006
Operating System: Linux 3.4.5-1083225 armv7l
Java Version:     0 The Android Project

java.lang.NullPointerException
   at forge.itemmanager.views.ImageView$ItemInfo.draw(ImageView.java:943)
   at forge.itemmanager.views.ImageView$Pile.draw(ImageView.java:903)
   at forge.itemmanager.views.ImageView$Group.draw(ImageView.java:832)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.toolbox.FScrollPane.draw(FScrollPane.java:308)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.Forge.render(Forge.java:223)
   at com.badlogic.gdx.backends.android.AndroidGraphics.onDrawFrame(AndroidGraphics.java:414)
   at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1524)
   at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1248)


I can't reproduce this. If you can still reproduce, could you provide me with more specific steps and/or a before screenshot?

No, I can't seem to reproduce it either.

[kestell]

After generating commander decks, and setting a card as the commander, when I want to start, a window pops up that says:

Invalid commander deck Kestell's deck is missing a commander.

When I edit the deck, in the commander tab, the commander is empty. Then I go on catalogue, "set as Commander" on the creature - it pops up wonderfully, I save but it doesn't see it.

I'm guessing it never saves the commander. I edited the text files of the decks and there is no entry under commander - I added it manually - and it started up

[drdev]

Description: [In the quest deck editor, in the inventory tab with pile view sorted in color association the black was collapsed. I clicked the arrow to expand it and this bug report happened]

NullPointerException | Open

Code: Select all

Forge Version:    1.5.24.006
Operating System: Linux 3.4.5-1083225 armv7l
Java Version:     0 The Android Project

java.lang.NullPointerException
   at forge.itemmanager.views.ImageView$ItemInfo.draw(ImageView.java:943)
   at forge.itemmanager.views.ImageView$Pile.draw(ImageView.java:903)
   at forge.itemmanager.views.ImageView$Group.draw(ImageView.java:832)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.toolbox.FScrollPane.draw(FScrollPane.java:308)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.Graphics.draw(Graphics.java:95)
   at forge.toolbox.FContainer.draw(FContainer.java:58)
   at forge.Forge.render(Forge.java:223)
   at com.badlogic.gdx.backends.android.AndroidGraphics.onDrawFrame(AndroidGraphics.java:414)
   at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1524)
   at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1248)


After generating commander decks, and setting a card as the commander, when I want to start, a window pops up that says:

Invalid commander deck Kestell's deck is missing a commander.

When I edit the deck, in the commander tab, the commander is empty. Then I go on catalogue, "set as Commander" on the creature - it pops up wonderfully, I save but it doesn't see it.

I'm guessing it never saves the commander. I edited the text files of the decks and there is no entry under commander - I added it manually - and it started up

I just released 1.5.24.008, which fixes both of these bugs. Turns out the first bug was reproducible if you changed the filters while a group was collapsed, then later expanded it.

This release also adds the support you asked for to play multiple rounds for drafts. Rather than radio buttons, you'll simply be prompted to choose how many opponents you want to face when pressing the Start button. If you choose 1 (the default), you'll play against a randomly chosen deck among the 7 AI draft decks. If you choose to play multiple opponents, you'll face the AI draft decks in order.

Thanks for the feedback.
-Dan

[kestell]

I think that after choosing commander as a variant type, the default choice should not be Random generated decks - it should be custom user decks.

[kestell]

Also, in duel commander, the starting life total is 30.

[friarsol]

Also, in duel commander, the starting life total is 30.

Do you want to clarify? Firstly, that wouldn't be an Android specific problem and secondly according to http://mtgcommander.com/rules.php "Players begin the game with 40 life."

[drdev]

So I'm happy to share that I've started making a dent in adding one of the last major missing features: Gauntlets!!!

So far, I've added support for displaying this screen which lists existing gauntlets and allows you to play any of them from start to finish. It also allows renaming and deleting gauntlets.

All that's left to do is add support for creating new gauntlets, then I'll be able to release this new feature. Once that's done, all buttons on the home screen will finally be enabled, and the android port of Forge will have almost all features of the desktop game.

Stay tuned.

[drdev]

I just released 1.5.24.009, which includes full Gauntlet support and a home screen with no disabled buttons!!!

For creating new gauntlets, I decided to save some UI design and development by using a few list chooser dialogs to select which type of gauntlet to create (Quick, Custom, or Contest) and, based on your choice, additional information needed to create the gauntlet (such as opponent count and AI deck restrictions for quick gauntlets). For selecting decks for yourself or the AI, you'll see a separate deck chooser screen to pick that deck, which will remember the last deck you selected and show a useful title such as "Select Your Deck" or "Select Deck for Opponent 3 / 10".

Let me know if you have any questions or concerns about the new gauntlet support.

Thanks.
-Dan

[drdev]

I think that after choosing commander as a variant type, the default choice should not be Random generated decks - it should be custom user decks.

This should also be fixed by 1.5.24.009, FYI.

[Agetian]

Really good job on Gauntlets, Dan!
Btw, as a side note about the slowdown issue: I noticed one more case when the slowdown becomes super apparent - it's when counters are placed on the card. So, auras, equipments and counters thus far. I think this points somehow towards the fact that when something is drawn on top of something else, the game slows down considerably (though for some reason e.g. lands stacked on top of one another do not seem to cause the issue).

- Agetian

[squee1968]

Just to throw another monkey wrench into the machine, Melira, Sylvok Outcast also causes a slowdown regardless of other cards on the battlefield.