Scripting Helpers is winding down operations and is now read-only. More info→
Log in to vote
1
Will this spawn multiple models in one space?
Hey guys, I have a question.
01 | local function setupPlayerData(player) |
02 | local data = DataStore1:GetAsync(player.UserId) |
03 | if not data then |
04 | data = {Items = {}, Money = 0, Experience = 0} |
05 | DataStore1:SetAsync(player.UserId, sessionData[player]) |
06 | end |
07 | sessionData[player] = data |
08 | end |
09 |
10 | game.Players.PlayerAdded:connect(setupPlayerData) |
11 |
12 | local function savePlayerData(player, playerItems) |
13 | for i, v in ipairs(workspace[player.Name].itemHolder) do |
14 | sessionData[player].Items[v.Name] = { |
15 | CFrameValues = {v:GetPrimaryPartCFrame().X, v:GetPrimaryPartCFrame().Y, v:GetPrimaryPartCFrame().Z, v:GetPrimaryPartCFrame():toEulerAnglesXYZ()} |
16 | } |
17 | end |
18 | DataStore1:SetAsync(player.UserId, sessionData[player]) |
19 | end |
I have a three by three grid that saves every sixty seconds (or, one minute.) Once the game saves twice with a part unmoved, on the next game join, will there be three parts in the same location?
If so, how would I prevent that?
Baseplate loading code:
1 | function loadPlayerData(player) |
2 | for i, v in ipairs(sessionData[player][Items]) do |
3 | local Base = workspace:WaitForChild('Baseplates'):WaitForChild(player.Name) |
4 | local Item = game:GetService'ReplicatedStorage':WaitForChild('gameItems'):FindFirstChild(sessionData[player].Items[v.Name]):Clone() |
5 | Item.Parent = Base:WaitForChild("itemHolder") |
6 | Item.CFrame = CFrame.new(sessionData[player].Items[v.Name].CFrameValues) |
7 | end |
8 | end |
9 | game.Players.PlayerAdded:connect(loadPlayerData) |
There might be errors I'm not aware of. I'll fix these errors while someone comes up with an answer.
0
I do not understand your question. ILikeTofuuJoe 1 — 7y
0
Alright. In a model (which there is FOUR of), there are two items inside. itemHolder, and the actual baseplate. Everytime someone places an object down, nothing happens. Every autosave, the game gets EVERYTHING in the user's baseplate, and saves it. If someone leaves (because if someone leaves, it autosaves also), would it spawn multiple parts in the same area on join? Fifkee 2017 — 7y
0
There would probably not be any diffrences though, the models are the same and they overlap. ILikeTofuuJoe 1 — 7y
0
Sell crates are taken into consideration, that's the problem. If two sell crates are in one position, then double the money from one sell crate. That would be kind of overpowered in the long run. Fifkee 2017 — 7y
0
Agree. They could get a lot of money by keep quitting and joining the game. ILikeTofuuJoe 1 — 7y
1 answer
Log in to vote
0
Yes. It will. EDIT: Add this
1 | game.Players.LocalPlayer.modelSpawned = true |
Add a part of the script that would detect if modelSpawed is true. If it is then probably do a return end) . Also set modelSpawned to false when the player first joined.
0
then, how would I prevent it? Fifkee 2017 — 7y
0
@ILikeTofuuJoe This is an irrelevant answer. If you're going to post an answer, provide how it's done and explain. SilverCreeper58 23 — 7y
0
So it didn't say anything about not letting the player spawn more models. ILikeTofuuJoe 1 — 7y
0
Don't try to get free reputation points, I literally commented "how would I prevent it?" aeiou Fifkee 2017 — 7y
View all comments (2 more)
0
By making a thing that would change a value to true. And if the value is true, make it so that the players can't spawn any more models. ILikeTofuuJoe 1 — 7y
0
I am certainly not getting free reputation. I have 0 reputation ok. A lot of my answers have errors in them. I just hope I don't get negative reputation. That's it. ILikeTofuuJoe 1 — 7y