Loops HouseSaltline

NEAR HACKATHON
Links
Team
1 member- EMOwner
Emmanuel Osadebe
Overview
Web3 games usually bolt a token onto a game: the economy sits in a trading screen beside the play, and nothing you own can be lost, so nothing has value. Saltline puts the economy inside an extraction shooter that runs in the browser.
You go over the fence of a port run by a machine, cut container seals and carry out what you can. Everything you take goes on an invoice you can see the whole time, and when it is big enough the port sends the Bailiff, which cannot be destroyed. Reach the boat and the haul is yours. Die and your gun lies in a wreck that another player can carry out.
How NEAR fits:
- Every gun is an NEP-171 NFT with rolled stats, wear, a maker who earns 2% of every sale, and a level that comes from the raids it has come home from. Parts, mods and scrip are NEP-245 tokens in the same contract.
- The NPCs have wallets. Moss and Ines are NEAR accounts that buy parts with their own scrip, build guns from their own stock, give a reason for every price and can go broke. The villain has a wallet too: every 500 scrip players pay it is one more machine on everyone's raid, and its strength halves every 12 hours.
- No account, the owner's included, can create scrip, parts or guns outside the contract's rules, and a test checks that.
- Players never see the chain: they sign in with Google and get a NEAR account, with no wallet, seed phrase or gas prompt.
- A fast-forward plays a week of the economy in a minute, so anyone can watch prices and wallets move.
We played the whole loop on the live testnet contract (a gun built, sold, resold with its maker paid, lost in a wreck and recovered by another player, and a payment that raised the villain's strength); the transactions are in the README. In Skirmish, players fight each other live.
It is live on NEAR testnet, with a front page that reads the contract. It was built during the hackathon around a shooter the lead had made earlier; that baseline is tagged pre-hackathon and disclosed in the README.