How To Check If My Ships Have Joined A Mission?

Article author
Male Nordic #2059
  • Updated

Sometimes it can happen that a ship sent on a Mission will not show right away in the game interface. To see that it was recorded on the blockchain, follow the below instructions:

1) Open your MetaMask wallet, navigate to "Activity" and find your "Join To Mission" action of the mission you are looking for. Usually the last one you just sent.

mceclip1.png

 

2) Click on the arrow in the top right to see the transaction on bscscan.com

mceclip0.png

 

3) On BSCscan.com, click on the tab "Logs" and there you can find the mission ID (77 in this example) and the number of ships (in this example 4) and 800 TLM sent (TLM has 4 decimal places)

mceclip2.png

 

4) To actually check if the ships were recorded on the contract, you not down your mission ID from step 3) and the number of ships from step 3) and go to this link to ask the smart contract: https://bscscan.com/address/0xbea8302e8b0f8d4ee45f7ca9161c4a2e4f255123#readContract

 

5) Enter your mission ID noted in step 3) and your BSC wallet address into item 3 in the contract

mceclip1.png

 

6) Click "Query" and check if the number of ships sent matches what you saw in step 1

mceclip0.png

 

7) Note that the "BNBAmount" will always be zero, but the number of ships determines the amount TLM staked. So this confirms that your ships indeed have joined the mission. When the mission returns, you will then be able to claim your TLM and NFT rewards.

 

8) Also note, that if you have already claimed your mission rewards, the contract will also return zero as the mission is no longer underway.

 

 

---

The only official smart contract addresses are:

TLM on ETH (ERC20): https://etherscan.io/token/0x888888848B652B3E3a0f34c96E00EEC0F3a23F72

TLM on BSC (BEP20): https://bscscan.com/token/0x2222227E22102Fe3322098e4CBfE18cFebD57c95

TLM on WAX (EOSIO): https://wax.bloks.io/account/alien.worlds

Mission Contract on BSC(BEP20): https://bscscan.com/address/0xBea8302e8b0F8d4ee45f7CA9161C4A2e4f255123

Was this article helpful?

33 out of 34 found this helpful

Have more questions? Submit a request