It shouldn't.and this is bad.
it means sneek can still access real NAND.
unless it's a neek feature, but neek should never access real NAND. it's part of it's purpose to be 100% sandboxed.
game notification works like that:
when launching a game, a temporary file is written with the game name and the current time.
When you launch System menu next time (probably only on reboot, not if you shutdown) the system menu checks for temporary file and calculate the time difference from current time-launch time = play time, and write it to board menu.
in order to have sysnand write the playlog, the temporary file need to be present on the /nand/temp/ folder
but if you launched neek from HBC, nswitch doe not know your game so it can't write to NAND.
once sneek is launched, you select the game and the sneek system menu write the temp file on /sneekNAND/temp/
when you exit the game and return to sneek system menu, it checks the file and create a log on sneek's system menu board.
When you exit sneek by using nswitch (or neek2o channel), it reboot the console and you shouldn't have any temp file on your realNAND/temp/
what you can check :
in sneek, launch a game and exit. Look on the sneek's board if you have the playlog. if it's not present then the temporary file is not present in emuNAND/temp/ folder.
if not, exit to real nand by rebooting, and see if it write log again. it's bad if it does.
Very bad if you use neek on vWii, as it means vWii is still accessed and tempered by neek and a brick can occur. Knowing there's no mean to restore backup on vWii, it's really bad to use sneek/uneek/neek2o on vWii.
Are you sure you didn't boot using an USBLoader with playlog setting enabled?
in that case, the loader writes the temp file on real nand before launching neek.
when you reload real nand system menu, you get your "autoboot game" listed as played, even if you played many other games while in neek.
"played for 23h59" is the limit.
either you shutdown and reboot more than a day later, or the date used in the temp file was incorrect.
Maybe the temp file is deleted from the NAND at shutdown request, so if you shutdown neek without returning to realNAND the file got deleted from neek's nand only, but is still on real nand. But that's just if you never returned to realNAND from neek.
Another possibility :
You used (long time ago) USBLoader to play that game with playlog setting.
the loader writes the temp file.
but you are also using "return to loader", so you never return to system menu to write the playlog. (I will check if playlog is auto-disabled when using return to)
You shutdown the console and few days later you power it and as you have bootmii boot2 to autoboot HBC you still never go to system menu.
You launch nswitch and play on neek. You exit neek and bootmii returns to HBC again.
then you decide to launch system menu from HBC menu, and system menu find your very old temp file generated by usbloader and write the playtime as 24h.
I'm pretty sure I was using nswitch back on those days, not USB Loader GX nor any other usb loader. And it happened twice. I never got back from emuNAND to realNAND since I didn't install nswitch wad on emuNAND: I was playing the games and either shutdown the Wii in middle of games, or shutdown the Wii after coming back to emuNAND's main menu (where the Disc Channel, News Channel Shop Channel, etc., are).
Now, I've tried to reproduce this once again but I couldn't:
I tried loading emuNAND with nswitch. Then loaded Black Ops, played online 1 round, that's 10-12 minutes, then rebooted Wii. The playlog was on emuNAND, not on realNAND. Also tried taking pictures on Metroid Prime 3, all pictures were on emuNAND's board, none of them were on realNAND's.
Also tried renaming "bootmiineek" folder to "bootmii" to load emuNAND from the beginning. I did same tests as before, with same results.
So everything seems to be working as it should.
The only changes I made from that time to present day were updating real system menu from 4.1E to 4.3E (emuNAND was still the same as before) and changing old slow hdd. Some games blackscreened (specially CoD series when going online) using that old hdd.
Could it be that the Wii couldn't write the playlog on emuNAND located on that slow hdd and wrote it on the realNAND?
Now, I've tried to reproduce this once again but I couldn't:
I tried loading emuNAND with nswitch. Then loaded Black Ops, played online 1 round, that's 10-12 minutes, then rebooted Wii. The playlog was on emuNAND, not on realNAND. Also tried taking pictures on Metroid Prime 3, all pictures were on emuNAND's board, none of them were on realNAND's.
Also tried renaming "bootmiineek" folder to "bootmii" to load emuNAND from the beginning. I did same tests as before, with same results.
So everything seems to be working as it should.
The only changes I made from that time to present day were updating real system menu from 4.1E to 4.3E (emuNAND was still the same as before) and changing old slow hdd. Some games blackscreened (specially CoD series when going online) using that old hdd.
Could it be that the Wii couldn't write the playlog on emuNAND located on that slow hdd and wrote it on the realNAND?