Skip to content

Game Setup

You must obtain clean, unmodified and complete data to proceed with our guides

Corrupted or incomplete files will cause unpredictable issues we can't cover.
TWO-TORIAL does not provide or distribute game data. Do not ask.

Preparing data

Ensure your game files are not marked as read-only:

  • Right click the directory containing your files
  • Click on Properties
  • Under the General tab, find Attributes and uncheck Read-only
  • Click Apply
  • When prompted, select Apply changes to this folder, subfolders and files
  • Click OK to confirm, then OK again to close Properties

The complete game data should be approximately 20 GB or larger.
If your data is significantly smaller, you likely have an update archive instead of the full game data.

Here's what the expected data structure should look like:

📂data
📂dev
📂modules
📂prop

If your data does not look like this

If you have .dll files next to your data, prop, etc., folders:

  • Create a modules folder if it does not exist already
  • Move all .dll files into it

If extra directories or files are still present (executables, scripts, etc.), remove them.

This also indicates tampered data, we strongly recommend obtaining clean data from elsewhere.

If your data is already up-to-date, you can skip ahead to the Installing spice2x section

Updating data

Make sure you're using the right update for your current game version

pop'n music updates have M39 and one or two datecodes in their archive names.

Single datecode: Contains one update (e.g., M39_NewDateCode.7z)
Two datecodes: Updates from the older to newer version (e.g., M39_OldDateCode-NewDateCode.rar)

A date code should look something like this: YYYYMMDDXX

In the two-datecode example:

  • OldDateCode is the older date, the game version required to apply this update
  • NewDateCode is the newer date, and is the version you'll arrive at after applying the update
  • Extract the update to your game directory, ensure directories align and overwrite files when prompted
  • Open prop\ea3-config.xml and find the <ext> line:
    <ext __type="str">NewDateCode</ext>
    
  • Update the datecode to match your new game version and save
  • If prop\bootstrap.xml exists, also update its <release_code> line:
    <release_code>NewDateCode</release_code>
    

Installing spice2x

If you already have spice2x installed, ensure you're using the latest version

  • Visit spice2x.github.io to download the latest release
  • Extract both spice.exe and spicecfg.exe from the archive into your game's directory
📂data
📂dev
📂modules
📂prop
🌶️spice.exe
🌶️spicecfg.exe

Configuring spice2x

Following tabs correspond to the ones found in spicecfg

Additional information is available at spice2x's wiki.

Avoid changing or patching anything you don't need or understand unless explicitly told to

This tab is used to bind your keyboard and controller buttons

Bind vs Naive

Bind - Use for controllers and hardware devices. More responsive and detects any HID device.
Naive - Use for device agnostic keyboard binds. Less responsive but works with simulated keystrokes.

Binding your buttons

Click on Bind or Naive then press the key you want associated with the action.

With your controller and/or keyboard plugged in, configure your keys for:

  • Maintenance: Service, Test
  • Game buttons: 1 to 9
  • P1 Keypad: 1 to 9, Keypad Insert Card

Additional info

  • Use page navigation at the bottom to bind multiple buttons to the same input
  • Check Bind Many to bind multiple controls in sequence
  • Click Edit after binding for advanced options (invert, MIDI sensitivity, etc.)

No need to change anything here

This tab is used to bind keys to toggle spice2x and game-related overlays

Binding extra buttons here is optional, defaults are fine

Click on Bind or Naive then press the key you want associated with the action.

This tab allows you to configure controller lights to sync with the game

Not all controllers support this, but it does not affect gameplay and is completely optional.

  • Click Bind
  • In Device, pick your controller
  • In Light Control, select the corresponding light
  • Click Close
  • Repeat for your other lights

This tab lets you configure which cards are used to save your game profile to

If you own a physical e-amuse/FeliCa card and a compatible NFC card reader

Setup instructions vary depending on your specific reader model.

Navigate to the Advanced tab and scroll down to the NFC Card Readers section.
Browse the available options and hover over each one to view descriptions and configuration guidance.

There is no need for you to specify cards for either player in this tab when using a card reader.

If you don't, you can use a virtual card number instead

If you already have generated a card number before, you may use this one.

To generate a new card number for Player 1 or 2:

  • Click on Open...
  • Choose where to save your card number
  • Give it a file name (e.g. card0.txt)
  • Click save
  • Finally, click on Generate

This will automatically generate a valid card number for you and keep it in the file you specified.

We recommend using popnhax instead of spice2x patching

No need to change anything here

No need to change anything here

NVIDIA GPU users ONLY

Enable NVIDIA profile optimization (-nvprofile) to let spice2x create an optimized profile for your game.

No need to change anything here

Connecting to a network

Pick one or the other, not both!

Option 1: Remote (Online Network)

Remote networks typically require an invitation to join.
You'll need to connect with members of the community who can provide you with an invite.

Your network should provide you with the necessary information to proceed:

  • Open spicecfg.exe and head to the Options tab

Under the Network category, set the following settings provided by your network:

  • EA Service URL (-url)
  • PCBID (-p)

Option 2: Local e-amuse Emulator (Asphyxia)

For instructions on setting up Asphyxia, please refer to our Asphyxia setup guide.

After Asphyxia is setup with the proper plugin for your game:

  • Open spicecfg.exe and head to the Options tab
  • Under the Network category, set your EA Service URL (-url) to point to your asphyxia server, typically localhost:8083

Before playing

A few things to remember before each play session

  • Close of any applications running in the background which could affect performance
  • Double-check your monitor is oriented properly for this game
  • Double-check your sample rate is correct for this game
  • Connect your controller

You're all done! The game should load up properly now

Help

Something's wrong?

Make sure you've followed all steps correctly and also read other relevant guides.

Still stuck? You can join our Discord community server for support!
Click on the Discord logo at the bottom right of the page.