Hi !
Your projects looks interesting @CryBlanka and @Fittergem1000 (I see that you too were creating this type of things).
I have one idea that could help you, I think that you could make an app maker as a plugin.
And the idea is that when you click on “Create an app”, it will open you a form with like the name of the app, the color of the app, the id of the icon, etc … and it will create an event that will say when the apps it’s open and only that, the rest would be handle by you.
So it’s my idea !
I hope it was helpful and have a nice day and keep up the good work !!!
2 Likes
Love the idea. I will attempt to add this. (Never made a plugin before lol)
3 Likes
Good luck then ! This text will be blurred
2 Likes
Can you add it to github? =)
Suggestion: update the dockbbuttonsfunctionality in githusoit use tweennservice and not :TweenSizeAndPosition() and make cMessagescripts to .lua
Adding on, use spring animations
(before i get murdered alive a reminder not all springs are bouncy)
1 Like
1 Like
agree,
it may be of use to create an issue (and a pr if ur feeling generous) in their github for organizational purposes:
1 Like
Hi Paulo,
as i said before, I don’t have that much experience in lua and I have no idea what arguments are you talking about and what would be the difference between wait and task.wait.
Best,
~ SG
1 Like
U using wait() not task.wait() or even better tween.Finished:Wait()
You not creating variables like tweenservice and consuming extra memory
You using outdated methods instead of tweenservice
About the remotes you could just create a remote and add a argument like big, square etc
Also i can help but please give credits 
1 Like
Hi Paulo,
thanks, why not I guess one or more credits 
SG Is Here#5578
Best,
~ SG
2 Likes
I will once i rewrite it hahaha
1 Like
Finished: tweenservice instead of outdated methods
Pending: performance issues, patch notification system exploit…
Releasing when i finish everything
Made a pull request on my update of the animations =)
Nice. For future reference, next time you should:
- Make an issue before making a PR
- Make commits describing of what you did, such as “feat(animation): [what you did with animation]”
- Make PR name obvious of its purpose, for search optimisation purposes and to be clear
- Don’t add credits to yourself in script, your contributions and what you edited is visible already on GitHub
3 Likes
oh ok tysm im new on github loll (i think i fixed it now check it)
Hi EPHORIZE4LIFE,
to be honest there is really no point of having GitHub repo, we just have it to push the releases, but at the same time we could push releases in our own website (but GitHub in people’s eyes seems safer). Paulo’s pull request does not contain much and at the same time we don’t use our GitHub repo, so I would say even if there was a problem I would better see it here in this thread instead of unused GitHub code.
Best,
~ SG
2 Likes
Yes, I was just replying for future reference when making a PR in any repository, just because it looked like they weren’t too familiar with GitHub.
1 Like
uuhhh what if you want to make changes to the module, or even contribute???
also im so tired of you putting this when it literally shows your pfp and your name…
2 Likes