Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

More clear documentation on how to change models

Closed
#1,096 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
tex
Domain
documentation

Research direction

Start with the existing documentation section that mentions the Model core option, file path tags, and .uae files. Compare these methods for selecting an A1200 instead of the default A500, then document a working example and explain whether the setup can be used by a Lutris installer.

Written by the indexing model from the issue text.

Description

The documentation is sparse when it comes to how to change the model (say, the A1200 instead of the default A500 for an Amiga ROM) for the same core. It explains that it can be done either by the "Model" core option or by file path tags but neither method is fully explained. It also says:
You can pass .uae configuration files and they will be appended to the core option configuration.

I have scoured this a dozen times and searched the Internet ten ways from Sunday but have gotten no closer to understanding exactly how to implement one of these methods (or indeed, which one is best in this case). An example of this being done would help, especially since I'm also trying to figure out if this can be set using a Lutris installer. (This is such a specialized question that I'm not sure any of the Lutris folks know the answer - and I suspect that I need to understand how it normally works first before I can figure out if it can be done with Lutris.) If this is a really obvious thing and I'm just being really obtuse about it, I apologize - but I've been bashing my head against this for hours with no success.

Dominant language
TeX
Stars
348
Forks
864
Avg merge
4d 5h
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libretro/docs

All issues in libretro/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.