Skip to content

v2.2 ~ Autopin ? Revamped Attract Mode ?! Kamaitachi integration?! ~

Choose a tag to compare

@CrazyRedMachine CrazyRedMachine released this 18 Jul 19:54
· 33 commits to main since this release

Version 2.2 is there with some nice new features as usual :)

Credits

Tachi integration uses libcurl to perform the requests,
jsmn, jsmn-find and chash to parse the json data.

Enhancements

<high_framerate>

If you play high framerate without timer freeze or event mode, you might have noticed the timer is faster than usual. A new patch has been added to slow it down
Note: it is automatically enabled when high_framerate is on.

Additional debug options

<force_slow_timer>

You can use this option to force slowing down the timer even without high_framerate. This is useful if for some reason you want to play at higher framerate but cannot use the high_framerate patch

New additions

< autopin>

Small QoL feature to save precious seconds, you can have popnhax enter your pincode for you.

Note: this is a 0/1 bool value. Do not enter the pincode directly in popnhax.xml. it requires you to enter your pincode in a separate _pincode.secret file as plain ascii.

Note: This hook has a 30sec cooldown, so that you can enter your actual pin if the one from the file is wrong. This also implies that if you quickly exit from the pincode screen and scan a new card in less than 30 seconds you won't trigger autopin right away... this definitely won't happen on normal use, so I'm fine with just leaving a cooldown

<attract_ex>

This will pimp the attract mode demo songs a little. It will play the EX charts instead of the Easy ones, and at x4.0 Hispeed for a flashier attract

<attract_full>

If you're frustrated by the songs being cut short when you leave your cab running, then this patch is for you. Attract mode will now play the full songs.

I'm not even close to being done with attract mode customization, I actually have a pretty cool goal in mind for cab users, so stay tuned 👀

<tachi_scorehook>

This is a scorehook for kamaitachi, which will send your score to the configured tachi server after each song played.
Note: this won't apply to "aborted" songs (ie. quick retire or quick retry during song).

It supports multiple user profiles based on your Popn Friend ID, just like local favorites does.

config file format

Config file is a json file with two keys, "key" for your apikey and "base" with the base tachi server address.

The config file should be named _tachi.default.conf or _tachi.<friendid>.conf and placed directly into the contents folder.

There is also legacy compatibility with an "url" key containing the direct-manual import url so that you can keep using your old silent-config.json file data.
(ie. rename your old silent-config.json to _tachi.default.conf and it should work, or _tachi.678945671234.conf if you want it to apply only on your account with friend id 6789-4567-1234).

Note: _tachi.<friendid>.conf files take precedence over _tachi.default.conf, but the default conf will still apply to remaining accounts and to guest plays.

_tachi.default.conf example file

this is the basic structure for reference

{
	"key": "<your api key goes here>",
	"base": "https://kamai.tachi.ac"
}

Additional debug options

<tachi_scorehook_skip_omni>

When this setting is enabled, the scorehook won't send omni chart scores to the configured tachi server.

Note: This setting affects omnimix charts only (removals and CS/older hardware exclusives, ie. songids <= 3400).

Custom charts (songid > 3400) are never sent.

<tachi_rivals>

This allows you to see your rival scores ingame (e.g. see scores and ranking on song select and result screen...), as if they were all playing on the same server as you.
It uses the same config files as the score hook.

Note: While kamaitachi allows you to add up to 5 rivals, Pop'n only supports a maximum of 4, therefore your 5th rival cannot be displayed ingame.