> For the complete documentation index, see [llms.txt](https://docs.nowayback.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nowayback.io/game/lore/plague-invaders.md). # Plague Invaders ### Invaders from other Games Beyond the warring realms of NWB, different Plagues of Invaders arrived in the NWB Metaverse. For all of their terror, the Plague Invaders become a common enemy that united the once-warring NWB Realms. To defend the Resources for the good of all Realms! The Plague Invaders sneaked in from other game universes to extract the invaluable Resources of NWB, seeking to create their own crafting system and trade them in new cross-world markets they set up. It is told that Monsters from the land of Monstropoly were the first Plague to Invade NWB. These fierce creatures came armed with different kinds of weapon: * Bigger Monsters (Tanks) resist more damage, using their fists to propel themselves towards enemies and deal damage * Assassin Monsters are fast creatures that use swords to swiftly slay their enemies * Gunner Monsters are weaker creatures that fire heavy weapons * Small Monsters are cute creatures that shoot long-distance weapons and deal significant damage --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.nowayback.io/game/lore/plague-invaders.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.