It is possible to activate the cheat menu in a network room with core fbneo.

Open
#16,895 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c

Research direction

The report concerns the FinalBurn Neo cheat menu, network rooms, and cheats stored under /system/fbneo/cheat. Start by reproducing the issue as a host in an online fighting game, then verify that the cheat menu cannot be used during network play while ordinary offline cheat use remains unaffected.

Written by the indexing model from the issue text.

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]

Do not let the fbneo cheat menu be activated if you are in a network game room, currently retroarch is being contaminated by cheaters in fighting games using easy commands generated by cheats.

Expected behavior

[What you expected to happen]

Actual behavior

currently, if you are the host of a network game room on core finalburn neo, and if you add the cheats to the /system/fbneo/cheat folder, you can trigger the cheats by playing online, and this is quite annoying because there are several cheaters in capcom and snk fighting games like street fighter and kof.

[What is actually happening]

cheaters are using cheats in fighting games in network play.

Results

It is not possible to use the cheat menu in network play on the finalburn neo emulator.

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

cheatsFBEO

I kindly ask the developers to remove this menu from the online game.

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

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.

More from libretro/RetroArch

All issues in libretro/RetroArch

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.