TOPIC: Charm of Avarice v3

Picture / link please? The thought of being out $1k because an RFID chip gets banged too hard is quite perturbing.

Just to correct a few misconceptions on the scanning results.

First, I was working in the Transmute room when Arcanist brought his token in. In checking the logs on the failure, the problem was original to the token, when it was exchanged. It did not get damaged or change during the convention. In looking at the logs for Thursday night/early Friday, I do not see that token show up, so it did not get the full scan over night. The first time it shows up in the log is when it failed.

That said, we are making changes to the logging app to prevent tokens like that from getting out in the first place. The number of these that got out is extremely small, but the code can be improved.

In truth, we did not have a single instance of a token going 'bad' during Gencon. The possibility exists that the tag could get damaged by sharp objects, so it is recommended that you keep them in the protective case, but simply dropping one or coming close to magnets in general, will not harm the tag.

Early at Gencon, the volunteers in Epilogue were new to the devices used for scanning. After some training on where the reader hardware was in the phones, the scanning process improved in speed and reliability. The biggest source of variability in scan results for most people has been the variability in reader hardware from one phone type to another. The tags have been extremely reliable. TD did a good job in selecting this tag.

Cranston wrote: Just to correct a few misconceptions on the scanning results.

First, I was working in the Transmute room when Arcanist brought his token in. In checking the logs on the failure, the problem was original to the token, when it was exchanged. It did not get damaged or change during the convention. In looking at the logs for Thursday night/early Friday, I do not see that token show up, so it did not get the full scan over night. The first time it shows up in the log is when it failed.

That said, we are making changes to the logging app to prevent tokens like that from getting out in the first place. The number of these that got out is extremely small, but the code can be improved.

In truth, we did not have a single instance of a token going 'bad' during Gencon. The possibility exists that the tag could get damaged by sharp objects, so it is recommended that you keep them in the protective case, but simply dropping one or coming close to magnets in general, will not harm the tag.

Early at Gencon, the volunteers in Epilogue were new to the devices used for scanning. After some training on where the reader hardware was in the phones, the scanning process improved in speed and reliability. The biggest source of variability in scan results for most people has been the variability in reader hardware from one phone type to another. The tags have been extremely reliable. TD did a good job in selecting this tag.

Not sure where your logs are stored but I SPECIFICALLY watched all 4 Charms be scanned at the end of my 11:36PM run (Thursday night/Friday morning) and all 4 came back as valid.

I am not one to cry wolf, I was incredibly concerned by the scanning issue, doubly so by the fact that the token HAD scanned properly only 9 hours earlier and had not left it's storage case in between the two scans.

I am INCREDIBLY concerned by the implied threat that a validly obtained Charm of Avarice which has an issue with it's RFID chip will not be honored and I could potentially lose $1300 in value over an RFID chip that has been shown to not always work properly in my presence.

Is this RFID validating software available for concerned true dungeon players to download for verification of our charms outside of conventions such as after purchasing a charm from a fellow TD player?

Will there be an officially supported recourse for true dungeon players to follow if one of these new Charms comes up showing invalid as one of mine did at GenCon?

I do not want to sound like the sky is falling here but the issue I encountered at GenCon and the comments about RFID failures meaning I am out of luck leave me concerned.

That is a very big concern. RFIDs do not last forever.

I’m completely baffled by the freak out going on in this thread.

What, in terms of explicitly stated policy or the history of your customer service interactions with td is making you think that if your legitimate CoA isn’t scanning that you’ll “be out a 1000 token” or whatever.

I have complete confidence that if my CoA isn’t scanning, td will make it right and the worst possible scenario here is I might get held up at the epilogue are for a bit while TD figures out what is going on.

TD can easily de-label my non scanning CoA, authenticate that it is indeed an rfid based chip, and then replace it.

the token validator is available for download. it is in a thread a while back. I am not digging for it, because I dont need it

Token Validator for IOS: Token Validator

Token Validator for Android: Token Validator

The app checks your Charm of Avarice token. It requires 2 scans to validate a token. On IOS, both occur with just one token placement. For Android, you need to bring the token to the phone twice, but the app leads you through the process.

The app requires internet access in order to do a complete validation. If internet is not available, the app will do a software validation, which is not as complete, but verifies that the record format is correct and answering correctly. The internet calls are required for decryption and final checks.

The app also requires NFC hardware, which only occurs on phones. iPhone 7 or later. Android phones are hit and miss. Check with the manufacturers specs on whether your Android phone includes NFC hardware.

The apps are free for download.

I see the Orb will have RFID too.

Kaledor wrote: I see the Orb will have RFID too.

IIRC Orbs started having them in the 2018 Orb. This was the reason it was sent seperate from the $8k order and included with the modules that year.

Kaledor wrote: I see the Orb will have RFID too.

FYI Token Validator only works on CoA.

The orbs have a different RFID in them.