Hey AlvinBlox, I’ve been a longtime fan of your channel and really appreciate all the educational and entertaining content you’ve shared over the years. Recently, I noticed a dip in views, and I think it might be because the videos you’ve been posting lately are a bit different from the ones you posted a couple of years ago. Those videos were incredibly engaging and educational, and I really miss that style. I believe if you return to creating those types of videos, it could bring back a lot of your audience and attract new viewers too. Your unique approach to making learning fun and interesting is what sets you apart, and I’m confident that if you tap into that again, your channel will thrive. Keep up the great work and know that you have a dedicated community rooting for you! Best, Shaen
Thanks for the new informative videos. I've been struggling to learn some of the more advanced topics in Roblox studio and these have helped me learn a lot more than I have in months.
Just a recommendation, can you make a tutorial on player movements? Covering basics like double jump, dashing and crouching to advanced like wall running and vaulting? I know it will be a little more complex and longer than your recent videos but it will help me out a lot. Thank you 🤝
Attributes vs (something)Values: Attributes are way better than values, you don’t have to use :Clone() or Instance.new() which makes it not use some of your memory, but one thing that I wish attributes have is a object type, similar to ObjectValue. The fact that attributes are serialised on an instance is a big winner in my opinion. Attributes are going to replicate with the instance they’re attached to instead of the replication being separated into another instance. They’re also a great match when you want to pair it up with other features like CollectionService; child instances are no longer a dependency, just the attribute’s existence. Attributes take up less memory on your device Attributes are ~18x faster to create dynamically Attributes are ~240x faster to delete You can even use Attributes on Value Objects
Hey AlvinBlox,
I’ve been a longtime fan of your channel and really appreciate all the educational and entertaining content you’ve shared over the years. Recently, I noticed a dip in views, and I think it might be because the videos you’ve been posting lately are a bit different from the ones you posted a couple of years ago. Those videos were incredibly engaging and educational, and I really miss that style.
I believe if you return to creating those types of videos, it could bring back a lot of your audience and attract new viewers too. Your unique approach to making learning fun and interesting is what sets you apart, and I’m confident that if you tap into that again, your channel will thrive.
Keep up the great work and know that you have a dedicated community rooting for you!
Best,
Shaen
Ye, I think if AlvinBlox goes back to his old types of videos then I am sure that his channel will thrive like it was thriving 2 years ago
Thanks for the new informative videos. I've been struggling to learn some of the more advanced topics in Roblox studio and these have helped me learn a lot more than I have in months.
Just a recommendation, can you make a tutorial on player movements? Covering basics like double jump, dashing and crouching to advanced like wall running and vaulting? I know it will be a little more complex and longer than your recent videos but it will help me out a lot. Thank you 🤝
Keep on going Alvin!!!
Attributes are useful to make Replicators with
which then the client can listen to easy server to client commutation
Attributes vs (something)Values:
Attributes are way better than values, you don’t have to use :Clone() or Instance.new() which makes it not use some of your memory, but one thing that I wish attributes have is a object type, similar to ObjectValue.
The fact that attributes are serialised on an instance is a big winner in my opinion. Attributes are going to replicate with the instance they’re attached to instead of the replication being separated into another instance. They’re also a great match when you want to pair it up with other features like CollectionService; child instances are no longer a dependency, just the attribute’s existence.
Attributes take up less memory on your device
Attributes are ~18x faster to create dynamically
Attributes are ~240x faster to delete
You can even use Attributes on Value Objects
But what do u use values for
Thanks for inspiring me sir😭
Best alternatives for values
well I would say that values are an alternative too attributes and tags
nice
First
Bru you are not
@@jsscontent514 They are lol
@@jsscontent514 does it matter??
LETS GO I AM THE FIRST COMMENT!
SO SIGMA
so sigma
Second actually, sadly
Go to newest and go to down to the oldest comment, it’s some random guy then you
Boring