# About Counter Fire ***After careful market research and testing, the product name will be changed from CEBG to Counter Fire, a name that will resonate with players and leave a lasting impression. All assets, gameplay, and value will remain unchanged.*** {% embed url="" %} Counter Fire is a light online multiplayer Battle Royale game. Counter Fire is the first Anime + MOBA + beauty + mecha game on blockchain. The anime style is also one of the most important aesthetic preferences of young people in the next era. The core gameplay of Counter Fire is similar to the PUBG, the famous game. In the game, up to 40 players parachute onto an island and scavenge for weapons and equipment to kill others while avoiding getting killed themselves. The available safe area of the game's map decreases in size over time, directing surviving players into tighter areas to force encounters. The last player or team standing wins the round. Counter Fire focuses on optimizing the fragmented scenario needs of mobile users. Counter Fire is a social game, you can make friends in the game, you can also team up with real friends to play games and experience victory. Counter Fire embeds both Play-To-Earn and Free-To-Play mechanisms so that both the P2E players and traditional players can be satisfied at the same time. Every traditional gamer who likes Counter Fire or makes friends in Counter Fire has potential to be converted into a blockchain player. We aim to attract players to Counter Fire world every day. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://contact-63.gitbook.io/cebg-whitepaper/about-counter-fire.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.