Advancing time not working properly with Simple Calendar

[Arctis-Fireblight]

Hi, I am Arctis.

I ended up forking and taking over maintenance for the Simple Calendar module and am providing support for Foundry V13+

I have had a couple of users report some issues when using our two modules together with the advancement of time.

Fireblight-Studios/foundryvtt-simple-calendar#12

Fireblight-Studios/foundryvtt-simple-calendar#8

I was wondering if you would be willing to help me troubleshoot further, and help our modules work together properly.

[paulcheeba]

Yeah for sure, Give me a few days or so to look into your changes and I will try to find a fix. I kept Tim's original About Time SC compatibility, so it shouldn't be hard to find. I'm glad someone has forked SC. I'm stoked to get it working again with ATN, it's been a long time coming.

[Arctis-Fireblight]

Sounds good!

The first thing I would probably look at is anything that references the module name.

Because I wasn't able to get ownership of the original package on Foundry, I had to change the slug to foundryvtt-simple-calendar-reborn.

Let me know if you think there need to be any changes on my end, and I can work on those as well.

[paulcheeba]

Your updates to SC seem to work ok. But you are still using FVTT appv1 framework which was depreciated in v12 and won't be compatible with v14. There are some great guides on the wiki for converting appv1 to appv2.
Do you think you can tackle that?
For the most part it changes how the application will be rendered but shouldn't touch the back-end logic. So I can work on re-integrating SCB and hopefully the integration continues to work after SCB is updated to appv2. I'm a middle aged electrical foreman so I've been pretty busy this last week. I'll do my best to tackle this this weekend.

[Arctis-Fireblight]

Thanks for the link to the docs. I did notice that the module is using deprecated API calls and I do plan to fix them in the near future. Right now I am focused on trying to smooth out some issues some users are having migrating their data and some rebranding touch ups to make it more obvious to users that this is a fork.

But after that the next issue on the agenda is upgrading to the newer APIs for foundry and then updating some of the dependencies, since they have known CVEs, as well as rewriting many of the unit tests, since they seem quite unstable.

[paulcheeba]

Your module also shows up in the foundry list as simple calendar, you should change the ID to something different, it was confusing because there are now 2x simple calendars.

…

On Wed, Jan 7, 2026, 10:43 p.m. Arctis Fireblight ***@***.***> wrote: *Arctis-Fireblight* left a comment (paulcheeba/about-time-next#39) <#39 (comment)> Thanks for the link to the docs. I did notice that the module is using deprecated API calls and I do plan to fix them in the near future. Right now I am focused on trying to smooth out some issues some users are having migrating their data and some rebranding touch ups to make it more obvious to users that this is a fork. But after that the next issue on the agenda is upgrading to the newer APIs for foundry and then updating some of the dependencies, since they have known CVEs, as well as rewriting many of the unit tests, since they seem quite unstable. — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASDOLKBZNY5VBRH2QACS6MD4FXVBXAVCNFSM6AAAAACQPCWSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMRSGA2TOOJQGI> . You are receiving this because you commented.Message ID: ***@***.***>

[Arctis-Fireblight]

Yeah, this is fixed in PR19

I initially changed the slug and stuff when I initially submitted my application to foundry, but didnt think about the the package name until after it was approved.

This should be merged and a new release published this evening after I get home form work. Need to fix the bugged unit tests again first though. I guess the original author decided to use the current date and time for the unit tests, which has caused numerous issues with failing tests and pipelines due to them not accounting for edge cases when ran at certain dates and times.

[paulcheeba]

This is fixed in v13.5.0.0, Simple Calendar Reborn has official support. Have a look at the changelog for details. Basically, S&S and DnD5e 5.2 calendars don't really advance time well, so ATN did that for them, while SC and SCR do manage time already, so ATN now defers to SCR if it is installed and the selected calendar.

https://www.patreon.com/posts/about-time-next-147909492?utm_medium=clipboard_copy&utm_source=copyLink&utm_campaign=postshare_creator&utm_content=join_link