TOPIC: Phone/Pad Apps

The idea of providing a way to list tokens for the run, but not necessarily for the build is a good idea. David's spreadsheet provides a notes field. I will have to think about this for a while. Providing a notes field would take a slot, but at least it's only one. Nothing will change on this before Gencon, but I will see if I can figure out something for next year's version. I will have to look into ways to print from the app, or add the notes to the bottom of the email output.

In the short term, you could generate the email, and add extra text at the bottom of the email. That would give you the complete token list, and any notes including lamp tokens, etc. Just a thought.

That would be great! Since those tokens don't affect the party card, a free flow notes field would work great.

Thanks

The Android version is through processing and should be available:

Version 3.7 Updates
- Corrected Amulet of the Wind
- Corrected text for the Wind token set
- Corrected the 5th Level Monk Hit Points
- Corrected Tooth of Cavadar description text
- Lock out other treasure enhancing tokens when Charm of Avarice is equipped
- Corrected a problem with the database not being closed in some circumstances
- Corrected a potential problem in a routine with NULL values

The IOS version is in review and should be available later today.

The IOS version has been released.

What's New in Version 3.6

- Corrected Amulet of the Wind
- Wind token set text updated to include immunity to normal missiles
- Corrected hit points for Level 5 Monk
- Corrected spelling on Kvothe's Bloodless token
- Corrected description text for Tooth of Cavadar
- Corrected the background color for the Cold damage modifier for melee attacks
- When Charm of Avarice is equipped, all other treasure enhancement tokens are disabled
- Email and Clone functions are disabled until a character is selected

Just updated iOS... Looks great!

Thanks!

It appears, at least on the iOS version, you have to reselect Kothe's Bloodless, else it is black and you don't get it effect until you do reselect it.

Not a bug, just an FYI for others...

Myron K. Crandall wrote: It appears, at least on the iOS version, you have to reselect Kothe's Bloodless, else it is black and you don't get it effect until you do reselect it.

Not a bug, just an FYI for others...

Good point. Sorry, I was going to bring that up, but spaced it.

You do need to reselect Kvothe's Bloodless, since it is now spelled correctly.

Found a couple of bugs in the current iPad app, most dealing with runestones...

First, the Spirit Runestone says bypassed 50% miss chance against undead, but should read against incoporal not a big deal... But...

Second, the Runestone fitting bases say they allow only rare runestones to be used... But the app lets any, including commons and uncommons.

Third, it seems the app assumes one Runestone is on Melee weapon, and other is always on Range... I think... But you can put both on same weapon, be it Melee or Range, or separate,.. One on each... I may be wrong n how it works, but this is what seems to happen.

Btw, I absolutely love the app... And the other excel spreadsheet... I use them both.

Thanks for providing such a useful tool. And for such a small pittance of a price.

Have you ever thought about leaving the Amulet of Wonder effects in, and let you choose past years so I can play with builds? I know it would be a pain, but I like screwing around with what-if scenarios...

Just information on future revisions.

Apple has released IOS 10, which will require me to update Xcode to test on IOS 10 devices. When that happens, I will not be able to test on IOS 8.x devices. All of this means that future updates for the Character Generator will require IOS 9.0 or later. It's the lawww of the West. Actually it's Apple's Law. You will update. IOS 8.x devices will continue to run the existing app just fine, but the new token set will only be available to IOS 9 or later. No changes will happen until after Gamehole Con, so no hurry.

Obviously this will not affect Android users. Android users will just have to continue to wear fire retardant clothes. Interesting choice. Constant required updates, or go up in smoke....

Cranston wrote:
Obviously this will not affect Android users. Android users will just have to continue to wear fire retardant clothes. Interesting choice. Constant required updates, or go up in smoke....

To be clear it is Samsung, not Android users that need to worry about fires. Unless you know something about the OS that I haven't seen.

jedibcg wrote:

Cranston wrote:
Obviously this will not affect Android users. Android users will just have to continue to wear fire retardant clothes. Interesting choice. Constant required updates, or go up in smoke....

To be clear it is Samsung, not Android users that need to worry about fires. Unless you know something about the OS that I haven't seen.

The first thing you learn in writing software, is it's always about the code. The code is why it works and the code is why it fails. The battery fails so it must be a software bug. (but yes, it is just Samsung phones as far as I know)