Closed m4saka closed 2 years ago
I still think having dom
in camera.cam.pattern.note_event
would be the way to go.
In my previous post, this dom
flag will have a different meaning from the dom
in audio.audio_effect.note_event
.
While dom
stops all active audio effects in audio_effect
, it stops only the same patterns invoked by other notes in cam.pattern
. For example, a spin
with dom:true
will stop all other spin
s but does not stop other active patterns.
But maybe we need to choose the way stopping all other patterns in cam.pattern
as well, because spin
and half_spin
should not be played simultaneously.
In the current KSM, spin
& half_spin
are not played simultaneously, but spin
& swing
(or half_spin
& swing
) can be played simultaneously.
This behavior cannot be reproduced in KSON unless we have something like "camera pattern groups" for domination, but it is too much for this small issue...
In the current KSM, spin & half_spin are not played simultaneously, but spin & swing (or half_spin & swing) can be played simultaneously. This behavior cannot be reproduced in KSON unless we have something like "camera pattern groups" for domination, but it is too much for this small issue...
It will work fine if the "dom
" flag works for each cam parameter.
This is because spin
(and half_spin
) refers only to rotation_z
and swing
refers only to shift_x
.
Since the specification of note_event by laser point is still unclear, it's better to remove note_event
and replace it with two events: fx_event
, which supports only FX lanes, and laser_slam_event
, which supports only laser slam.
Solved in v0.2.0.
Derived from: m4saka/ksm-chart-format-spec#1
@123jimin wrote:
@m4saka wrote: