There's no contesting that ROBLOX programmers often fail to implement program architectures that make their games easily scalable and maintainable. Frequently our first compulsion when scripting is to slap a script into whatever we intend to program. Doing this seems convenient at first, but it has a few inherent disadvantages:
- The script lives in the workspace and is therefore vulnerable to accidental deletion.
- It can be difficult to find as the game grows.
- You will often end up with lots of copies, each of which you will have to update when you want to make even a single-line change.
The longer a project goes on, the more these sloppy practices tend to bite you in the butt. You’ve got hundreds, potentially thousands, of lines of duplicate code that are neither interconnected nor easily serviceable. Preferably, your code should be more like a framework than a hodge-podge of batch scripts if you plan to make that murder clone you have in mind.
Allow me to introduce you to something called MVC.
MVC, or Model-View-Controller, was developed during the 1970s as a modular way to write graphical user interface software. It has three components that do distinct jobs; they are as follows:
Model: The code that defines the behavior and data of an object
View: The code that defines the user interface
Controller: The code that communicates actions to the model when something happens in the view, and vice versa
In the case of ROBLOX, you don't have to write the code for the GUI, because it's already been made for you: it's known as the workspace. It may seem a bit strange, then, to use MVC for making games, but bear with me.
Since the View has already been done for you, you are left to write Model and Controller.
Last challenge was to re-create the game "SUPERHOT", and we had a total of 4 people submit their creations, in order of the first to submit to the last:
I had an extreme amount of trouble trying to decide who should win, therefor, everybody is a winner! All 4 winners shall get the snack break tag for a week. Good luck on the next snack break!
There hasn't been a snack break in a little bit, so let's get it going with an "intermediate" task for those who would like to try! The challenge shall be to recreate the base (or more if you want extra points!) of the game SUPERHOT.
If you haven't heard of SUPERHOT, I will try to explain it as best I can, however it is advised for you to look up a video of it if you haven't heard of it before. In SUPERHOT, time only moves when you do. When standing still, and not looking around, time will move extremely slow. However, as soon as you start moving, the world around you will also begin moving. The objective of SUPERHOT is to use your ability to do things like line up shots, dodge bullets, and more.
You can create purely the slowing down dynamic, you don't need to create enemies/weapons if you do not want to. However, you must be actually able to showcase the dynamic.
When you submit your game, make sure it's uncopylocked!
The person who I deem completed the challenge the best will get the snack break badge until the next snack break (badge can be seen here). Everyone who completes the challenge will be mentioned on the next snack break post.
You can submit your game by messaging me on ROBLOX. Good luck!
Recently ROBLOX introduced an update to increase the protection of each ROBLOX game. This update includes the following security measures:
All games that do not have Filtering Enabled toggled shall have an age requirement of 13 to join.
Any place where text may be inputted in your game will now be required to have Text Filtering applied to it. Any game that does not have this feature will be put under review until it is added, however, it will not be content deleted, and no moderation action will be taken against the place owner's account.
What does this mean for us as developers?
As many of you know, a large portion of ROBLOX's community is under 13. In order to ensure your game is accessible by the entire community, you will have to make it within compliance of these two updates. While doing so, you may find these two articles helpful:
Scripting Helpers is looking to fill more volunteer positions in our team again this year.
We're looking for the following roles:
- General administrator
- Blog author
- Question moderator
- Events coordinator
- Forum moderator
- Website developer
...or, if you feel you have something new to bring to Scripting Helpers, feel free to apply too! Any and all exceptional applications will be considered for any role.
A Discord account is required to apply and fill a staff position.
Applications closed 22 January 2017.
We finally have a forum for anyone who wants to get meta about Scripting Helpers. You can find it here:
The forum uses third-party software but it is configured so that your Scripting Helpers account is automatically used when you visit. As an added bonus, the forum website has a built-in chat system so as a side effect Scripting Helpers now has user-to-user messaging for anyone who clicks the forum link. Neat.
Deprecation is a topic you'll hear often. Everyone will tell you that deprecated items should be avoided, but why?
Objects, properties, methods or events that become deprecated could be removed at any time by ROBLOX, because you're not suppose to be using them anymore anyways. Normally deprecated items aren't removed instantly to give people time to become used to new methods, or so they don't break older games.
Hello everyone! I hope you are all having a great holiday and end to this interesting and eventful year. I want to take a moment and talk about everyone's favorite currency for a moment: Scripting Helpers reputation.