CLASSIC PLAY · NATIVE MATCH OPTIONS · A REQUIREMENT-FIRST BUYING GUIDE
Choose the match you want to arrange before choosing the handheld.
If changing a classic game's match rules is part of why you want a retro handheld, identify the exact release, mode and options that matter. Check the complete routine: understand the offered choices, set the intended combination, confirm it, start meaningful play and observe the relevant rule in action. If you need the arrangement again, check whether it persists or must be re-entered. A settings screen is not proof that every selected rule applies to every mode.
Consider R36S for suitable compact classic play when the exact native options, meaningful controls, wanted view and supported configure-to-play routine fit. Compare R36MAX when you want a larger physical view of existing information. Neither panel size nor card capacity creates game-native rules, extra participants or a modern custom-match service.
Current descriptions list S with 3.5-inch IPS and MAX with 4-inch IPS, both at 640×480, RK3326 and 1GB DDR3L. Both describe a Linux-based retro gaming OS (ArkOS community firmware). MAX's larger panel is a physical-view choice, not a new rule editor or stronger listed processing platform.
USD base references read October 7, 2026: S64 $79.99, S128 $89.99, MAX64 $99.99 and MAX128 $109.99. Choose nominal room for a useful library after the essential match experience fits. Do not buy more capacity expecting it to reveal additional native controls.
By iGameConsole Editorial Team · Canonical product descriptions and all 14 S and 10 MAX configuration prices reviewed October 7, 2026. No named game's options, combined-rule match, settings persistence or multiplayer route was tested for this article.
The 30-second standard-or-configured verdict
You may simply want to choose a familiar mode and start. Or you may enjoy arranging the conditions before playing. Both are valid interests. The purchase should depend on the actual native function you need, not on an assumption that every classic supports unlimited custom matches.
| Your goal | The useful check | What does not establish it |
|---|---|---|
| Start a standard match | The exact mode, relevant controls and ordinary play | A title screen without the wanted activity |
| Change an offered rule | The native option's meaning and application in the intended mode | An option name or a highlighted value alone |
| Combine several options | Whether the supported combination is accepted and actually used | Separate demonstrations of each setting |
| Use the arrangement next time | The supported return or re-entry routine | A campaign save or an unchanged menu during one session |
| Arrange a match with another person | Both native rules and the complete supported participant connection | Two handhelds or a multiplayer label |
The spending rule: verify the essential native configuration and meaningful play first. Then choose S for a suitable compact role or MAX for a wanted larger physical view. Capacity is a separate room decision, not a rules upgrade.
If changing rules is optional, ordinary play can still be the complete reason to own the device. If one rule combination is indispensable, make that a purchase gate. An unknown function is neither a promise nor proof that the game universally lacks it.
1. Define the experience you want to arrange
“Custom matches” can mean selecting an opponent, changing an offered limit, choosing a stage or combining native conditions. Those are not automatically one feature. State the actual change that makes the session appealing.
Ask why you want it. You might prefer a particular competitive structure, enjoy experimenting with supported combinations or want a familiar event without unrelated campaign progression. That reason determines which options matter and which are merely nice extras.
A fixed native mode may already meet the goal. In that case, you do not need a rule editor to make the handheld worthwhile. Conversely, a large game collection does not compensate if the exact title lacks the one arrangement you need.
Use one sentence: “I want this release in this mode with these offered conditions.” This makes the request specific enough to investigate without demanding every imaginable customization. No exhaustive option list or named feature is certified in this guide.
2. Identify the release and mode before the menu
Original versions, ports, regional editions, remakes and modified builds can offer different native settings. A series name is not a specification for match options. Name the title, original platform, edition, language and wanted mode.
Check where the configuration belongs. An exhibition menu, practice setup and continuing campaign can use different rules within the same game. An option available in one should not be advertised as global.
Also identify the starting situation. A fresh profile, continuing record and prepared setup can display different defaults or accessible choices. A demonstration should describe that state instead of implying every new unit starts identically.
Separate availability from package inclusion. Even if a release offers the desired options, that does not prove the selected product includes it or that the actual emulator reproduces the complete task. Those are separate questions, not conclusions from a screen illustration.
A useful brief asks about the exact activity, not “Does it play the franchise?” That small change prevents a genuine game-launch example from answering the wrong purchase question.
3. Keep native rules separate from emulator and device settings
A game-native option belongs to the release's own interface and rules. Emulator mapping, display configuration and device settings operate at other layers. Changing a button assignment does not necessarily change what the game considers a valid event.
Likewise, selecting a new rendering filter does not create an extra native match option. A larger card does not add software rules. The helpful question is which component provides the change and what part of the experience it affects.
Difficulty and assistance deserve their own scope. A native difficulty choice, an emulator convenience and an altered game file can have different purposes and consequences. Do not describe all of them as a standard custom-match feature.
The unfinished-classics guide addresses difficulty, retry cost and assistance. This article focuses on arranging an offered native match and verifying that the conditions actually apply.
No cheat, macro, bypass procedure or universal shortcut is supplied. If the essential change requires another software environment or original accessory, identify that documented route rather than relabeling it as ordinary configuration.
4. Read the actual meaning of each offered option
A short label can hide an important distinction. A value might describe a native count, game-clock setting, limit or predefined category. Do not assign units or effects simply because a number appears.
Read the relevant description and context in the exact language and edition. An English device menu does not establish that all game labels or explanations are English. A bigger physical panel cannot translate an unclear option.
Ask what changes during play. Does the setting affect the next event, the whole mode, one participant or only presentation? That question links the menu to the experience instead of treating navigation as successful configuration.
Where the release offers a default, identify it accurately rather than calling it an optimal or fair setting. Preference, intended native behavior and measured competitive balance are different claims.
No universal option ranges, resource counts or strongest setup are provided here. Clear interpretation of the actual release is more useful than a generic list of settings that might not exist.
5. Check whether the wanted combination is allowed
Options that work separately may not form every combination you imagine. A mode can constrain a choice, reset another setting or require a particular starting condition. Inspect the actual supported arrangement.
Change one meaningful option at a time while learning with disposable play. Review the complete setup before starting rather than assuming earlier selections remain unchanged as you move through the menus.
If a choice becomes unavailable, identify the native reason where documented. Do not assume a hardware fault, extra content requirement or hidden feature merely from its appearance. A grayed entry is an observation, not an explanation.
The essential test is the combined brief. If you need two conditions together, separate successful examples do not certify that combination. Request the relevant setup and resulting ordinary play.
A rule system's limits are software facts. MAX's larger panel and 128GB's nominal room do not make mutually restricted settings compatible.
6. Review and confirm before starting
Moving a highlight, changing a preview and committing a setting can be different operations. Learn the exact release's supported confirmation and cancellation behavior before assuming the next match uses your choice.
Where a summary is offered, use it to check the intended arrangement. Where it is not, follow the actual native routine instead of inventing a universal review screen. The task is a correctly understood setup, not merely a visually busy menu.
Check what happens when you go back to choose a participant or mode. The software may preserve a choice, restore a default or apply another native condition. Observe the relevant behavior rather than assuming all menus share one state.
Use disposable material to understand reset and cancellation. Do not overwrite a valuable profile or alter someone else's setup merely to test an unfamiliar command.
A careful setup does not guarantee that every rule behaves correctly in play. It establishes the intended input to the next stage. Starting and observing the actual match remain separate checks.
7. Follow the settings into meaningful play
A launcher and configuration screen cannot demonstrate an event's complete behavior. Start the actual intended mode with the reviewed arrangement and inspect the rule that matters at a meaningful point.
Match the observation to the condition. If the option concerns how an event ends, opening seconds may be insufficient. If it affects an action or selection, demonstrate that operation rather than relying on unrelated footage.
You do not need an all-game benchmark to make a bounded decision. You need evidence for the requirement that determines the purchase. State which sequence was observed and what remains outside its scope.
Keep a menu label and an achieved result separate. “The selected arrangement begins this demonstrated match” is useful; “every custom match works” claims much more than one example can support.
None of the images here demonstrates a configured match. They illustrate device format, physical controls and gaming interest. No combined-rule task was performed for this guide.
8. Separate game limits from real session duration
A native clock, round count or end condition can shape an event without predicting the complete real time you spend using the device. Menus, interruptions, stoppages and other release-specific behavior remain separate.
If fitting a break is important, ask about the actual full session and stopping routine, not only the displayed value. No universal conversion from a game-clock setting to real elapsed time is supplied.
Likewise, a shorter native event is not automatically easier, more satisfying or appropriate for every buyer. Choose the rule because it serves your desired activity, not because a number appears smaller.
The sports-game guide develops match-versus-season and clock expectations. This article does not create another short-session list; it checks whether an offered native arrangement actually applies.
No matches-per-charge, completion-time or sleep-resume guarantee is inferred. Charging, stopping and saving should follow the actual device and software instructions.
9. Distinguish opponent settings from a connection to another player
A configurable opponent or participant list does not establish human multiplayer. Native player roles, computer-controlled opposition, taking turns and simultaneous shared play are different activities.
If another person is part of the goal, specify the actual arrangement. Same-device input, external controllers, linked handhelds and a connected service require different evidence. Two bought consoles are not a demonstrated route.
Resolve both layers: the native match supports your intended rules and the actual setup supplies the participant connection. A successful solo configuration cannot certify that second chain.
The reviewed S/MAX descriptions do not establish built-in wireless features to rely on for this recommendation. USB-C and visible sticks do not prove original accessory behavior or a supported linked match.
Keep a local solo option useful when it genuinely meets your purpose. If shared play is indispensable, choose a documented complete route rather than treating it as an implied bonus.
10. Determine the scope of the changed rules
A setting can apply to one event, a mode, a profile or another native scope. Identify which situation you need instead of expecting a change to govern the whole game.
Starting a rematch can differ from entering another mode. Changing a participant can differ from starting a new campaign. Check the relevant return situation rather than calling every difference a failure.
A mode may deliberately retain fixed rules while another permits adjustment. That can be appropriate native behavior. The purchase question is whether the adjustable mode serves the activity you want.
For a shared device, respect other people's choices and records. Learn supported profiles or re-entry rather than changing global settings to suit one person without agreement.
No universal rule inheritance, all-mode application or cross-profile synchronization is promised. Native scope belongs to the exact release, not storage capacity.
11. Reusing settings and retaining progress are separate outcomes
You may want the same arrangement next session, or you may be happy entering it each time. Decide which is essential. A repeatable manual routine can be adequate without a saved preset system.
If persistence matters, verify the actual supported method, proper exit and later return. A campaign save does not necessarily retain option values. An unchanged menu during one session does not prove later persistence.
Where a release offers named presets or separate records, check what they contain. Do not infer preset slots, automatic profiles or independent backups from one saved configuration.
Protect valuable permitted data before meaningful changes. Multiple records on the same active medium do not independently protect against loss of that medium. A bigger card does not add automatic recovery.
Never interrupt a save, remove active storage or overwrite the only useful record to test persistence. Use low-stakes material and the actual instructions.
12. Native rules are not a level editor or external creation tool
Changing an offered match option adjusts a function the release provides. Placing objects, designing a stage and testing a new layout are different creative tasks. A settings menu is not automatically a stage editor.
The native level-editor guide follows selection, placement, playtesting, revision and retained creations. This guide does not borrow those capabilities to make ordinary match options sound more powerful.
Likewise, a native arrangement is not automatically an exportable file, downloadable scenario or shareable online lobby. If an external deliverable matters, identify the supported creation, transfer and destination route separately.
Modern custom-match services can resemble classic menus while requiring a different environment. The visual style does not make them classic-console software or a supported S/MAX task.
No stage creator, external editor, preset exchange or current service is certified here. Choose the documented environment for the actual essential function.
13. Match the controls and information to the configuration task
Useful input includes moving through options, making the intended change, confirming it and playing the resulting event. A moving cursor establishes only part of that chain.
Physical controls are an appealing reason to choose a dedicated handheld. Their actual mapping and meaningful game actions still depend on the emulator and setup. A familiar layout does not certify every original input.
Read the text and cues that matter. Small option labels, selected values and event information may be more relevant than the central character artwork. A larger panel cannot explain an unfamiliar rule or change its language.
Both S and MAX list 640×480. MAX offers more physical area, not new source pixels. No universal readability, precision or latency score is supplied.
If a required task depends on original pointer, keyboard, motion input or a modern application, resolve that route first. A connector or extra stick is not the complete answer.
14. R36S can serve a focused compact match role
Review S when a suitable exact classic, essential native options, meaningful input and wanted compact view fit. The device can have a clear purpose without becoming a universal custom-match platform.
The reviewed description identifies NES, SNES, GBA and PS1 as core directions. Those labels do not certify every title or optional mode. N64 and PSP remain title-dependent; resolve a demanding essential release rather than judging from attractive artwork.
S lists 3.5-inch IPS at 640×480, RK3326 and 1GB DDR3L with a Linux-based retro gaming OS (ArkOS community firmware). It is not an Android app direction or a suitable PS2 purchase route.
S64 at $79.99 is the lower entry price. S128 at $89.99 adds nominal room on the same listed platform, not rule controls, preset slots or multiplayer.
Purple, Black, White, Red, Yellow, Green and Blue are listed in both capacities. Choose finish for preference, then check the exact live option's price and availability. Color does not determine native settings.
Use the R36S configuration page after the actual match task fits. An essential unknown should be resolved before storage selection, not hidden behind a default recommendation.
15. Compare MAX for a wanted larger physical view
MAX's 4-inch IPS panel can be a reason to spend more if you prefer that physical format for the actual options and event presentation. It should not be described as providing more native rules.
The reviewed S and MAX records list the same 640×480, RK3326 and 1GB DDR3L. No new combined-setting or performance benchmark establishes a stronger processing tier here.
Inspect the information you actually use, not only a flattering hero image. Preference for more physical viewing area is legitimate without a guarantee that every label is easier to read or every action easier to perform.
MAX64 is $99.99 and MAX128 $109.99 at the checked USD bases. Additional room remains a library decision, not access to a broader rules system.
Black, White, Blue, Gray and Red are listed across both capacities. Confirm the actual selected configuration. No finish-specific performance or settings difference is asserted.
Compare R36MAX when larger physical viewing is the useful difference. Resolve Android, PS2, wireless, modern services and indispensable demanding titles through appropriate documented evidence instead of treating MAX as a universal upgrade.
Hardware facts and native configuration requirements
| Decision point | R36S | R36MAX | Configuration boundary |
|---|---|---|---|
| Display | 3.5-inch IPS; 640×480 | 4-inch IPS; 640×480 | Physical area, not new native choices |
| Chipset and memory | RK3326; 1GB DDR3L | RK3326; 1GB DDR3L | No measured configured-match advantage established |
| System | Linux-based retro gaming OS (ArkOS community firmware) | Linux-based retro gaming OS (ArkOS community firmware) | Actual build, menus and mappings can vary |
| Storage | 64GB / 128GB | 64GB / 128GB | Nominal room, not presets or automatic protection |
| Controls | D-pad, face and shoulder controls, analog input listed | D-pad, face and shoulder controls, analog input listed | Actual meaningful input needs matching evidence |
| Connections | USB-C, 3.5mm audio, MicroSD listed | USB-C, 3.5mm audio, MicroSD listed | No automatic original-input or shared-play route |
| Named native rule combinations | Not certified here | Not certified here | Resolve indispensable exact-release conditions |
| Supplied games and extras | Not established by these images | Not established by these images | Confirm the actual selected package |
These listing facts do not supply a battery comparison, match-duration estimate, supplied library audit or all-game guarantee. They remain useful precisely because they are not used to fill unknown software behavior.
For another model, inspect its own current identity and documented route. Price, shell layout and a broad platform label are not substitutes for the essential configuration task.
16. Four configurations and real reasons to spend
Choose physical format and nominal room separately after the native match fits. This avoids treating the highest price as the most complete set of game rules.
| Configuration | Price | Reason to consider it | Not a promised benefit |
|---|---|---|---|
| R36S 64GB | $79.99 | Lower entry price for suitable compact classic play | Every native combination supported |
| R36S 128GB | $89.99 | More nominal library room | New rules, presets or automatic backups |
| R36MAX 64GB | $99.99 | Wanted larger physical view | More source pixels or stronger listed processing |
| R36MAX 128GB | $109.99 | Larger view plus additional nominal room | A modern custom-match service or linked play |
At these bases, capacity adds $10 within either model; MAX adds $20 at matched capacity. S128 and MAX64 are $10 apart, trading nominal room against physical view rather than rule-making capability.
More games can create more choices across releases. They do not expand the options inside one title. Usable space and actual software depend on the supplied arrangement.
Check the live selected option for current pricing and availability, then applicable order details. Do not infer accessories, destination totals or delivery deadlines from this comparison.
If an indispensable rule remains unverified, spending more does not resolve it. Establish the native function first; choose the real hardware benefit second.
Buy the match experience, not an imagined menu of features.
For suitable compact classic play with an understood native configure-to-play route, review S. Compare MAX when its larger physical view is a benefit you want. Choose room only after the essential task fits.
Review R36S configurationsCompare R36MAX viewing options
These links open product choices. They do not select a variant, certify a rule combination or add an item to your cart.
17. Everyday experiments, travel and gifts
The local experimenter
You enjoy a familiar game while changing one supported condition to see how the session feels. Keep the actual native scope clear and change one meaningful choice at a time. No improved skill, motivation or balance result is guaranteed.
The player who wants a consistent routine
You prefer one arrangement and want to return to it. Verify persistence or a simple supported re-entry path. A saved preset is not essential if manual setup genuinely suits you, but it should not be promised without evidence.
A trip with a few familiar games
Before leaving, check the actual release, controls, intended arrangement and stopping method. Follow device instructions and use an appropriate carrying setup. A small format is not proof of pocket fit, a whole-trip charge or identical resume behavior.
A gift for a particular playing preference
Ask whether the recipient wants standard play, native adjustment, creation or shared competition. Those can lead to different requirements. Do not assume a familiar image or large-capacity option supplies the experience.
Confirm essential contents and the applicable order information. Respect existing profiles and valuable records rather than replacing them to create a preferred demonstration or gift setup.
18. Request the combined task and validate safely
A useful example identifies the release, mode and starting state, changes the actual supported options, reviews the combination and begins meaningful play. It observes the rule that determines your purchase rather than stopping at a settings page.
If reuse matters, include the supported exit and return. If shared play matters, request the separate connection route. This keeps the evidence bounded while covering the parts that make the experience worthwhile.
A copyable purchase question
“I want [exact title, platform, edition and mode] with [these native options together]. Please identify what the choices mean, their applicable scope and any dependency. Show supported selection and confirmation, start the actual match and demonstrate the relevant rule in action. Explain next-match and later-session behavior separately. I do not mean emulator assistance, a level editor or multiplayer unless I specify that.”
On receipt, match the configuration and read the actual instructions. Use low-stakes play to check navigation, confirmation, meaningful actions and return behavior. Do not alter several unrelated software settings to diagnose one unclear native option.
Protect valuable permitted records before meaningful changes. Never interrupt saving, remove active storage or overwrite the only useful profile to test a reset. A bounded success supports your routine, not every possible combination.
If something differs, describe the stage: option absent, choice canceled, combination changed, rule not observed, or later settings not retained. That report is more useful than a universal statement that the handheld cannot configure matches.
Three clear purchase routes and the non-fit boundary
The standard-mode player
You want familiar ordinary play without a setup project. Confirm the exact mode and meaningful task. S can fit the compact role; MAX is a wanted larger physical-view comparison. Native customization need not become an artificial requirement.
The native-options player
One offered arrangement matters. Verify its meaning, allowed combination, actual application and required return behavior. Choose hardware for a documented physical benefit, not more imagined settings.
The dependency-led player
You require a modern lobby, original input, external creator or actual shared connection. Resolve that environment first. Neither S nor MAX is certified for those routes by this article.
If the essential feature is unknown, this guide does not recommend buying on hope. Unknown is not universal absence, but it is not a purchase promise. A higher price or capacity cannot close the evidence gap.
A worked decision without an invented match test
Suppose a buyer wants a familiar classic with two particular native conditions. Identify the exact release and mode, then confirm that both options exist there, what they mean and whether the combined setup is supported.
Review the arrangement, start the actual event and observe the meaningful effects. If it fits, compare compact S with larger-view MAX. Capacity remains a library-room decision, not a way to add either condition.
If one condition instead belongs to a later edition or a modern service, resolve that route. If ordinary standard play would be equally enjoyable, keep the custom combination optional rather than inflating the purchase brief.
This hypothetical example explains the method. It is not a named game's option audit, benchmark, balance study or successful configured match.
Seven steps to choose a handheld for native match options
Identify the actual offered rules, verify meaningful configuration and play, then choose a suitable physical format and nominal storage option.
-
Define the desired match.
State whether standard play is enough or an exact native arrangement is essential. Separate preferences from purchase gates.
-
Identify the release and mode.
Name title, platform, edition, language and relevant starting state. Do not borrow another version's options.
-
Understand scope and combinations.
Check option meanings, dependencies and the actual supported combination. Separate native rules from emulator or device settings.
-
Confirm and observe meaningful play.
Follow the supported selection and confirmation routine into the event and check the rule that matters.
-
Resolve reuse and participant needs.
Verify next-match or later-session behavior where essential. Check any actual shared-play connection independently.
-
Choose a real hardware benefit.
Review S for suitable compact classic play or MAX for a wanted larger physical view. Choose capacity for useful nominal room.
-
Validate without risking valuable data.
Use low-stakes play and actual instructions, preserve useful permitted records and avoid destructive reset or save tests.
Native match-options handheld buying FAQ
How should I choose a handheld for native match options?
Identify the exact release, mode and wanted native arrangement. Check option meanings, allowed combinations, actual application and essential reuse behavior before choosing the physical format and capacity.
Does every classic game support fully custom matches?
No universal customization system is established here. The exact release determines what can be selected and in which mode. Standard play may already meet your goal.
Are game-native rules the same as emulator settings?
No. Native game options, emulator mappings, display settings and device configuration operate at different layers. Identify which component provides the wanted change.
Does a changed menu value prove the rule is active?
No. Preview, confirmation and meaningful play are separate stages. Start the intended event and observe the relevant native effect under the actual supported configuration.
Do separately available settings guarantee every combination?
No. Modes and dependencies can constrain combinations. Verify the actual arrangement you need instead of combining unrelated demonstrations into a universal promise.
Does a match clock predict the whole session length?
No universal conversion is supplied. Native clocks, end conditions, menus and stopping routines can affect different parts of the activity. Check the actual full session if timing is essential.
Does configuring participants prove multiplayer works?
No. Native participant choices and the actual human connection are separate requirements. Two handhelds, USB-C or a multiplayer label do not establish a complete supported route.
Does saving a campaign retain every match option?
Not necessarily. Check the actual scope and supported return routine. Re-entering an arrangement may be adequate, but saved presets or global persistence should not be promised without evidence.
Does 128GB add rules, presets or independent protection?
Capacity provides nominal room, not new native options, preset systems or automatic backups. Protect valuable permitted data through an appropriate separate supported process.
Does MAX add configuration features or stronger processing?
Its documented difference here is a 4-inch rather than 3.5-inch physical view. Both list 640×480, RK3326 and 1GB DDR3L. No new native choices or measured configured-match advantage is established.
Are named rules tested and firmware instructions identical?
No named configured match was tested here. Both products describe a Linux-based retro gaming OS (ArkOS community firmware); builds can vary by batch, update or re-flashing. Follow the actual delivered setup and verify indispensable tasks.
What prices and final buying rule are used?
October 7 USD base references are S64 $79.99, S128 $89.99, MAX64 $99.99 and MAX128 $109.99. Verify the actual native match first, choose the wanted physical format second and useful nominal room third. Check live selected options and applicable order details.
Follow the guide for the remaining requirement
For matches, seasons and actual versus expectations, read the sports-game buying guide. For difficulty and assistance, use the unfinished-classics guide. For making stages rather than configuring rules, use the native level-editor guide.
Once the wanted native task fits, compare compact R36S and larger-view R36MAX. The next link should answer the next real question, not substitute product repetition for a useful decision.
Arrange the play you want, then choose the device.
A familiar classic can be enjoyable as it is. Its actual native options can also offer a different session when those choices are part of the release. The right purchase keeps that interest connected to an understood, supported task.
Choose S for suitable compact classic play or compare MAX for a wanted larger physical view. Do not pay for capacity expecting it to rewrite native rules, add modern services or establish a shared connection.
Evidence and editorial scope
This guide uses canonical S/MAX descriptions and complete configuration prices read October 7, 2026. Hardware facts, game-native options, software configuration, package contents and observed behavior remain separate evidence categories. Product titles and historical library figures are not used as rule certification.
Existing sports, unfinished-classics and native level-editor bodies were reviewed to distinguish configured-match application from clock expectations, difficulty assistance and stage creation. This does not establish an exhaustive whole-store content audit or measured search demand.
Five existing Shopify-hosted images were visually inspected in this conversation. Whole-device artwork, actual controls, in-hand format and desk context illustrate the purchase setting, not tested rule combinations or supplied games. No new generation or cleanup was performed. Native game text and hardware markings remain intact.
No option-range audit, combined-rule event, preset persistence, multiplayer route, input benchmark or external creation service was tested. Resolve essential unknowns with matching evidence; do not turn them into promises or claims of universal absence.
Final buying rule: choose the native arrangement you want, verify that it actually governs the match, then choose the handheld.
