TOPIC: Token Validator Release!!

Just tested mine (through the plastic case) on my Pixel 2--works great.

Thank you for making an Android version!

My tokens validated inside of my Dansco book. Thanks for releasing the Android version.

Cranston wrote:

Wayne Rhodes wrote: Tested out on a iPhone 8
Sometimes takes several tries to validate.

Does not work on dragon orbs (not that it said it would but tested anyway).

You do need to get the token in a very specific location on the front of the phone close to the top for it to scan.

I had tried putting my CoA into a poker chip key chain to keep it tied off but it will not vacillate on the app in the key chain, but will with the plastic it comes in. I’m not sure if the keychain will work with TDs scanning equipment or not. I’ll bring a key chain to test that with to the con.

I have better luck scanning the token on the back side of the phone. Close to the top, but on the back. Generally, I find on the back of the phone, I can get some distance, but I am running iPhone Xs.

EDIT: I can confirm that my iPhone Xs reads the Charms of Avarice, while the charms are within the plastic case. There should be no need to remove them from the container, in order to validate them.

Dragon Orbs utilize a different type of RFID tag, that cannot be read by phones.

That seems weird, why would they use a different one?

James J Krot wrote:

Cranston wrote:

Wayne Rhodes wrote: Tested out on a iPhone 8
Sometimes takes several tries to validate.

Does not work on dragon orbs (not that it said it would but tested anyway).

You do need to get the token in a very specific location on the front of the phone close to the top for it to scan.

I had tried putting my CoA into a poker chip key chain to keep it tied off but it will not vacillate on the app in the key chain, but will with the plastic it comes in. I’m not sure if the keychain will work with TDs scanning equipment or not. I’ll bring a key chain to test that with to the con.

I have better luck scanning the token on the back side of the phone. Close to the top, but on the back. Generally, I find on the back of the phone, I can get some distance, but I am running iPhone Xs.

EDIT: I can confirm that my iPhone Xs reads the Charms of Avarice, while the charms are within the plastic case. There should be no need to remove them from the container, in order to validate them.

Dragon Orbs utilize a different type of RFID tag, that cannot be read by phones.

That seems weird, why would they use a different one?

I will preface by saying that I am not in the "know" about the Dragon Orb RFID, but my belief is that they are UHF vs HF (sorry old school terminology. Now HF is referred to as NDEF, or NFC) Anyway, the range on UHF is MUCH larger, but the amount of data that can be transferred is MUCH less. So, if you want a specific token to be recognized just walking through a doorway (or into room 7?), you need UHF. The readers in phones are built specifically for NFC tags, and cannot read UHF.

In short it depends on what you want to do with the tag. For Charm of Avarice, preventing copying or fakes is the primary reason, so NFC would make more sense. For detecting the presence of a token entering the dungeon at distance, UHF is the ticket.

Again, I don't know anything about the tags in the Orbs, but that's a guess.

That seems weird, why would they use a different one?

The technology in the Dragon Orbs can only be validated by TD HQ.

For the CoA there was a strong request from token traders that they be allowed to validate the tokens themselves. To enable that we needed to move to a technology usable by phones.

In other words, the CoA stuff is newer tech.
If it's liked, I imagine it might be used for future tokens as well.

Mike wrote:

That seems weird, why would they use a different one?

The technology in the Dragon Orbs can only be validated by TD HQ.

For the CoA there was a strong request from token traders that they be allowed to validate the tokens themselves. To enable that we needed to move to a technology usable by phones.

In other words, the CoA stuff is newer tech.
If it's liked, I imagine it might be used for future tokens as well.

Time to re-do the Dragon Orbs... Trent needs copies of each variation.

Version 2.1 of the Token Validator for IOS has been released. It includes support for IOS 13 and support for Dark Mode.

Enjoy!

I have some news for IOS users of the Token Validator. IOS 13.2 breaks the app. I have a correction in the works, but it will be several days (hopefully by next Friday) to get released. I still have some testing and need to submit to Apple before release. The new version will be 2.2.

The update will change how you need to operate the app. You still start by tapping the Read Tag button, but need to do move the token between reads. (they used to happen one right after the other) Now you will need to tap the button, move the token to the reader, at the top of the iPhone until it beeps, move it away and bring it back a second time. The text on the screen guides you through it.

IOS 13.2 allows background tag reading, so I need to make changes to make sure the Token Validator is the only app collecting the data.

I will post again when the release goes live.

Sorry for the inconvenience.

Token Validator for IOS version 2.2 is available for download.

This version corrects issues related to IOS 13.2 or later. You will need to adjust how you read the Charm of Avarice token. Tap the button as normal. Bring the token up to the reader at the back of the top of the iPhone. You will hear a beep. Move the token away, and bring it back in to the reader. You will hear a second beep, and the data will be validated.

I apologize for the change, but Apple introduced significant changes to the NFC Reader libraries in IOS 13, and especially in IOS 13.2.

Thanks!

Version 3.0 of the Token Validator has been released for IOS and Android. The primary reason for the release is preparation for potential tokens beyond CoA.

Cranston wrote: Version 3.0 of the Token Validator has been released for IOS and Android. The primary reason for the release is preparation for potential tokens beyond CoA.

Time to start scanning every token that I receive...

Fiddy wrote:

Cranston wrote: Version 3.0 of the Token Validator has been released for IOS and Android. The primary reason for the release is preparation for potential tokens beyond CoA.

Time to start scanning every token that I receive...

well, the orbs for sure....