I'll modify the code so that the stepstype is passed in along with the button list. So it won't be necessary to fetch the stepstype from GAMESATE.
This section lists all the button names in the new system. Stepstypes meant for different controllers should use different button names.
You may have noticed that the player number is missing from the new format. I haven't decided yet how to handle routine mode. I'm considering adding another actor type that would be an overlay on top of the actor. So when the notefield needs to render a tap for player 1, it draws the normal tap, then draws the player 1 overlay on top. That way, it's easier to extend a noteskin to cover 3, 4, or more players, because you only have to make more overlays. Does that seem like a good idea?
This section lists all the button names in the new system. Stepstypes meant for different controllers should use different button names.
You may have noticed that the player number is missing from the new format. I haven't decided yet how to handle routine mode. I'm considering adding another actor type that would be an overlay on top of the actor. So when the notefield needs to render a tap for player 1, it draws the normal tap, then draws the player 1 overlay on top. That way, it's easier to extend a noteskin to cover 3, 4, or more players, because you only have to make more overlays. Does that seem like a good idea?
< cybik> til Kyzentun fixes bugs for breakfast
--
< maxvg1> shakesoda: then why do i still play lol
<@shakesoda> because you're an ITG player. And thus, a masochist
--
<@shakesoda> Kyzentun: I think you might need to put down the meshes for a bit
--
< maxvg1> shakesoda: then why do i still play lol
<@shakesoda> because you're an ITG player. And thus, a masochist
--
<@shakesoda> Kyzentun: I think you might need to put down the meshes for a bit