It’s a pretty neat effect and is useful as reference for other types of systems where you want to animate numbers rather than just typewriting or putting a static event. Thanks for sharing.
There is some feedback I’d like to offer. Still understanding that this isn’t exactly a dedicated and full model and rather something just rough to demonstrate an effect, I feel like it’s still applicable.
Don’t use delay. Subject to frequent discussion lately spawn, delay and wait are bad. You should settle for event-based solutions where possible. In this case, what you should be using instead is Tween.Completed. The delay is clearly used here to run functions after the tween finishes but an event already exists to properly do that and so it should be used.
Use ipairs over pairs when working with contiguous arrays (e.g. GetChildren). Child ordering doesn’t matter in this scenario but ideally and canonically it’s better to use ipairs to go through arrays. I am unsure of the speed difference but I’d imagine a known order is faster to iterate than arbitrary order (index versus next function).
Consider using variables to store TweenInfos that are used multiple times rather than creating a new TweenInfo object every time a tween needs to be made, provided you’re going for a consistent feel. I notice that there’s a lot of TweenInfos being created that are just the same as another, so these can just be reused instead of created per tween.