GAME-DRIVEN SELECTION · 2026
Choose for what happens during combat, not just the letters RPG.
For turn-based and action RPGs, choose a retro handheld around the exact release, the information you must read, the actions you must perform, and what happens while you make a decision. Deliberate command selection, timed menus and real-time movement create different buying checks. None of those labels alone proves compatibility, easy stopping or a need for the most expensive device.
For a suitable compact classic-game setup, start with R36S, currently $79.99 for 64GB or $89.99 for 128GB. Compare R36MAX when a larger physical view matters, from $99.99 for 64GB. Compare R36H when you specifically prefer its horizontal layout, from $89.99 for 64GB.
These are conditional routes, not a claim that every RPG is installed or fully tested. A larger screen does not make combat faster. A horizontal body does not certify lower latency. A turn-based game does not automatically pause or save wherever you want.
The 30-second combat-style verdict
Choose the game and behavior first, then the view, body and capacity. Your combat preference should tell you what to inspect, not force a universal model ranking.
| Your preferred experience | What changes the buying decision | Conditional product direction |
|---|---|---|
| Deliberate command choices. | Readable options, clear targets, suitable mapping and actual stopping rules. | R36S when its compact view and layout suit; MAX when you want the larger physical view. |
| Menus while a battle clock may advance. | The exact release, mode, timer behavior and transitions between reading and action. | Choose only after the required behavior is established, not from a turn-based label. |
| Real-time movement and combat. | Required inputs, action visibility, menu transitions and your preferred physical layout. | R36S as a compact candidate; R36H if horizontal arrangement is genuinely preferred. |
| Long story sessions. | Language, dialogue, menus and a tested progress routine. | Compare useful viewing size after the release fits. |
| Interrupted play. | A supported pause or stopping method and a reliable later load. | No shape or genre alone establishes the solution. |
| A remake, touch-based release or demanding later platform. | That distinct software and input requirement. | Find appropriate documented hardware rather than extending a classic-game recommendation. |
The right device is the one that supports the way you want to play. The right evidence is the evidence for the actions and information that matter to you.
1. Describe your combat preference as a task
You may like studying a command list, choosing an ability and watching the result. You may prefer moving and reacting directly. Or you may enjoy a mix: decisions in menus, with a battle clock or timed input still shaping the action.
Translate that preference into a task. “I need to read these options before choosing a target.” “I need to move and trigger these actions reliably.” “I want to open the item menu without assuming the battle stops.” These are specific questions a demonstration can address.
Do not begin by declaring that all action RPGs need advanced hardware or that all command-driven games are simple to run. The original platform, exact release, emulator, settings and controls still determine the hardware requirement.
A useful first sentence is: “I want this release mainly for this combat experience, and this is the part that would make the handheld unsuitable.” That identifies the essential condition before you compare a storage number or a price.
2. Separate deliberate commands, timed menus and real-time action
These are practical buying categories, not rigid labels for every game. A release can combine them, and the important behavior may change from one part of the game to another.
| Combat behavior | What the player is doing | What to verify |
|---|---|---|
| Deliberate command selection. | Reading choices and selecting an action or target. | Actual decision timing, text, cursor movement, confirmation and cancellation. |
| Timed command selection. | Using menus while time or a meter may affect battle. | What continues, what waits and which options or modes change the behavior. |
| Real-time movement and attacks. | Positioning, reacting and using mapped actions. | The actual input scheme, meaningful gameplay and visibility of cues. |
| Mixed or context-dependent behavior. | Moving between reading, commands, timing and direct action. | The transitions, not just one convenient part of the demonstration. |
A menu on screen does not prove unlimited thinking time. An action sequence does not mean the entire game uses the same input. A turn-based label does not rule out timed elements elsewhere in a release.
Use the categories to choose your evidence request. Do not use them as substitutes for identifying the actual game.
3. The exact release comes before the combat label
A familiar series can include original releases, remakes, ports and later games with different systems and hardware requirements. The game you remember may not be the version in a modern video or on another platform.
Record the full title, original platform, edition and language that matter to you. If an optional battle mode or menu behavior is important, name it. A title string or franchise image is not enough to establish all of those.
Do not assume that a classic release and a modern remake have the same combat, controls or hardware needs. Do not assume that a regional edition or translation behaves identically to another version in every relevant detail.
The English-language edition checklist helps when the text changes the purchase. Language and edition are part of the software requirement, not features created by a larger screen.
Release-first rule: establish the game and version you will actually play. Only then can a command, timing or action demonstration answer your buying question.
4. Command-driven play still needs clear inputs
Taking time over a decision does not remove the need for understandable controls. You still need to move through commands, choose a target, distinguish confirmation from cancellation and recognize what the game accepted.
Check the displayed button prompts against the actual mapping. A familiar letter on a handheld shell is not proof that every game uses it for the same action. Different releases and emulator arrangements can map commands differently.
Observe a meaningful sequence rather than a static menu: open the relevant options, choose an action, select a target, cancel when appropriate and return to ordinary play. This shows more of the task than watching a battle animation alone.
Choose a physical layout you want to use repeatedly. R36S can be a sensible compact candidate when the release and arrangement fit. R36MAX may be worth comparing for a larger physical view of the information. Neither choice needs an invented timing score to be useful.
6. For real-time combat, observe the actions you actually use
Real-time combat makes the relationship between movement, buttons and on-screen events important. The useful buying question is whether you can perform the required actions on the selected configuration.
Choose a representative task: move, use a relevant action, change a selection if the game requires it, and return from a menu. Do not substitute a title screen or an unrelated easy scene for the activity that motivated the purchase.
A visible response shows that the shown action occurred. It does not quantify input-to-display latency, prove every combination or establish that one model is faster than another. Those claims require an appropriate measured method.
You may prefer a particular control arrangement without claiming it is universally superior. Choose for your actual grip and task, then keep the observed result within its scope.
7. The transition between action and menus can decide the purchase
A game may feel comfortable during movement but awkward when you switch to items, abilities or party commands. Another may offer readable menus while a battle clock creates a different pressure. Assess the whole interaction you intend to use.
Ask to see the meaningful transition: ordinary play, menu entry, selection, any target or confirmation step, and return. Check what continues during that sequence and whether the mapped controls remain clear.
Do not assume the same pause behavior for every menu or mode. Do not assume a button shortcut removes all timing pressure. If a specific interruption method or wait behavior is essential, make it a separate confirmation point.
A good demonstration answers the task you asked about. It does not need to show every route or boss, but it should not claim those unobserved parts as completed tests.
8. Reading under pressure is different from reading at leisure
A dialogue box during exploration and a command menu during a timed battle can impose different demands. Check the information you need at the moment you need it, not only a pleasant story screenshot.
Look for command names, target markers, resource information, status indicators and any cues that determine your next action. The actual font, layout, scaling and viewing distance matter. A screen diagonal alone cannot certify readability for every player.
If you want to compare the larger R36MAX view, use the actual release presentation. Its listed 4-inch panel is physically larger than the R36S's 3.5-inch panel, but both are listed at 640×480. The size difference does not guarantee larger in-game fonts or changed menu design.
The JRPG screen, text and saving guide gives the focused viewing comparison. Here, the added question is whether that information must be read while the game is still asking you to act.
9. Choose R36MAX for a wanted physical view, not automatic combat superiority
R36MAX is the larger-view direction in this guide. Consider it when that physical format is something you want to use for the suitable release, whether the important content is dialogue, menus or visible action.
Its current USD base options are 64GB at $99.99 and 128GB at $109.99. The storage difference is additional nominal capacity, not a faster battle system.
Do not call the bigger screen a compatibility upgrade, a low-latency feature or a medical accessibility guarantee. Compare the actual presentation and your own needs.
If the compact R36S view already works for you, extra spending should solve a named requirement. If it does not, the lower price alone is not a reason to force the smaller format.
10. A visible pair of sticks is not a universal RPG requirement
The original input scheme matters more than the number of sticks in a product photo. Some classic releases rely primarily on directional and button input; another release may need a different controller mode or action.
Identify the native controls and the emulator's mapping, then observe the required behavior. Do not assume that two sticks add a camera scheme to a game that did not originally have it. Do not assume an action-RPG label requires dual analog input.
Likewise, do not infer sensor technology, trigger behavior, precision or latency from the layout. The linked descriptions establish physical-control direction, not every input characteristic a buyer might imagine.
The control-first buying guide explains the full chain from original input to observed action. Use it when a particular controller requirement determines the purchase.
11. R36H is a horizontal-layout option, not a measured action upgrade
R36H adds a different physical arrangement to this comparison: a horizontal landscape body with a listed 3.5-inch IPS display at 640×480. Consider it when you genuinely want that relationship between the screen and controls.
Its current USD base configurations are 64GB at $89.99 and 128GB at $99.99. The complete sixteen-variant connection was read for this guide, covering eight colors and both capacities.
The listing names RK3326 and 1GB DDR3L, the same listed hardware platform as the other two models. That is not a measured latency comparison. The horizontal shell does not certify more accurate movement, easier combinations or comfort for every person.
Choose the arrangement because you prefer using it, not because a genre label assigns action games to one body. A command-driven RPG can also be played in a horizontal format when its actual configuration fits.
12. Current model and capacity choices
These are USD base configuration prices checked against the current store records on October 3, 2026. They are not a stock count, destination-specific total or proof of a supplied RPG library.
| Configuration | Current USD base price | Listed physical direction | Reason to compare it |
|---|---|---|---|
| R36S 64GB | $79.99 | Compact vertical, 3.5-inch IPS. | Lower-priced compact candidate when the required release and setup fit. |
| R36S 128GB | $89.99 | Same listed R36S physical format. | Additional nominal storage capacity. |
| R36H 64GB | $89.99 | Horizontal, 3.5-inch IPS. | A wanted horizontal screen-and-control arrangement. |
| R36H 128GB | $99.99 | Same listed R36H physical format. | Horizontal preference plus additional nominal room. |
| R36MAX 64GB | $99.99 | Vertical, 4-inch IPS. | A wanted larger physical view. |
| R36MAX 128GB | $109.99 | Same listed MAX physical format. | The larger view plus additional nominal room. |
All three descriptions identify Linux-based retro gaming with ArkOS community firmware, listed RK3326 hardware, 1GB DDR3L and 640×480 panels. Those facts do not establish identical results in every build or a combat-performance advantage for a particular body.
Match the actual live color and capacity, current market price and checkout. Do not inherit an accessory list, named game or timing promise from another independent offer.
13. At the same price, ask what you want to change
At the reviewed $89.99 USD base price, R36S 128GB and R36H 64GB offer a different trade: extra nominal storage on the compact vertical model versus the horizontal arrangement with lower listed capacity.
At $99.99, R36H 128GB and R36MAX 64GB offer another trade: the horizontal model with additional room versus the larger physical view with the lower capacity.
Neither comparison has a universal winner. If your main complaint is the arrangement of the controls, storage is not the same solution. If your main preference is a larger physical view, a bigger card does not provide it. If your view and body already suit you, useful capacity may be the relevant difference.
Use the combat requirement to decide which column matters. Do not let equal prices make you assume equal purpose, or let a larger number become a performance score.
14. More storage does not change the battle rules
A 128GB label adds nominal storage capacity relative to 64GB. It does not make a battle clock wait, improve reaction timing, add a controller mode or turn a modern remake into a supported classic release.
It also does not establish card quality, a named-game inventory or a safer save routine. The actual supplied files and software arrangement need their own confirmation when essential.
Choose extra room if you will use it for a lawfully managed library and the selected package is clear. Keep the main game requirement separate. A few suitable adventures with a understood setup can serve your routine better than an unexamined large count.
If a required function is unresolved, do not buy a larger card hoping it fills the gap. Ask about the software and behavior that actually determine the purchase.
15. Decision time is not the same as a safe stopping point
A game can let you think about a command without letting you save the session there. A long battle can remain long even if individual choices are not timed. An action sequence can have a usable pause method without guaranteeing permanent progress.
Identify the actual stopping rules. What can be saved normally? What happens when you pause? Is there a supported temporary suspend or emulator-state route, and has the relevant behavior been checked on the selected setup?
Do not assume a universal shortcut or that every state is compatible after a software change. Check a later load with low-stakes progress before depending on the routine. Normal saves, emulator states and a suspended application are different mechanisms.
The short-session guide addresses the broader start-and-stop requirement. The combat-specific point is that time to choose an action and the ability to preserve a session are separate buying facts.
16. Returning to the adventure matters as much as starting a battle
A long adventure earns its place when you can return to it confidently. You may need to remember the objective, understand the selected release and know which save method you used.
Keep a useful progress routine rather than assuming the device protects every campaign automatically. Before changing software or storage, preserve your own data appropriately and follow the applicable instructions.
The exact firmware can vary by batch and can be updated or re-flashed. Do not assume one old menu screenshot describes every unit's save or resume behavior.
This is not a promise that a handheld makes every campaign easy to finish. It is a reason to check the part of ownership you will repeat across many sessions.
17. Fast-forward is not a substitute for combat fit
You may want to accelerate a familiar repetitive section, but that requirement is different from wanting readable choices or manageable timing. A feature that speeds one animation can also change how quickly input, text or events need attention.
Do not assume an RPG label proves useful fast-forward or that a larger screen produces more speed. Do not promise a multiplier, shortened campaign or easier boss result without relevant evidence.
If acceleration is essential, specify the exact release and sequence. Check ordinary play and the proposed faster mode separately, including controls, reading and the return to normal behavior.
The JRPG fast-forward buying checklist is the focused next step. This article chooses by combat interaction, not by an imagined time saving.
18. Tactical maps add another information task
If the RPG you want involves a grid, unit ranges or detailed map decisions, its needs may extend beyond a command menu. Recognizing the relevant information before a move can matter as much as the action animation.
Identify the map, unit statistics and selection controls you need to use. A turn-based label is not a certification that the map is readable on every screen or that a battle can be interrupted at any moment.
The tactical-game buying guide handles that distinct map-and-menu question. Use the combat framework here to identify timing and inputs, then follow the more specific information requirement where needed.
Keep the duties separate rather than making every RPG article repeat the entire tactical checklist. The next guide should resolve the next real question.
19. A familiar RPG series does not define modern hardware requirements
An original-era release, a later port, a remake and a named application can be different software tasks. A recognized character or title does not make all of them suitable for the same Linux-based handheld.
If touch input, a special peripheral, a modern platform or an app is essential, verify that requirement directly. Do not assume ordinary physical controls can replace every original interaction, or that price alone certifies the needed platform.
R36S, R36MAX and R36H are considered here for appropriate classic-game directions. Do not choose them as universal Android, PS2 or modern-console substitutes. N64 and PSP references remain title-dependent rather than all-library guarantees.
Compatibility, actual inclusion and lawful access are separate questions. A launchable file does not establish the entire playthrough, and a pictured battle does not establish that the release is supplied.
20. If you remember co-op, name the second-player requirement
An action-RPG memory may include another person sharing the adventure. That adds a separate requirement to the game and combat-style decision.
Ask how the desired mode would actually work on the selected setup. A game that originally offered multiplayer does not establish a supported handheld connection or second-controller route. Two devices do not automatically create netplay.
The current descriptions do not establish built-in Wi-Fi or Bluetooth as a feature to rely on for these recommendations. A USB-C connector alone does not certify the needed accessory or display workflow.
If shared play is the reason for the purchase, verify the complete route before choosing. A solo demonstration can be useful for solo play without answering the co-op question.
21. Three combat preferences, three sensible priorities
You enjoy deliberate choices and story reading
Begin with the exact edition, readable commands and normal progress routine. R36S is the compact starting candidate when the view and layout suit. Consider MAX for a wanted larger physical presentation. Do not assume that every command-driven game is automatically easy to stop.
You enjoy menus with time still relevant
Identify the actual battle mode, waiting behavior and transition into target or item selection. Assess what you must read under those conditions. A bigger panel can be a personal viewing choice, but it does not change the game's clock.
You enjoy direct movement and actions
Observe the native inputs and relevant play on the selected configuration. Compare R36S's compact role and R36H's horizontal arrangement as physical preferences, not measured latency tiers. Choose only after the required release fits.
Preference rule: let your play style identify the checks. Let actual product facts and observed behavior support the recommendation.
22. For a gift, ask how the recipient likes to play
A recipient who loves RPGs may enjoy deliberate decisions, active combat, story reading or a particular mixture. A large library number does not tell you which experience they want.
Ask about the favorite release and the part they value. Find out whether a compact device, a larger view or a horizontal arrangement would be welcome. If they already own a handheld, identify the missing role rather than buying a duplicate by genre alone.
For a nontechnical recipient, arrange a clear handover of the selected setup: important controls, the actual save method, normal stopping instructions and who helps with changes. Do not promise zero preparation or universal instant resume.
Color can be a thoughtful preference, but it does not change combat behavior. Confirm essential package items and current purchase terms before ordering, especially if timing or an accessory determines whether the gift will be usable.
23. Ask for a demonstration that matches the battle task
A useful clip identifies the model, software and release, then shows the interaction you asked about. A cinematic, montage or title screen can look impressive while leaving the purchase-defining task untested.
| Requirement | Relevant evidence | Conclusion to keep limited |
|---|---|---|
| Reading commands. | Actual options, markers and selections at the intended presentation. | Observed interface, not universal readability. |
| Waiting while choosing. | Identified mode and what continues through the menu sequence. | That context, not every menu or battle. |
| Performing actions. | Native mapping and meaningful movement or combinations. | Shown actions, not measured latency or every move. |
| Returning after an interruption. | Applicable save, exit and later-load sequence. | That routine, not impossible-to-lose progress. |
| Shared play. | The actual second-player route and intended mode. | That connection, not automatic multiplayer from two units. |
The gameplay-video evidence guide explains how to interpret these observations. A demonstration can support a useful limited answer without becoming an all-routes test certificate.
24. A copyable combat-style question before purchase
I am considering this model and configuration for this exact RPG release and language. I care most about these commands or actions, and this is what I need to read while deciding. Please identify the relevant mapping, battle or wait behavior, and supported stopping routine. What has been observed on this setup, what is actually supplied, and what remains untested?
For real-time play, add the particular input or transition that matters. For command-driven play, add the menu, target or timed decision. For a gift, add the recipient's physical-view and setup needs.
If the answer depends on a feature that is not established, do not fill the gap with a bigger card, a preferred shell or a genre label. Resolve the question or compare another documented fit.
Evidence stop rule: keep the essential requirement visible. A clear conditional recommendation is stronger than a universal promise about every RPG.
25. Confirm what you receive, then begin with a low-stakes check
Match the selected color and capacity to the actual offer. Confirm essential accessories, supplied content and instructions rather than reading them out of a picture.
For first use, identify the release and mapping, check the meaningful combat task and use the applicable progress routine with low-stakes data. Do not test an unfamiliar shortcut on an irreplaceable campaign.
Follow the selected unit's instructions for charging, storage and shutdown. No fixed runtime, universal power supply or guaranteed charge time is established by the combat preference.
A successful first session answers the task you check. It does not prove every future battle, route or software change. Keep useful observations and limitations together.
26. Seven steps to choose for your RPG combat style
Use this buying checklist to connect the exact release, combat interaction and physical preference with an appropriate handheld configuration.
- Identify the exact RPG release. Record title, platform, edition and language. Separate original releases from remakes, ports and applications with different requirements.
- Describe the combat interaction you want. Distinguish deliberate commands, timed menus, direct action and transitions between them. Name the task that would make the purchase unsuitable.
- Check the information and timing. Identify what must be read and what continues while you decide. Do not assume that a menu, turn-based label or optional mode pauses every relevant event.
- Verify native inputs and actual mapping. Observe the required actions, selections and menu transitions on the selected setup. Visible sticks or shell shape do not certify controller behavior or latency.
- Establish the stopping and later-load routine. Check the release's actual save and interruption methods with low-stakes progress. Keep normal saves, emulator states and suspend behavior separate.
- Choose the real physical and storage benefit. Consider R36S for a suitable compact role, R36MAX for a wanted larger physical view or R36H for a genuine horizontal-layout preference. Choose capacity for nominal storage room.
- Confirm the selected offer or resolve the gap. Check actual price, color, capacity, supplied content and essential features. If a purchase-defining behavior remains unverified, ask for evidence or keep comparing rather than forcing a universal recommendation.
The result should explain why the selected device fits your way of playing. A combat label is the starting question, not the whole answer.
RPG combat-style handheld buyer FAQ
Should I choose different handhelds for turn-based and action RPGs?
Not automatically. Use the combat style to identify reading, timing, input and interruption requirements, then verify the exact release and configuration. R36S is a compact candidate for suitable classics, MAX a larger-view option and H a horizontal-layout option. None is assigned a universal genre-performance ranking.
Do all turn-based RPGs let me stop safely anywhere?
No. Time to choose an action is different from a save or supported stopping point. Check the actual release's pause, normal save and any temporary-return behavior. A genre label does not guarantee mid-battle saving, instant resume or progress that cannot be lost.
Does opening a command menu always stop the battle clock?
No universal result can be assumed. Some releases or modes keep time relevant during selections, and wait behavior can be context-dependent. Identify the exact release and setting, then observe the menu and target-selection sequence you intend to use.
Do action RPGs always need two analog sticks?
No. The native input scheme and actual mapping determine the need. An action label does not add camera control or dual-analog requirements to an original game. Verify the relevant inputs and actions instead of choosing by a visible stick count.
Is R36H proven better for action combat?
No measured action, precision or latency advantage is established here. R36H is considered for its horizontal physical arrangement. Choose it when that layout is wanted and the required release fits, not because the shell certifies better performance.
Does R36MAX make RPG menus or combat faster?
A larger physical screen does not establish faster emulation or changed battle rules. R36MAX lists a 4-inch IPS display, while R36S and R36H list 3.5-inch displays. All three list 640×480, RK3326 and 1GB DDR3L. Choose the view as a physical preference and verify actual behavior separately.
What are the current prices used in this comparison?
The reviewed USD base prices are R36S 64GB $79.99 and 128GB $89.99, R36H 64GB $89.99 and 128GB $99.99, and R36MAX 64GB $99.99 and 128GB $109.99. These are configuration references checked on October 3, 2026, not complete destination-specific checkout totals or stock guarantees.
Does 128GB improve RPG timing or add a wait mode?
No such behavior follows from nominal capacity. More storage does not upgrade the processor, change the original combat rules or establish a particular feature. Choose it for useful room in the supplied arrangement, and verify essential software behavior separately.
Will all my favorite RPGs be installed and fully tested?
This guide makes no all-library or named-game inclusion promise. Confirm the exact release, language, supplied configuration and relevant evidence. A game count or illustrated battle is not a manifest, license or complete playthrough test.
Can I rely on the same ArkOS shortcuts on every unit?
No universal shortcut is promised. All three listings describe a Linux-based retro gaming OS with ArkOS community firmware. Exact firmware can vary by batch and can be updated or re-flashed, so menus, mappings and save routines may differ. Use the actual configuration's instructions.
Does an original co-op RPG guarantee handheld multiplayer?
No. Verify the desired mode and actual supported second-player route. Two handhelds do not automatically establish netplay, and a connector or original multiplayer feature does not certify the complete accessory or connection workflow. A solo demonstration answers a different question.
What should I ask before choosing a handheld for one RPG?
Specify the exact release and language, the information you must read, the actions and timing you care about, and the stopping method you need. Ask what was observed on the selected setup and what remains untested. If an essential condition is unresolved, seek evidence or keep comparing.
Follow the next requirement with the right guide
- JRPG screen, text and saving for the physical reading and campaign question.
- Tactical maps and menus for grid and unit information.
- Control-first selection for native inputs and actual mapping.
- English-language editions for identifying the release you can read.
- JRPG fast-forward checks when acceleration is a separate must-have.
- Gameplay-video evidence for interpreting what a demonstration supports.
- Short-session selection for a realistic interruption routine.
The guides have different jobs. Connect them where the next question genuinely changes the purchase, rather than repeating a general sales claim.
Choose the adventure, then the interaction you want
Start with R36S for a suitable compact classic-game role. Compare 64GB at $79.99 and 128GB at $89.99 after the release, controls and setup fit.
Choose a real physical difference when it matters. Compare R36MAX at $99.99 for 64GB or $109.99 for 128GB for the larger view. Compare R36H at $89.99 for 64GB or $99.99 for 128GB for a wanted horizontal arrangement.
No genre, screen or body shape makes every RPG perfect. A good recommendation explains how the confirmed release and physical role fit the way you want to play.
Review R36S optionsCompare the larger viewCompare the horizontal layoutEvidence and scope
This is a combat-style buying framework, not a newly measured performance review. Current canonical descriptions and complete variant choices provide the hardware, physical-format and price references checked on October 3, 2026. They do not establish a test of every RPG, battle mode, latency result or progress feature.
Store illustrations were reviewed for visible layout and ALT descriptions. They do not prove current-batch measurements, installed games, native controller behavior or complete package contents. No invented scores, full-series percentages, playthrough hours, fixed runtime, reviews, stock or policy promises are used to justify the recommendation.
