Installation
Download the recent available file for this product via Axon. If you were using SCO v2 before SCO v3, it is important to note that the setup process has changed massively. If you're updating to SCO v3.1, you will need to reconfigure your items and operator barcodes.
The base file only includes the JSM SelfServ 7350. All other models and accessories are available on Axon, in the dropdown next to the Download button.
Trying to update your existing install? Check out our Update Guide instead.
1) Enable HTTP Requests
In Roblox Studio with your selected game open, click the 'Home' tab, then 'Game Settings'. Move to the 'Security' tab in the open window and make sure the slider for 'Allow HTTP Requests' is enabled and then hit 'Save'.
2) Product Insertion
Insert your file by 'dragging' the product file into Roblox Studio with your game fully loaded. The model is already ungrouped upon inserting so there is no need to ungroup.
Your game will need to be published for the product to work.
3) Folder and File Movement
You no longer need to move folders or files into ServerStorage, as the tills now automatically load everything in.
4) Whole System Configuration
Inside the JSM | SelfCheckout V3
folder, you will find the SystemConfig
script. Double-click it to be shown the different options that can be customised. This step will contain some features to elaborate, although the rest is annotated or self-explanatory.
- UITheme
- Maintenance
- InGameStaff
- If you set this to 'Custom', it will load your own theme from ServerStorage.
- If you set this to 'Default', it will load the commonly used JSM UI.
- We offer some additional themes created by other creators, check out the Themes page for information.
- It is important to note that not all self-checkouts support this feature.
- Some checkouts, not all, are presented with an 'on/off' button.
- This feature is used to disable interventions, e.g, help call, when a staff member is not present in-game to keep checkouts running
- You can control the
StaffThreshold
to set the bare minimum of staff required before disabling interventions
5) Operator Barcodes & Pins
Inside the JSM | SelfCheckout V3
folder, you will find the Accounts
settings script under Deploy
. You can manage the access level, operator ID and pins through this script.
Employee
- able to handle basic interventions, e.g, age approvalManager
- ability to close & open checkoutsAdministrator
- ability to access the system functions section
The ID in each account must be unique. To setup the actual operator barcode, click and open the tool. You'll find a function called "JSM | Operator Barcode". Within this function there is one attribute, "AccountID". Set this to the account id you previously made in the Accounts script.
6) Pick & Mix
We offer several types of different checkouts. Some checkouts differ, such as the scanner or the ability to accept cash. Different models of checkouts, such as SelfServ 90 need to be downloaded from Axon. You can find them in the dropdown next to the Download button.
- To duplicate (create more) of a certain self-checkout, click the checkout and hit
CTRL + D
- Ensure the new self checkout is in the
Terminals
folder. This is also important if you're inserting new models. - For your new checkout, open its path on Explorer and double-click
Settings
. - Set the
LaneNumber
to another unique number that hasn't been used by any other self-checkouts.
You can also adjust the CardOnly
feature to disable cash payments. The StartMode
feature has 4 different labelled options, used to control the boot process when the game starts.
If you fail to set the LaneNumber
to something unique, your checkout won't boot.
7) Adding Items
The Calgon is an example item. You can use the example item to copy and paste the configuration to add items, or use the instructions given below. It is important to note that once a product has been scanned & bought, the customer won't be able to rescan that specific item.
- Copy the bindable function from the example item into your item.
- In properties, you'll see 5 attributes. The
AgeRestricted
attribute determines if a product is age restricted. TheCost
attribute should be set to the price of your product. EASActive activates your JSM EAS if a product has not been paid for. This is only for customers who own the JSM EAS/anti-theft gates. ItemImage should be set to the asset id of the image you want to set for your item. LoyaltyCost is the price of the item when a Loyalty Card has been scanned.
The name of the Bindable Function is JSM | Item Data
, it should have 5 attributes:
- AgeRestricted (Boolean)
- Cost (Number)
- EasActive (Boolean)
- ItemImage (String:
rbxassetid://...
) - LoyaltyCost (Number)
JSM EAS is currently incompatible with JSM Self Checkout v3.1. This means that the EASActive attribute will not work. We are working on resolving this and thank you for your patience.