Change the Days since 2000 Block

BigNate469

If this is implemented, then all existing

(days since 2000)

blocks should be converted into

(days since () ::sensing)

blocks, or the existing

(days since 2000)

block should continue to exist as a hidden block.

Additionally, the default value of the input in a

(days since () ::sensing)

should be 2000.

Yes, I know that most of that has been said before in this topic, but I just wanted to put it in one post and outline what I think is best in this case.

Thiago_le_meilleur

‎

Last edited by Thiago_le_meilleur (April 15, 2025 11:14:16)

lapisi

Thiago_le_meilleur wrote:
(#342)
This suggestions is a duplicate of this one :
https://scratch.mit.edu/discuss/post/292541/

that's a link to the topic you're on right now

Last edited by lapisi (April 11, 2025 21:40:23)

CatPoderoso21

9kiwi9 wrote:

(days since 2000)//I think this block should become
(days since (2000))//category=sensing .  Do you think it is a good idea?

Hyper support!

jmb1293634

theonlygusti wrote:
It's pointless.

Its not pointless I am using it extensively in my current project + how many people use the

when [ v] > (10)

block?

Last edited by jmb1293634 (April 15, 2025 07:57:47)

jmb1293634

Tramcrazy wrote:
Good idea but, I don't really see the point in this block (the existing one and the suggestion) as to find the year you can just use this:
(current [Year v])

stickfiregames wrote:

Support

(days since [28 v] [September v] [2014 v] :: sensing) // maybe make the year a number slot, and maybe the day as well

as well as

(global [minute v] :: sensing)

pretty sure

(days since 2000)

(by the way I think this is one of the most versatile blocks in existence - second only to

glide () secs to x: () y: ()

)
reports much smaller units of time than the

(current [ v])

can ever hope to do: at least milliseconds I think

jmb1293634

ScratchBoy179 wrote:
No support. I've made a whole game based on this block lol. It's the only way to get 1) miliseconds 2) time zones

finally someone who appreciates the value of

(days since 2000)

_Zelda-Lover_

theonlygusti wrote:
I would just remove the days since 200 block altogether. It's pointless. Maybe replace it with days since the Epoch
(days since the Epoch :: sensing reporter)

What’s an Epoch?

TeStar002

No Support. I think most people here do not know the main use for the days since 2000 block. It gives very precise information about the time in milliseconds. It is the easiest way to use milliseconds, and I have used it in multiple projects on my main account. It is also used to detect time zones. Making the days since 2000 block have an editable would not help in almost any scenarios.

GameCatastrophe0927

TeStar002 wrote:
No Support. I think most people here do not know the main use for the days since 2000 block. It gives very precise information about the time in milliseconds. It is the easiest way to use milliseconds, and I have used it in multiple projects on my main account. It is also used to detect time zones. Making the days since 2000 block have an editable would not help in almost any scenarios.

Yeah, I agree with this, it's mainly used for clocks.

TeStar002

_Zelda-Lover_ wrote:
What’s an Epoch?

The beginning of January 1 1970. Or any time that was selected to be the “Origin”. I don't think that would help at all though.

medians

lapisi wrote:
8to16 wrote:
(#338)
workaround
((days since 2000) - ([year] * (365))
too hard to work with, I don't think anyone wants to try to do calculations to find out what to put in that block

Leap years also exist, so 365 might not work

Last edited by medians (July 13, 2025 22:22:19)

106809nes

medians wrote:
lapisi wrote:
8to16 wrote:
(#338)
workaround
((days since 2000) - ([year] * (365))
too hard to work with, I don't think anyone wants to try to do calculations to find out what to put in that block
Leap years also exist, so 365 might not work

To counter this, I think they would do this instead:

((days since 2000) - ([year] * (365.25)))

oh whoops.. did i necropost? mb..

Last edited by 106809nes (Aug. 19, 2025 23:31:47)

Scratch_Cat_Coder8

Nvm

Last edited by Scratch_Cat_Coder8 (Aug. 20, 2025 03:48:35)

da-ultimate-creater

106809nes wrote:
oh whoops.. did i necropost? mb..

There isn't really necroposts on suggestion forums if the suggestion hasn't been implemented or rejected. It's more like a bump imo.

Natpalprs5

Just remove the block. I can't think of a single instance where I've seen it used.

PoIygon

Natpalprs5 wrote:
Just remove the block. I can't think of a single instance where I've seen it used.

its the only reason you can get miliseconds and timezones.

Also if anyone disrespects this block fdreerf will come after you and turn your legs into pretzels

AceCoderClaws

No support. Days since 2000 is a useful block and I don't see a reason to change it. If you need the time from a different date you can just subtract the time that'd passed between that date and 2000.

set [days since 2015 v] to ((days since 2000) - (5479))  //5479 days between 1/1/2000 and 1/1/2015

da-ultimate-creater

Natpalprs5 wrote:
Just remove the block. I can't think of a single instance where I've seen it used.

Just because you can't think of an instance where this block is used doesn't mean that nobody used it.

If you remove the block, it will destroy tons and tons of projects that already use this block.

IloveRoblox003

Natpalprs5 wrote:
Just remove the block. I can't think of a single instance where I've seen it used.

It can calculate delta time and other things relating to time..

Discuss Scratch