User:RiceEmpress

Chapter	Characters	Song	Level Requirements
Chapter 0.I		First Star*	1 1 1 1
Chapter 0.II			1 1 1 1
Chapter 0.III			1 1 1 1
Chapter 0.IV			1 1 1 1

*Used as the song present in the tutorial. Not unlocked for Free Play after chapter completion.

31 Dec 2025 04:06 +0000
Stop by our MAGFest booth (in the indie games showcase) to try out our newest games! You can play Stage 1 of Chronal Chain and a new crossover song in PROJEKT GODHAND!

1. ChronalChain #PK_GODHAND

25 Dec 2025 06:58 +0000
PROJEKT GODHAND 0.6 is now available (and 20% off in Steam's Winter Sale)! This version brings 3 new songs to GODHAND CORE, bringing the total base content to 39 songs.

We'll be making that 50 in the full release, so let's hope you asked Santa for a new keyboard...? #PK_GODHAND

24 Dec 2025 23:39 +0000
GODHAND 0.6 is coming tomorrow, but you can listen to this cover of Maybe This Year... definitely today???

💚 @mioricelesta.bsky.social ❤️ @hiiragiyuu.bsky.social

It'll arrive as one of 3 new songs in the default songlist! #PK_GODHAND youtu.be/WToBmEZFc04 https://youtu.be/WToBmEZFc04

09 Dec 2025 23:36 +0000
you may have noticed that we've been withholding the most important feature of PROJEKT GODHAND for its 1.0 release. but this christmas, we'll finally add just a little bit of it in early access 0.6

it's been a long year... pass the yuri #PK_GODHAND

10 Nov 2025 14:55 +0000
The soundtrack for PROJEKT GODHAND ACT 1, "paradiso disk" is now available for preorder! You'll receive all the tracks that are currently playable in the game right now, and the rest will be available at launch in January. #PK_GODHAND https://anarchgames.bandcamp.com/album/godhand-paradiso-disk

05 Nov 2025 04:29 +0000
PROJEKT GODHAND 0.56 is now available! This version adds space bar support (it can hit specifically mashes on either side), Korean player name support, and some minor fixes. #PK_GODHAND

03 Nov 2025 16:20 +0000
PROJEKT GODHAND 0.55 is now available! This version aims to fix a rare crash issue, and makes some changes to the timing adjustment option (you'll find the value has changed substantially, but it should still be correct for you). #PK_GODHAND

20 Oct 2025 12:06 +0000
PROJEKT GODHAND 0.54 is now available! This version fixes some display issues related to cloud save, as well as a DLC loading issue related to the Unity version update. #PK_GODHAND

10 Oct 2025 18:27 +0000
PROJEKT GODHAND 0.53 is now available! This version adds cloud save, faster startup, and a required Unity security fix. #PK_GODHAND

05 Oct 2025 02:34 +0000
The PROJEKT GODHAND demo is now live! Now you can enjoy a Free Keyboard Smashing with a selection of 7 songs, and pick up the game at 20% off this week! #PK_GODHAND https://store.steampowered.com/app/2978440/PROJEKT_GODHAND/

there is only rice

HI i'm ruby! this is my testbed

Event Cycle

The countdown timers are all based on the countdown clock extension for Fandom. A typical template for the countdowns looks something like:

{{NOISZ SL Recursive Events|cyclestart=2023-03-15 04:00 +0000}}

Where cyclestart is a variable determining the beginning of an 8-week cycle. The widgets use this 8-week cycle to determine what events are currently running - or rather, how far it is into an 8-week cycle. Synthetic and Recursive events currently run on the same clock. If you look at the NOISZ SL Recursive Events, it may look daunting, but a lot of it is just text operations; the only variable here is the currenly running, event, seen in things such as {{CurrentNoiszSLEvent|cyclestart={{{cyclestart|}}}}}, {{EventCountdown|eventstyle=Nuclear Drip|cyclestart={{{cyclestart|}}}|countdown=True}} and {{EventTimeLeft|cyclestart={{{cyclestart|}}}}}. Note that {{{cyclestart|}}} sets a variable within the template, and whatever goes after the pipe at the end is set as the default for that variable if nothing is entered.

CurrentNoiszSLEvent uses that 8-week cycle to determine what events are running. EventCountdown uses the Countdown widget until a certain mark in that 8-week timer, and EventTimeLeft does the same, but for a mark 2 weeks after that.

If you look at CurrentNoiszSLEvent, it uses a case/switch statement depending on EventCycleTime, which returns how many seconds we are into an 8-week cycle.

EventCycleTime is simply: {{#expr:({{#time:U|now}} -{{#time:U|{{{cyclestart|2023-04-01 04:00 +0000}}}}})mod4838400}} ie, it looks at the time between now and any past date set as the beginning of a cycle, which is defined as the moment Recursive Event 01 goes live. It uses mod4838400 to divide that time elapsed by the total number of seconds in an 8-week cycle, and returns the remainder, which is how many seconds we are.

To recap, it does that, and CurrentNoiszSLEvent uses that time to determine where in an 8-week cycle we are in seconds; if we are less than 1209600 seconds into a cycle, which is two weeks, it determines the currently running Recursive Event is Attitude Mint. If it's more than that, the case switch moves onto the next statement, and so, if we're more than 1209600 seconds but less than 2419200 (4 weeks) in, then the current event is Blue Moon, and so on.

Countdown Clocks

EventTimeLeft

EventTimeLeftUnix: {{#expr:1209600 - {{EventCycleTime|cyclestart={{{cyclestart|}}}}}mod1209600}}
665461

The countdown clocks for EventTimeLeft and EventCountdown use markers to count down to. EventTimeLeftUnix looks at how many seconds we are into a cycle and divides it by 1209600, and returns a remainder. It subtracts that from 1209600, the amount of seconds in two weeks; this returns the amount of seconds left in this mini 2-week cycle within the greater 8-week cycle.

EventTimeLeft is the countdown clock itself, and is:

<includeonly><span class="countdown" data-end="stop" data-callback="myFunction" data-options="short-format" style="display:none;">Ends: <span class="countdowndate">{{#time:r|@{{#expr:{{EventTimeLeftUnix|cyclestart={{{cyclestart}}}}} + {{#time:U|now}}}}}}</span></span>

The time it's counting down to is {{#time:r|@{{#expr:{{EventTimeLeftUnix|cyclestart={{{cyclestart}}}}} + {{#time:U|now}}}}}}, which adds the seconds left in the 2-week cycle that is a single event to the current time, and then counts down to it.

EventCountdown

EventTimeCountdownUnix looks at where we are in the 8-week cycle and accordingly counts down to the next 2-week marker using a case/switch. The "if time > 0" condition in there is to deal with the possibility that a date in the future was set to determine the 8-week cycle.

EventCountdown is the clock itself: {{#if: {{{countdown|}}} | <span class="countdown" data-options="short-format" style="display:none;" data-end="stop" data-callback="console.log('countdown ended!')">Starts: <span class="countdowndate">{{#time:F d, Y H:i T|@{{#expr:{{EventTimeCountdownUnix|cyclestart={{{cyclestart|}}}|eventstyle={{{eventstyle|Attitude Mint}}}}} + {{#time:U|now}}}}}}</span></span> | Starts: {{#time:F d, Y H:i T|@{{#expr:{{EventTimeCountdownUnix|cyclestart={{{cyclestart|}}}|eventstyle={{{eventstyle|Attitude Mint}}}}} + {{#time:U|now}}}}}} }}

Where the time it counts down to is: {{#time:F d, Y H:i T|@{{#expr:{{EventTimeCountdownUnix|cyclestart={{{cyclestart|}}}|eventstyle={{{eventstyle|Attitude Mint}}}}} + {{#time:U|now}}}}}}

This adds the time left until the next two-week marker to now, and tells the clock to count down to it. If nothing is defined, it decides the next style will be Attitude Mint.

Countdown clock end

If you look at the dev.fandom.com link above, you can see that a countdown clock ends many ways. One problem with the clocks currently is that the wiki does not update its own internal clock until something forces it to wake up, usually in the form of an edit or a null edit. Once an event ends, the event cycle doesn't update until null edits are made to the relevant pages, forcing it to recalculate everything.

If you look at the clocks' codes, you can see the "data-callback"; this calls the relevant Javascript function defined by this variable. The function is defined in MediaWiki/Common.js. EventCountdown is where it's properly used; you can see it uses the "selfNullEdit" defined in common.js, where the function finds the element with id "ca-null-edit" - the Null Edit Button - and clicks it using jQuery. corn chip

“What” the cat