libretro / libretro/RetroArch

[Feature-Request]Continuously scan dir/scan dir on boot/ scan dir excluding folder

Open
#12,904 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

First and foremost consider this:

#- Only RetroArch bugs should be filed here. Not core bugs or game bugs
#- This is not a forum or a help section, this is strictly developer oriented

Description

[Description of the bug]

Expected behavior

[What you expected to happen]

Continuously scan dir/scan dir on boot/ scan dir excluding folder.
Is there anyway to have Retro Arch continuously scan a dir for new roms? Is there anyway to exclude certain sub-directories?
For example my dir is B:\Games\Emulation it has the games sorted by platform, it had additional emulators and retroarch as subdirs, so I want to exclude the emulator/retro arch dirs and only include the game dirs.

[What is actually happening]

Steps to reproduce the bug
  1. [First step]
  2. [Second step]
  3. [and so on...]
Bisect Results

[Try to bisect and tell us when this started happening]

Version/Commit

You can find this information under Information/System Information

  • RetroArch: [version/commit]
Environment information
  • OS: [The operating system you're running]
  • Compiler: [In case you are running local builds]

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no source files, tests, version, or concrete reproduction steps. Start by clarifying the desired boot-time and continuous scanning behavior and the rules for excluding subdirectories, then locate RetroArch's directory-scanning entry point; done should include agreed behavior and coverage for both scanning and exclusions.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.