User:RiceEmpress
Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
| pubData | description | link
04 Jul 2026 14:50 +0000 04 Jul 2026 01:21 +0000 Scores that were affected by a bug have been fixed on the leaderboards, and will correct themselves on your local save on updating to 1.53. #PK_GODHAND
03 Jul 2026 00:06 +0000 The day when they arrive to demolish your keyboard gradually approaches... #PK_GODHAND
02 Jul 2026 13:56 +0000 01 Jul 2026 06:45 +0000 [contains quote post or other embedded content]
30 Jun 2026 22:54 +0000 30 Jun 2026 20:05 +0000 [contains quote post or other embedded content]
30 Jun 2026 03:54 +0000 This version also adds TIPS to Story Mode, Rivals (set from friends leaderboard), and more! #PK_GODHAND
29 Jun 2026 03:57 +0000 also maybe some fluffy new surprises... some other surprises too... who knows #PK_GODHAND
27 Jun 2026 02:48 +0000 26 Jun 2026 00:00 +0000 [contains quote post or other embedded content]
24 Jun 2026 02:22 +0000 🎨 @/buwakuda @/mochi070823
23 Jun 2026 22:24 +0000 In addition to the main prizes, we'll be giving Steam codes for the game or Act 2 DLC to SPECIAL MENTION artists! #PK_GODHAND
22 Jun 2026 19:11 +0000 19 Jun 2026 18:20 +0000 18 Jun 2026 04:04 +0000 16 Jun 2026 23:52 +0000 13 Jun 2026 03:34 +0000 11 Jun 2026 14:43 +0000 [contains quote post or other embedded content]
08 Jun 2026 17:02 +0000 https://store.steampowered.com/app/681530/NOISZ/
https://www.nintendo.com/us/store/products/noisz-re-collection-g-switch/
06 Jun 2026 03:29 +0000 All TIPS from Act 1 will also unlock retroactively on starting Act 2. #PK_GODHAND
01 Jun 2026 15:16 +0000 24 May 2026 04:00 +0000
17 May 2026 16:48 +0000 10 May 2026 17:17 +0000 securely store cleaning supplies ㅇㅅㅇ #NOISZ_SL #PK_GODHAND [contains quote post or other embedded content]
06 May 2026 22:50 +0000 05 May 2026 04:21 +0000 noisz-ivkoma.webcomic.studio
https://noisz-ivkoma.webcomic.studio/
01 May 2026 16:14 +0000 '
|
|---|
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}}
743860
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.