# PokeWilds: a Gen 2 engine built on libGDX, and what its alpha status means for you > PokeWilds is a cross-platform Gen 2 style game and engine by SheerSt, distributed as zipped builds for Windows, Linux and macOS. It is in alpha, its README says to expect bugs, and the most recent tagged release predates the current source tree by more than two years. **SheerSt/pokewilds** — PokeWilds - A Gen 2 Game/Engine using libGDX - Repository: https://github.com/SheerSt/pokewilds - Stars: 2,893 · Forks: 219 - Language: Assembly - License: not declared - Published: 2026-09-28 · Updated: 2026-09-28 · Language: en - Canonical page: https://hysenlabs.com/projects/sheerst-pokewilds ## What PokeWilds is, and who the alpha is actually for PokeWilds is a Gen 2 game and engine built on libGDX. The README describes it as using procedural generation to create large worlds with different biomes, each with its own monsters, and scaling wild monster levels the further you explore. It is not a ROM hack and it is not an emulator front end: the README answers the emulator question directly, saying the game runs natively on Windows, Mac and Linux and is coded with Java and the libGDX framework. The audience is narrower than the download page suggests. This is for people who want the feel of the console games plus a survival and construction layer: field moves that cut, dig and smash resources, BUILD for walls, roofs, furniture and beds, and gates made by placing a door between fence tiles. It is also for people who want to read the engine's data files, since the README points at core/assets/attacks/ as the place where the extra capabilities live. The disclaimer is blunt: the project is in Alpha, and the README says to expect bugs and asks you to file an issue on GitHub when you find one. Treat that as the contract. If you need a finished game, this is not it yet. ## Procedural biomes, level scaling and the field-move economy The world is generated rather than authored. Biomes differ in which monsters appear, and monster levels rise with distance from where you started, which turns geography into a difficulty curve: the README notes that biomes with rare monsters are difficult to get to. That single design choice does more work than any menu, because it makes travel itself the progression. The field-move system is the second mechanism. Beyond the familiar traversal moves, the README lists new HMs for interacting with the world: building structures and houses, jumping up ledges, starting fires. Resources come from CUT, DIG and SMASH, each known by different types of monsters. Materials also come from capturing monsters and dropping them in an area they are happy in, then talking to them. Happiness is type-driven, and this is the part worth understanding before you build anything. A monster needs its preferred habitat tiles. Dual-type monsters need tiles for both types. The README's example is Chikorita, which needs only tall grass, against Jumpluff, which needs tall grass and trees. Monsters produce materials only when happy, so base placement is really habitat planning. Teleport is gated the same way. You cannot teleport anywhere: you must first build teleport beacons, then select one when using TELEPORT. ## Installing PokeWilds on Windows, Linux and macOS There is no package manager, no installer and no build step for players. The README gives three download links on the latest release, split by platform: a Windows 64-bit zip, a Linux 64-bit zip, and a combined other-platforms zip covering Mac, Linux 32-bit and Windows 32-bit. Download the one that matches your machine and extract it. ```bash # Windows 64-bit https://github.com/SheerSt/pokewilds/releases/latest/download/pokewilds-windows64.zip # Linux 64-bit https://github.com/SheerSt/pokewilds/releases/latest/download/pokewilds-linux64.zip # Mac, Linux 32-bit, Windows 32-bit https://github.com/SheerSt/pokewilds/releases/latest/download/pokewilds-otherplatforms.zip ``` The README does not put the run instructions in the repository. It says to follow the instructions inside the README.txt file in the game folder, so open that file before you double click anything. On Windows, the README's first common issue is that launching through the Windows search results leads to save loss. Double click pokewilds.exe from the folder instead. On macOS, double clicking pokewilds.jar leads to save data loss; the README says to follow README.txt to create a launcher you can safely double click. If the screen goes black at night, run pokewilds-compat.exe rather than the normal executable. Controls, once you are in: ```text Arrow keys to move Keyboard Z = A button Keyboard X = B button Keyboard Enter = Start button Hold keyboard X to run. ``` To stop a monster from using its field move, stop moving and hold X. Settings live in settings.txt, and the README's rules are specific: no spaces around the '=', keys must be capitalized, muteMusic takes true, and specPhysSplitEnabled toggles the special and physical split. ## The save-corruption path, and why the backup file matters Save handling is the sharpest edge in the project, and the README treats it as a known hazard rather than an accident. Two of the five common issues are save loss caused by how you launch the game, on Windows and on macOS respectively. The mitigation is procedural: start the executable from its folder, not from a search result, and on macOS build a launcher as README.txt describes. Recovery exists but is manual and depends on you knowing the naming scheme. The game folder holds a zip of your last save. If your save is default.sav, the backup is default.sav.zip. Separately, the README documents a second path for a corrupted save: the backup is named .sav.backup, you rename it to .sav.zip, extract it, and the result must be a directory called .sav/ containing files like game and map0,0. Then you load the new name from the menu. Read those two paragraphs as one system. There is a backup, but restoring it means renaming files and checking the extracted directory structure by hand. If you are not willing to do that, keep your saves somewhere you can copy them. One more environmental failure: running the game inside a Windows OneDrive folder sometimes prevents it from running at all. The README's fix is to put PokeWilds outside OneDrive. ## World generation stalls and other things the README admits World generation can hang. The README describes a rare issue where generation takes over 10 minutes and gets stuck, with the advice to close the game and retry, noting that the game prompts you to save on exit. That is a real failure mode for a procedural world, and it is the kind of thing that makes an alpha feel like an alpha. There are smaller rough edges. Reading a sign can leave your text glitchy, which the README says is not a bug and resolves by walking into tall grass to trigger an encounter. That explanation is charming and also a sign of how much of the game's behaviour is undocumented outside the README. The content is incomplete by the project's own account. The Pokédex is not in the game; the README says it will be added on the next update and points to an external document for habitats, field moves and harvestable items. Trade evolutions have been reworked for single player into stone-based evolutions, with a separate document for the new methods and stone locations. Where the README is silent matters too. It does not document a supported way to migrate a save between versions, and it does not state a licence for the repository, so anyone planning to reuse the engine rather than play the game has no stated terms to work from. ## PokeWilds multiplayer, mobile and mods: what is and is not there The README is direct on multiplayer: not currently, but 0.9 will bring online multiplayer alongside other features. Until that ships, the game is single player, which is why trade evolutions were converted to stone-based ones. Mobile is the same answer: not currently, with plans. So the two most common search intents around this project, multiplayer and Android, both land on a stated future version rather than a present feature. Mods are a different case. The repository is an engine, and the README notes that the extra capabilities beyond the console games live in core/assets/attacks/, with sprite and animation work ripped from the console game for accuracy. That tells you the data is file-based and inspectable, but the README does not document a mod loader, a plugin API or a stable asset schema. Editing files is not the same as a supported modding surface, and an alpha with no published licence makes redistribution questions worse, not better. Offline play is the one place the project is unambiguous: it runs natively, so there is no server to depend on. The shiny odds are stated as 1 in 256, and the README says that will become user-adjustable in the next update. ## How PokeWilds differs from ROM hacks and from engine frameworks The nearest alternative in practice is a ROM hack running in an emulator. The difference is architectural, not cosmetic. A ROM hack patches existing console code and inherits the original's constraints on map size, memory and platform. PokeWilds is a Java and libGDX application, and the README lists what that buys: cross-platform play, multiplayer, huge maps and fullscreen mode. Procedural generation at that scale is not something a Gen 2 ROM hack does, because the hardware budget was never there. The cost of that choice is the opposite of the ROM hack's. A ROM hack runs in an emulator that thousands of people have already configured, with save states and fast-forward. PokeWilds ships as three zip downloads, needs README.txt read before first launch, has platform-specific launch traps that can cost you a save, and has no Pokédex yet. You are trading emulator maturity for engine freedom. The other comparison is to a general framework like libGDX itself, which the project uses rather than competes with. PokeWilds is an opinionated layer on top: Gen 2 sprites and animations, a field-move economy, habitat-driven monster happiness. If you want to build your own monster game, libGDX gives you nothing domain-specific, and PokeWilds gives you a working example to read, with the caveat that the repository states no licence. ## Conclusion Adopt PokeWilds if you want a native, emulator-free Gen 2 style game with procedural biomes and a building layer, and you are comfortable running alpha software where the README itself warns about bugs. Do not adopt it if you need online multiplayer (the README says 0.9 will bring it), mobile play (not currently supported), or a stable save format you can rely on without keeping the .sav.backup file. Before you invest time, verify three things: that your build matches your platform (the releases page splits windows64, linux64 and an otherplatforms zip), that your game folder is outside any Windows OneDrive folder, and that you have read README.txt inside the game folder, because that file, not the repository README, holds the actual run instructions. ## FAQ ### What can I play PokeWilds on? The README lists Windows 64-bit and Linux 64-bit as separate downloads, plus an other-platforms zip covering Mac, Linux 32-bit and Windows 32-bit. Mobile is not supported currently, though the README says there are plans. ### Is PokeWilds getting updates? The README states the game is being actively worked on and that there is no ETA on the next update. It also says version 0.9 will add online multiplayer alongside other features. ### Is PokeWilds multiplayer? No. The README says multiplayer is not currently available, and that 0.9, the next version, will bring online multiplayer to PokeWilds. ### Can you play PokeWilds offline? Yes. The README says the game runs natively on Windows, Mac and Linux, so there is no server requirement; the only online feature mentioned is the planned multiplayer in 0.9. ### Is PokeWilds complete? No. The README labels it Alpha, warns to expect bugs, and notes that the Pokédex will be added on the next update. ## Sources - [Issues](https://github.com/SheerSt/pokewilds/issues) - [README](https://github.com/SheerSt/pokewilds/blob/main/README.md) - [Releases](https://github.com/SheerSt/pokewilds/releases) - [SheerSt/pokewilds on GitHub](https://github.com/SheerSt/pokewilds) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/sheerst-pokewilds