This problem has been around for quite some time now. Seems to happen mainly because the ruleset assembly filename ends with .Packed.dll whereas the assembly namespace is osu.Game.Rulesets.Gamebosu. At a first glance, it seems that DllResourceStore assumes that the assembly filename is the same as the assembly namespace;

this could be alleviated by either renaming the final ruleset assembly to match the assembly namespace or PR-ing a framework fix to provide an assembly namespace override prefix to use for lookups.

Either I'm missing something simple or maybe my ROMs don't work but I can't click on them or get any kind of feedback I've pressed every single key on my keyboard nothing happens? Am I doing something wrong I just dragged the ROMs into the ROM folder and can't play them

And while I am at it, adding a workflow for automatically publishing release artifacts would be cool too.

i download it and i get this error

Need to patch Emux to prevent crashing the game when running some roms.

• ROM selection screen gets stuck in weird state when launching a rom then quickly hitting escape during the transition then selecting the same ROM again (DI error).

• Mouse scroll propagating to sound overlay when it shouldn't

Could you add localisation support like Flutterish did? Id like to translate your ruleset to Russian.

Title says it all

whyyyyyyyyy

osu!lazer version: 2023.621.0-lazer
gamebosu version: current latest.

May require a PR osu-side to disable the HUD presence (as well as the break overlay presence).

Add a toolbar button to open the gamebosu rom selection from anywhere in the game.

even after updating from last issue (#225), the rulesets still wont work in my lazer client. Perhaps its my environment problem?

osu!lazer version: 2023.621.0-lazer
gamebosu version: current latest (2023.708)

Error warning by osu!lazer:

Log File:
runtime.log

Basic system information:
OS: Windows 11 Pro
Version: 10.0.22621 Build 22621
System Manufacture: GIGABYTE
Processor:11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz, 2688 Mhz, 6 Core(s), 12 Logical Processor(s)
(Info get from "System Information" Windows executable.)

Look into using a custom DrawNode for DrawableGameboyScreen.