NFT-On-Chain-Metadata VS nft-mix

I wanted to create an NFT that chooses between an enum of 3 different NFT types. Also I wanted this choice to be decided at random so the minter doesn't know what type of NFT they'll get. I followed this NFT as a guide https://github.com/PatrickAlphaC/nft-mix/blob/main/contracts/AdvancedCollectible.sol. The only significant change that I made was switching Chainlink to API3 as my random number provider. I used a basic API3 implementation to get the random number like this https://github.com/Ashar2shahid/eth-denver-hackathon/blob/master/contracts/Requester.sol. I was able to Franken-code the 2 contracts together to get this:

I tried to make a contract that mints a token from an enum of options https://gist.github.com/ChristianOConnor/0ae15b021521c9583dde6c3cc782d4d3. This code fails at every turn. I started with the code from this video https://youtu.be/MFgMpA819DU. I didn't want the strength or intelligence to be generated dynamically, I just had an array of 3 character types that I wanted chosen at random. From my contract: enum Classifier{FIRST, SECOND, THIRD}. I used this contract as a reference for how to select at random from an enum https://github.com/PatrickAlphaC/nft-mix/blob/main/contracts/AdvancedCollectible.sol. This Patrick Collins contract uses Chainlink but I swapped that out with API3. My contract is a complete failure. What am I doing wrong?

I'm using this program to make an NFT https://github.com/PatrickAlphaC/nft-mix and I get this error when I run create_collectable.py