cheatmsx.com

CheatMSX (cheatmsx.com) is an MSX gaming resource that collects cheats, maps, manuals, walkthroughs, password generators, and emulator cheats in one place. Its FAQ-style help content is not a single standalone "FAQ" page; instead, answers to common MSX gaming questions are spread across the site's resource sections and its community areas (Forum, Contact, About us). If you are looking for a specific answer, the fastest route is usually the matching resource category rather than a general FAQ list.

How the site is organized

The main navigation and statistics give a clear picture of what exists on CheatMSX:

Titles are browsable alphabetically (A–Z and 0–9) or through "Show all titles."

Where FAQ-type answers actually live

Because there is no dedicated FAQ menu item in the main navigation, treat these sections as the practical FAQ:

• Cheats and Emulator Cheats — the most common "how do I get past this" questions.
• Online Password Generators — answers to password-protected game stages.
• Manuals — official documentation, useful when a question is about controls or mechanics rather than cheats.
• Walkthroughs — longer answers that a short FAQ entry could not cover.
• Forum — for questions not covered by any existing entry.
• About us / Contact — for site-level questions rather than game-level ones.

Finding an answer step by step

1. Identify what kind of question you have (cheat, password, map, manual, patch).
2. Pick the matching section from the list above.
3. Use the alphabetical index (A–Z, 0–9) or "Show all titles" to locate the game.
4. Open the entry and check whether it covers your platform or emulator.
5. If nothing matches, post in the Forum.

Expected result: you either land on a specific entry for your game, or you confirm the site has no entry and the Forum is the next step.

Common blocker: the page will not display

The site shows this notice when content is blocked:

Please disable your adblock and script blockers to view this page

If sections appear empty or comments do not load, disable your ad blocker and script blocker for cheatmsx.com and reload. Comments are powered by Disqus and require JavaScript, so a script blocker will also hide them.

FAQ vs. the other resources

A quick way to choose the right section:

• Need a code to skip a level → Cheats
• Need the code to work inside an emulator → Emulator Cheats
• Stuck at a password prompt → Online Password Generators
• Need to know what an item does → Manuals
• Need a full route through the game → Walkthroughs
• Need a fan translation or bug fix → IPS Patches
• Need to change game behavior at memory level → Peeks & Pokes

Site details worth knowing

• Interface languages: English, Spanish, Portuguese.
• The site accepts support via PayPal Donation and Patreon; no pricing for content access is stated on the page.
• Copyright notice runs from 2009 to 2026, indicating a long-running archive.

Password auditing and password recovery are two sides of the same technical capability: testing how easily credentials can be guessed or cracked. Auditing is the proactive, authorized practice of measuring password strength across accounts you control; recovery is the reactive practice of regaining access to an account or file when the password is lost. Both rely on the same underlying techniques—dictionary, brute-force, and rule-based attacks—and both require authorization. LCPSoft, a vendor of cross-platform password auditing and recovery applications, frames its tools around exactly these use cases, including Linux user accounts and Oracle Database credentials.

Auditing vs. recovery: what actually differs

The techniques overlap almost completely. What changes is intent, timing, and who is allowed to run them.

A practical consequence: an audit that finds nothing weak is still a success, while a recovery attempt that fails is a failure. Don't conflate the two when reporting results.

How the common techniques work

All three approaches take a hash or encrypted credential as input and test candidate passwords against it. The difference is how candidates are generated.

Dictionary attacks

The tool tries passwords from a wordlist—common passwords, leaked lists, or a custom list built from the organization's vocabulary. Fast and effective against human-chosen passwords. The expected result is a quick hit rate on weak accounts and near-zero on strong ones.

Brute-force attacks

The tool enumerates every combination in a character set up to a length limit. Exhaustive but slow: each added character multiplies the search space. Useful for short passwords and PINs, impractical for long passphrases.

Rule-based (hybrid) attacks

Start from a dictionary and apply transformations—capitalization, appended digits, leetspeak substitutions, year suffixes. This mirrors how people actually "strengthen" weak passwords and catches far more real credentials than a plain dictionary.

Mask and combinator attacks

A mask specifies the pattern (for example, uppercase + lowercase + four digits), and combinator attacks join two wordlists. These sit between dictionary and brute-force in cost and coverage.

The practical takeaway: run dictionary and rule-based attacks first, then escalate to masks or brute-force only for accounts that survive. This ordering keeps audit time proportional to the value of the target.

Supported targets

LCPSoft's stated scope covers cross-platform password auditing and recovery, with Linux user accounts and Oracle Database credentials among the named targets. In practice this means:

• Linux user accounts — credentials stored in the local shadow file or validated through PAM. Auditing here tests the password policy actually enforced on the host.
• Oracle Database credentials — database user accounts, where the audit checks whether schema or application accounts use guessable passwords.
• Other systems — the same techniques apply to any credential store you are authorized to test, but confirm the tool supports the specific hash or authentication format before planning an engagement.

Verify format support before you start. A tool that handles one hash type may not handle another, and a failed run is often a format mismatch rather than a strong password.

Legal and ethical boundaries

Only audit or recover credentials on systems you own or have explicit written authorization to test. This is not a formality—unauthorized password cracking is illegal in most jurisdictions regardless of intent.

Practical rules:

• Get scope in writing: which hosts, which accounts, what time window.
• Never run recovery against third-party services; use their official account-recovery process instead.
• Store any recovered plaintext securely and destroy it once the audit or recovery is complete.
• Report findings to the system owner, not to a wider audience.

If you cannot produce authorization, stop.

Interpreting results and fixing weak passwords

Raw crack counts are not the deliverable. What matters is what the results tell you about policy and user behavior.

Look for:

• Crack rate by account group — a high rate among admin or service accounts is a priority finding.
• Time-to-crack — passwords that fall in seconds under a rule-based attack are effectively absent.
• Reuse and patterns — repeated base words or predictable suffixes signal a training problem, not just individual weak choices.

Then act:

1. Force a reset on every cracked account.
2. Tighten the policy: minimum length, block known-breached passwords, and rate-limit authentication attempts.
3. Re-audit after the reset to confirm the fix holds.
4. Move high-value accounts to multi-factor authentication so a single weak password is no longer sufficient.

The goal of an audit is not a clean report—it's a measurable reduction in the number of credentials an attacker could guess.

A peek reads a value from a specific memory address, and a poke writes a value to one. On CheatMSX, the Peeks & Pokes section is a small, separate collection (the site's statistics list 7 entries) of raw memory addresses and values for MSX games, distinct from the much larger Emulator Cheats collection (364 entries). You use them by entering the address and value into your MSX emulator's memory editor or debugger while the game is running, then verifying the effect in-game.

Peek vs. poke: the core distinction

A peek tells you what is currently stored; a poke changes it. In practice you peek first to confirm an address holds what you expect, then poke to alter it. Poking blind is the most common reason a listed value appears to do nothing.

How peeks and pokes differ from emulator cheats

Emulator cheats are usually applied through a cheat engine or a cheat file that the emulator loads and manages for you — you toggle a named cheat on or off. Peeks and pokes are lower-level: you supply the raw address and value yourself through the emulator's memory tools. That makes them more flexible (any address, any value, no pre-built cheat file needed) but also less forgiving, since nothing validates the address for you. CheatMSX keeps them in separate sections, which reflects that difference in workflow.

Finding the Peeks & Pokes section on CheatMSX

The site organizes content by type, and the statistics panel lists "Peeks & Pokes" alongside Emulator Cheats, Cheats, Maps, Manuals, Walkthroughs, IPS Patches, and Online Password Generators. Navigate to that section from the site's content categories to see the available entries. Because the collection is small, treat it as a supplement to the larger Emulator Cheats set rather than a primary source — if a game you want isn't covered there, check the Emulator Cheats section first.

Applying a peek or poke while playing

The general workflow, which works in most MSX emulators that expose a memory editor or debugger:

1. Load the game and get to a state where the value you want to change is visible or known (e.g., you can see your life count).
2. Open the emulator's memory editor / debugger. The exact menu name varies by emulator; look for "Memory," "Debugger," or "Cheat" tools.
3. Peek the address from the CheatMSX entry. Confirm the byte matches what the entry or your in-game value suggests. If it doesn't match, the address may be for a different game version or a different memory state.
4. Poke the new value into that address.
5. Return to the game and verify. The change should appear immediately for values the game reads each frame; some values are only read at specific moments (level load, menu open), so you may need to trigger that moment.

Expected result: the in-game value reflects what you poked. If nothing changes, re-peek the address — many games overwrite a value on the next frame, which means the poke needs to be repeated or the address is a copy rather than the live one.

Common pitfalls

• Wrong address for your version. Different regional or revision releases of the same MSX game can store values at different addresses. A poke that works on one dump may do nothing on another.
• Address holds a copy, not the source. Games often mirror a value in several places. Poking a display copy changes what you see but not the game logic, or vice versa.
• Value overwritten immediately. If the game recalculates the value every frame, a one-time poke is reverted. You need a repeating poke or a cheat engine that re-applies it.
• Emulator compatibility. Not every MSX emulator exposes a memory editor, and the tools differ. If yours has no way to enter an address and value directly, peeks and pokes aren't usable there without a cheat-file format the emulator supports.
• Decimal vs. hexadecimal. Addresses and values are often given in hex. Entering a hex value as decimal (or the reverse) produces a wrong result that looks like a failed poke.

Because the Peeks & Pokes collection on CheatMSX is small, the practical approach is: check it for your specific game, and if it isn't listed, use the Emulator Cheats section or peek the address yourself to find the value you want to change.

Retro gaming is the practice of playing older video games — typically from the 1970s through the early 2000s — on original hardware, through emulation, or via official re-releases. It is defined less by a fixed year cutoff than by a combination of era, hardware generation, and design style. If you want to start, the practical path is: pick a platform generation, choose how you want to play (original hardware, emulation, or a modern re-release), then solve the two problems that trip up most beginners — display lag and region locking.

What "Retro" Actually Means

There is no single agreed cutoff, and the term shifts as time passes. A useful way to think about it is in three layers:

• Era — games from roughly the late 1970s to the early 2000s, before HD displays and online distribution became standard.
• Hardware generation — cartridge and early disc consoles: NES, SNES, Sega Genesis/Mega Drive, Game Boy, PlayStation, and similar machines.
• Design style — pixel art, limited sprites and color palettes, chiptune audio, and often high difficulty with limited or no save systems.

A game can feel "retro" in style even if it is new. GGGames.se, an enthusiast site covering both modern and retro games, frames its coverage around exactly this split — "Modern and Retro" — and its review of QUOD INIT EXIT IIo covers a game that is new but built in a deliberately old-school style. That is a good illustration of why style matters as much as release date.

The Main Retro Platforms

Each generation has its own quirks — controller design, region coding, and video output all differ — so it helps to pick one platform to start rather than trying to cover everything at once.

Three Ways to Play, and How to Choose

Original hardware

You buy the actual console and cartridges or discs. This gives the most authentic experience, including original controllers and timing. The trade-offs are cost, aging hardware (worn cartridge slots, failing disc drives), and the need for a compatible display.

Emulation

Software runs the game on a modern computer or device. This is the most flexible and often the cheapest route, and it makes save states and region-free play easy. The catch is that the legal status of ROMs varies by country, and reliable sources matter — avoid sketchy download sites.

Official re-releases and compilations

Publishers and platforms reissue classic games on modern systems, sometimes with save states, rewind, and display options. This is the lowest-friction option if you want to play legally and without setup. Availability changes over time, so check the current store listing for the specific title you want.

A simple decision rule: if you want authenticity and don't mind maintenance, go original hardware. If you want convenience and flexibility, go emulation or official re-releases.

Common Pitfalls to Avoid

• Display lag — modern TVs can add input delay that makes precise retro games feel wrong. A low-latency mode or a dedicated upscaler helps.
• Region locks — many older consoles only play games from their own region. Check before buying imports.
• Unreliable ROM sources — unofficial download sites carry legal and security risks. Prefer official re-releases where they exist.
• Assuming "old" means "cheap" — some retro hardware and cartridges are collectible and priced accordingly.

A Practical Starting Path

1. Pick one platform generation that appeals to you.
2. Decide how you want to play: original hardware, emulation, or an official re-release.
3. If using original hardware, sort out your display and check region compatibility.
4. Start with a well-regarded title for that platform rather than a rare or expensive one.
5. Expect higher difficulty and fewer conveniences than modern games — that is part of the design, not a flaw.

If you are unsure where to begin, following a site that covers both modern and retro games — like GGGames.se — can help you find reviews and context for older titles alongside current releases.

A battle map is a scaled, top-down map used during tabletop RPG encounters to show where characters, monsters, and terrain sit relative to each other. You use one when positioning matters — combat, chases, traps, room-by-room exploration — and skip it for purely narrative scenes. You can make one by drawing terrain in a vector editor, placing assets, then exporting for screen, print, or a virtual tabletop. DungeonFog is one tool built for exactly this workflow.

Battle map vs. world map: what's the difference

These two map types answer different questions, and mixing them up is the most common early mistake.

A battle map zooms in far enough that a single chair or pillar changes your tactics. A world map zooms out far enough that a single chair is invisible. You generally need both over a campaign, but they serve different moments at the table.

When to actually put a battle map down

Reach for a battle map when the answer to "where exactly is everyone?" changes the outcome:

• Combat — line of sight, flanking, area-of-effect spells, and movement speed all depend on position.
• Dungeon crawling — doors, corridors, and room shapes matter for exploration and ambushes.
• Chases and escapes — distance and obstacles drive the tension.
• Stealth and traps — who is standing where determines what gets triggered.

Skip the map for shopping, negotiation, travel montages, and any scene where nobody cares about exact distance. Forcing a grid onto a conversation slows the game down.

How to make a custom battle map

DungeonFog describes a three-step process: create a map, place assets, then export and play. Here's what each step involves and what to expect.

1. Draw the terrain

Start with the layout — dungeon walls, building floor plans, or overland terrain. DungeonFog uses a vector-based editor, which means shapes stay sharp when you scale or print them, rather than turning blurry like a stretched bitmap. Draw the rooms and corridors first; decoration comes later.

2. Place assets

Populate the map with props, furniture, and terrain features. DungeonFog's library lists over 3,000 assets spanning different time periods and settings, and new asset packs are released monthly as part of its premium content subscription. Search the library for the pieces that match your story rather than settling for whatever's closest.

3. Export and play

You can play with others inside DungeonFog itself, or export and print the map. Exporting is where your earlier choices pay off — a vector map holds up at print resolution, and a well-scaled grid keeps tokens aligned.

Key considerations before you commit

• Grid scale. Decide your squares-per-inch (or per-5-feet) before you draw, not after. Changing it later means redoing the layout.
• Resolution. If you plan to print, you need higher resolution than for on-screen play. Vector output helps here.
• Asset library size. A bigger library means less time hunting for the right prop — but also more browsing. Check whether the library covers your campaign's setting (fantasy, modern, horror, etc.).
• Where you'll play. On screen, printed, or inside a virtual tabletop each has different export needs.

Ways to play with your map

• On screen — display the map on a TV or monitor laid flat or mounted, and move physical minis on top.
• Printed — export at print resolution and tile the pages for a physical battle mat.
• In a virtual tabletop — play with others inside DungeonFog, or export the file for use in your VTT of choice.

The practical takeaway

If you only need a quick sketch, paper and a marker still work. If you want reusable, high-detail maps that survive printing and scaling, a vector editor with a large asset library saves real time across a campaign. DungeonFog fits that second case — free to sign up, with premium memberships and a marketplace for additional content. Check the pricing page for current tiers before committing, since asset packs and premium features sit behind that subscription.