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

Event-script parser (RDT offsets[8])

Open
#44 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp

Research direction

The issue names no files or entry points in this repository. Start by reading the RE1 event opcode table in BioRand or biohazard-utils, and find where the existing room-script handling of RDT offsets[8] lives in the codebase. The issue lists three goals: naming events, giving subtitles voice-line timing (#38), and listing items given by events. Done means a parser that yields those three outputs for the RE1 event scripts. Ask the maintainer to confirm scope before writing code.

Written by the indexing model from the issue text.

Description

area:re1 enhancement

Room scripts set some story flags; the cutscene/event scripts set the rest, hand over items (Barry's lockpick, Richard's radio) and play voice lines. Parsing them would:

  • name events without asking (ask mode)
  • tell the subtitles which voice line plays when (#38)
  • list items given by events in the progress tracker

BioRand / biohazard-utils (MIT) have the RE1 event opcode table.

Dominant language
C#
Stars
0
Forks
0
Avg merge
1d 6h
Merged PRs (30d)
3

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 mscrnt/lockpick

All issues in mscrnt/lockpick

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.