Angel Battles Historic Wrapper
Angel Battles Historical NFTsAngel Battles is a limited-supply, pre-ERC721 game with the first contract deployed on the Ethereum mainnet in block 4949586 (Jan-22-2018 01:42:39 AM +UTC). The game was one of the most complex and functional games of its time, spanning 3 NFT data contracts and dozens of gameplay contracts. Features included: Three Token Types – Angel Cards were the base card and had one of 6 aura colors. Angels were sold and earned experience by winning arena battles. Pet Cards w...
Angel Battles Guide
Welcome to Angel Battles, one of the oldest NFT projects. We launched in Jan 2018 and became one of the top 5 games on Ethereum, but rising gas fees made mainnet too expensive. We then rebuilt the entire game for a low gas fee environment that allows much richer gameplay. In Angel Battles, 100% of the money that comes in to the game through purchase of new packs goes to the Gitcoin Matching Fund to fund public goods. Having the game 100% on chain and the developers as volunteers means that we...
Deploying on Polygon
We are excited to announce that we have chosen to deploy Angel Battles 2 on the Polygon network. We watched several scaling solutions develop over the last few years and carefully considered where the best place to deploy Angel Battles 2 would be. It was a difficult decision where it seemed like new front runners were constantly emerging. We considered solutions under the following criteria.Security – While we don’t need the full security of Ethereum, a more secure scaling solution is better....
Angel Battles Historic Wrapper
Angel Battles Historical NFTsAngel Battles is a limited-supply, pre-ERC721 game with the first contract deployed on the Ethereum mainnet in block 4949586 (Jan-22-2018 01:42:39 AM +UTC). The game was one of the most complex and functional games of its time, spanning 3 NFT data contracts and dozens of gameplay contracts. Features included: Three Token Types – Angel Cards were the base card and had one of 6 aura colors. Angels were sold and earned experience by winning arena battles. Pet Cards w...
Angel Battles Guide
Welcome to Angel Battles, one of the oldest NFT projects. We launched in Jan 2018 and became one of the top 5 games on Ethereum, but rising gas fees made mainnet too expensive. We then rebuilt the entire game for a low gas fee environment that allows much richer gameplay. In Angel Battles, 100% of the money that comes in to the game through purchase of new packs goes to the Gitcoin Matching Fund to fund public goods. Having the game 100% on chain and the developers as volunteers means that we...
Deploying on Polygon
We are excited to announce that we have chosen to deploy Angel Battles 2 on the Polygon network. We watched several scaling solutions develop over the last few years and carefully considered where the best place to deploy Angel Battles 2 would be. It was a difficult decision where it seemed like new front runners were constantly emerging. We considered solutions under the following criteria.Security – While we don’t need the full security of Ethereum, a more secure scaling solution is better....
Subscribe to angelbattles.eth
Subscribe to angelbattles.eth
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
We’re sorry you are having issues playing Angel Battles. First of all, it’s important to understand how Angel Battles works – you are playing a cutting edge, publicly available, globally distributed system that no one ‘owns’ or is ‘in charge’ of. Angel Battles original devs have done our best to ensure you have a smooth experience, but there may be certain issues.
If the question is about how the game works, strategy, etc. – make sure to check the official guides first.
The game is complex and the guides are detailed. If it’s a blockchain issue, however, try the following tips to help you troubleshoot.
Step 1 - Localize the Problem – Make sure you are logged in to your wallet and connected to the site. If you check your wallet and the tx says ‘pending’ or ‘queued’, then it’s probably an issue with the Poylgon network. If the web user interface (UI) looks out of wack, or things aren’t refreshing, it could be a problem with the web front end.
Try Refreshing the Page – In the case where your angels weren’t loading, a battle result was taking forever (but the transaction went through) or your wallet wasn’t connecting, refreshing the page can help.
Change RPC Provider – Unless you run your own node, you need to use someone else to provide this direct connection to the blockchain. These nodes generally work, but can become congested, fail, or implement rate limits. Sometimes switching to an alternative RPC provider can help restore your connection to the blockchain. This is more of an issue on testnets vs Polygon mainnet.
Reset Metamask – If you have many ‘queued’ transactions in metamask that are not going through, sometimes resetting metamask may help. Go to Settings >> advanced >> reset account. Note: resetting will NOT require you to reenter your seed phrase or affect anything on the blockchain.
Increase Gas Limit – Wallets will usually estimate how much gas you need for a certain action, but sometimes due to randomness or other user actions, this fails. If you have a tx that fails and the gas used is a high % of the gas available, increasing the gas limit might help. We have tried to hardcode this in where helpful. Note: Any unused gas is always refunded back to you, so although your wallet might estimate a higher fee, what you actually pay will be lower. Also, be careful not to confuse the gas limit with the gas price.
Run The Front End Locally – You can get a copy of the front end code and run it locally, if there are issues accessing the front end on IPFS. Running the front end locally will also allow you to insert logging statements or make other changes. If your front end change improves the user experience, consider opening a pull request.
Speed Up Tx - Most wallets will select a good gas price, but networks can quickly become congested (i.e., with spikes in prices, popular NFT mints, etc.). You can usually choose to ‘speed up’ a transaction by paying a higher price.
Try Later – RPC issues, network congestions, etc. will generally resolve themselves over time. Sometimes waiting a couple of hours can make for a much better experience.
Manual Update Button – For Arena and VS Battles, the UI should automatically update after the blockchain confirms the result of a battle. However, we have included a manual update button that will read the current state of the battle (round, hp, buffs, etc.) and update the UI.
Open The Console – You can right click and then ‘inspect’ if on desktop to see the browser console. We have embedded some statements that may help and you can use the browser’s built in debugger.
Be Aware of Card Quantity – The web UI needs to read each card from the blockchain, so if you own a very large number of cards (i.e., many hundreds) it might be best to split them between wallets.
Ask for More Help – You can always open an issue on the Angel Battles github repo or discord https://discord.gg/u2xgWuQ
We’re sorry you are having issues playing Angel Battles. First of all, it’s important to understand how Angel Battles works – you are playing a cutting edge, publicly available, globally distributed system that no one ‘owns’ or is ‘in charge’ of. Angel Battles original devs have done our best to ensure you have a smooth experience, but there may be certain issues.
If the question is about how the game works, strategy, etc. – make sure to check the official guides first.
The game is complex and the guides are detailed. If it’s a blockchain issue, however, try the following tips to help you troubleshoot.
Step 1 - Localize the Problem – Make sure you are logged in to your wallet and connected to the site. If you check your wallet and the tx says ‘pending’ or ‘queued’, then it’s probably an issue with the Poylgon network. If the web user interface (UI) looks out of wack, or things aren’t refreshing, it could be a problem with the web front end.
Try Refreshing the Page – In the case where your angels weren’t loading, a battle result was taking forever (but the transaction went through) or your wallet wasn’t connecting, refreshing the page can help.
Change RPC Provider – Unless you run your own node, you need to use someone else to provide this direct connection to the blockchain. These nodes generally work, but can become congested, fail, or implement rate limits. Sometimes switching to an alternative RPC provider can help restore your connection to the blockchain. This is more of an issue on testnets vs Polygon mainnet.
Reset Metamask – If you have many ‘queued’ transactions in metamask that are not going through, sometimes resetting metamask may help. Go to Settings >> advanced >> reset account. Note: resetting will NOT require you to reenter your seed phrase or affect anything on the blockchain.
Increase Gas Limit – Wallets will usually estimate how much gas you need for a certain action, but sometimes due to randomness or other user actions, this fails. If you have a tx that fails and the gas used is a high % of the gas available, increasing the gas limit might help. We have tried to hardcode this in where helpful. Note: Any unused gas is always refunded back to you, so although your wallet might estimate a higher fee, what you actually pay will be lower. Also, be careful not to confuse the gas limit with the gas price.
Run The Front End Locally – You can get a copy of the front end code and run it locally, if there are issues accessing the front end on IPFS. Running the front end locally will also allow you to insert logging statements or make other changes. If your front end change improves the user experience, consider opening a pull request.
Speed Up Tx - Most wallets will select a good gas price, but networks can quickly become congested (i.e., with spikes in prices, popular NFT mints, etc.). You can usually choose to ‘speed up’ a transaction by paying a higher price.
Try Later – RPC issues, network congestions, etc. will generally resolve themselves over time. Sometimes waiting a couple of hours can make for a much better experience.
Manual Update Button – For Arena and VS Battles, the UI should automatically update after the blockchain confirms the result of a battle. However, we have included a manual update button that will read the current state of the battle (round, hp, buffs, etc.) and update the UI.
Open The Console – You can right click and then ‘inspect’ if on desktop to see the browser console. We have embedded some statements that may help and you can use the browser’s built in debugger.
Be Aware of Card Quantity – The web UI needs to read each card from the blockchain, so if you own a very large number of cards (i.e., many hundreds) it might be best to split them between wallets.
Ask for More Help – You can always open an issue on the Angel Battles github repo or discord https://discord.gg/u2xgWuQ
No activity yet