Harmony 3.0: Utility Epic

Description

Contributor guide

Tech stack

None

Domain

toolingdeveloper experience

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

4

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

over 1 week

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

Familiarity with HarmonyUnderstanding of .NET runtime patching

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

20

Research direction

This epic contains multiple sub tasks: add nullable support, implement a new logging system, backport features from Harmony.Extensions (overrides for AccessTools/SymbolExtensions, delegate compiler improvements), investigate separating Utility classes from Harmony, and implement issue #317. Contributors should review the linked issue #317 and the Harmony.Extensions repository for context. The epic requires coordinated work across different parts of the codebase; newcomers may start with smaller, well defined sub tasks like the nullable support or specific backports.