Feature: speed timinggroup property that sets fixed scrolling speed to timinggroup

[freeze-dolphin]

• fix: separate sc dropRate and the one set by user manually in events panel
• refactor: remove useless DropRateChannel and related code
• feat: allow dropRate to be negative

2026-01-28.00-48-55.mp4

[0thElement]

Why did you remove DropRateChannel?

This will break existing SC code that relies on it.

[freeze-dolphin]

Why did you remove DropRateChannel?

This will break existing SC code that relies on it.

Is this field just there to provide Settings.DropRate.Value?

[0thElement]

Yes, it's perfectly fine and desirable to leave the DropRateChannel there. An example use case would be custom note type that follows the regular note drop rate.

Seems good to me after the revert.

[freeze-dolphin]

I just realized that, should I put the DropRate (modified by sc) into GroupProperties.cs and rename it to SCDropRate?

and then let DropRateSerialized become DropRate inplace

like other tg properties controlled by lua sc

[freeze-dolphin]

it's a simple minor refactor so i don't re-open a new pr

here is the patch file: https://github.com/freeze-dolphin/ArcCreate/commit/0219d3795f204e562909cd0e73600aa71f917f06.diff

---

now the dropRate is calculated by adding the one serialized in chart file and SCDropRate controlled by lua sc

---

also remove the unnecessary cleanup logic:

---

@rechn3r