Log In  


Alas, it looks like the old (albeit undocumented) TIME() function has either been broken or deliberately retired, as it now always returns 0.

No doubt coinciding with the addition of the cool new clock features of v0.1.11c, which are very cool.

Sadly, this means there are a few tweetjams/carts that no longer function :o(
(using TIME() was a sneaky way of getting a linear number change with few characters!)

*pores a bottle for our fallen tweetcarts *

#TimeIsDead #LongLiveTheTime

time api breaking change
P#45964 2017-11-07 08:49 ( Edited 2017-11-07 14:40)


Oh no! That wasn't supposed to happen. It is returning 0 when there is no _update or _update60 callback being used. This will be fixed in the next update.

#TimeLives #NoTweetcartLeftBehind

P#45971 2017-11-07 10:24 ( Edited 2017-11-07 10:25)


Whoop! \(^O^)/

P#45972 2017-11-07 10:28 ( Edited 2017-11-07 10:59)



That's a uh..

It's an important function >_>;

P#45986 2017-11-07 14:40

Log in to post a comment


New User | Account Help
:: New User
About | Contact | Updates | Terms of Use
Follow Lexaloffle:        
Generated 2018-10-23 12:03 | 0.223s | 1572k | Q:15