Cool_Tools/bemaniutils
1
0
Fork 0
mirror of synced 2025-02-21 04:56:25 +01:00
Code Releases Activity

Add documentation from Subject38 as to where the bitfield for hot_music comes from.

Browse Source
This commit is contained in:
Jennifer Taylor 2022-09-23 02:25:37 +00:00
parent 3ee62db915
commit 829ce77f63
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
bemani/backend/jubeat/festo.py
View File

@ -693,7 +693,10 @@ class JubeatFesto(
# Mapping of what music is allowed by default, if this is set to all 0's
# then the game will crash because it can't figure out what default song
# to choose for new player sort.
# to choose for new player sort. The way to calculate what song one of the
# bits is for in any music_list array below is to look at the "pos_index"
# field in the music_info.xml file. The entry in the array is calculated by
# "(pos_index / 32)" and the bit to set is "1 << (pos_index % 32)"
info.add_child(Node.s32_array(
'white_music_list',
[
@ -784,6 +787,9 @@ class JubeatFesto(
],
))
# Bitfield that determines what music is considered "pick up" versus "common" on the jubility
# jacket field at the end of the game. Hot music is just the music in the current mix. The
# bitfield values were taken from the "pos_index" field for all songs that are in festo.
info.add_child(Node.s32_array(
'hot_music_list',
[