Forge Android App: 11-13-2016 Alpha 1.5.58.002

[friarsol]

When activating Lion's Eye Diamond with a Phrexian mana spell such as Gitaxian Probe on the stack, Forge doesn't prompt for which color mana you wish to create. It defaults to the color used for the spell on the stack.

Ahh I've been trying to track down a repro for this forever. It looks like this might be a good hint.

[lefty]

When Forge downloads card images, there are usually some left over that it skips as unavailable. Is there anyway to get a list of the skipped cards generated within the app, so that we could manually add them if we have the image files from elsewhere?

I currently am missing 17 card images, but I dont know which ones, and I really dont want to scroll through 25000 card lines in the library to try to see which ones dont have images.

[Agetian]

UPDATE (06/29/16): I uploaded a new version of the mobile version of Forge for Android. This version matches the just-released new beta version of Forge (v1.5.53) and contains all the improvements and fixes present in that version of the game. According to the numbering scheme employed in mobile Forge, the new version is considered to be 1.5.54.001 Alpha.

By the way, on that note, do we have any particular criteria for when mobile Forge can be considered "beta" quality instead of "alpha" quality? I believe that today its "alpha" status is a bit of a misnomer, I have used it on four different Android devices and it was at least as stable as the desktop version, and is very much playable, too (could be somewhat slow on older/slower devices, yeah, but on all modern devices it runs fast and is very responsive). It matches the features of desktop Forge almost one-to-one, it lacks Quest Draft Tournaments but instead it has a great Planar Conquest mode which even the desktop version doesn't (yet) have. To my mind being "alpha" is typically associated with common crashing and/or a significant lack of features, most of which are in the early stages of development, and I can't really say either about the current mobile Forge, so I'm a bit confused... :/

- Agetian

[jtrowell]

in theory alpha status is supposed to be for when you have nto yet implemented all the planned core features, while beta is for when you have all the core features (but might still be missing some content)

For Forge mobile version, the fact that some of the destop features where missing might have justified the alpha status, provided that they were considered to be core features.

As we now only miss the tournament, and also have an alternative game type with the planar conquest, i think that it's indeed probably time to stop calling it an alpha version.

Even the beta status might be seen as obsolete, the game already has almost all the existing features and content of the game, and new released are more like DLC or expension packs when a new set is added, with the inevitable bugfixes that go with any new release, at this point it's more like a living project, we're not in beta anymore from my point of view.

[friarsol]

By the way, on that note, do we have any particular criteria for when mobile Forge can be considered "beta" quality instead of "alpha" quality?

I think Dan was using the Alpha moniker to denote that even though the product might have some of the right "fit and finish" it still being released in between Beta builds, so it's possible it gets built in the middle of a serious issue that hasn't been caught and fixed yet.

[Agetian]

Ah, that would make sense. Possibly we should then start calling the builds that match up with the Beta releases "Beta" as well, while calling the in-between snapshot releases "Snapshot" or something?.. I'm not sure, tbh.

- Agetian

[drdev]

I mostly have kept the Alpha tag to avoid confusion with the desktop Beta and since there are features like Quest tournament that haven't made their way over. That said, I'm not opposed to changing it to Beta or dropping the tag altogether.

[timmermac]

Lots of skipped images for what seems to be something other than not existing on the server. Log file attached. Please advise.

[Aquillion]

Something seems to be wrong in Quest Mode's Tarkir Shard, regarding the Sultai Brood. There is a stray quote mark at the end of Tarkir - Sultai Brood", and all their decks are listed as "Random X" with a different number after X.

[drdev]

Something seems to be wrong in Quest Mode's Tarkir Shard, regarding the Sultai Brood. There is a stray quote mark at the end of Tarkir - Sultai Brood", and all their decks are listed as "Random X" with a different number after X.

Turned out to be a simple typo in the regions.txt file for Tarkir. This will be fixed in the next Android release.

[drdev]

Lots of skipped images for what seems to be something other than not existing on the server. Log file attached. Please advise.

Looks like your phone isn't allowing Forge to create the folder "/storage/external_SD/card pics/EMA". Is your external hard drive writable? Does manually creating that folder fix this issue for you?

[dostick]

Hi.
I'm trying to play Forge with a Xiaomi Remi Note 3 Pro but it freezes always when on duel screen I push "Play" or "Draw". Also app froze when navigating menú to change folders. I paste the error log generated by the app.

NullPointerException | Open

Code: Select all

Forge Version:    1.5.54.001
Operating System: Linux 3.10.73-perf-gc7d7acd aarch64
Java Version:     0 The Android Project

java.lang.NullPointerException: Attempt to get length of null array
   at forge.toolbox.FList.setListData(FList.java:80)
   at forge.toolbox.FFileChooser.setFileListForDir(FFileChooser.java:171)
   at forge.toolbox.FFileChooser.activateSelectedFile(FFileChooser.java:194)
   at forge.toolbox.FFileChooser.access$300(FFileChooser.java:24)
   at forge.toolbox.FFileChooser$FileList$1.tap(FFileChooser.java:360)
   at forge.toolbox.FFileChooser$FileList$1.tap(FFileChooser.java:341)
   at forge.toolbox.FList.tap(FList.java:159)
   at forge.Forge$MainInputProcessor.tap(Forge.java:590)
   at forge.toolbox.FGestureAdapter.touchUp(FGestureAdapter.java:196)
   at forge.toolbox.FGestureAdapter.touchUp(FGestureAdapter.java:158)
   at com.badlogic.gdx.backends.android.AndroidInput.processEvents(AndroidInput.java:360)
   at com.badlogic.gdx.backends.android.AndroidGraphics.onDrawFrame(AndroidGraphics.java:420)
   at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1522)
   at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1239)


[drdev]

So I know I've been somewhat MIA for the last couple months, but I want to assure everyone that I am most certainly still around. And for my next trick, in light of recent suggestions of dropping the "Alpha" tag from the Android app, I thought it was about time I got around to implementing the last major feature missing from the app: Quest Tournaments!

It's not quite ready yet, but here's a screenshot to hold you over until then.

Thanks.
-Dan

[5enza]

Very excited and looking forward to this feature!

[Pande]

I installed on an Nexus 5x Android 6.0.1 (Marshmallow). Turned on the "Install from unknown sources" settings. Updated to version 1.5.54.001. And then when I start it, it just freezes when looking for new updates at the splash screen.

What am I doing wrong? I was very excited to try this out.

Edit. For what is worth I found the forge.log. I don't think it helps...