Player data isn't always loading

[Limited_Unique]

local DataStore2 = require(1936396537)
local defaultWins = 0
local players = game:GetService("Players")

players.PlayerAdded:Connect(function(player)
	local WinsDataStore = DataStore2("WinsDataStore")
	WinsDataStore.Parent = player
	local PointsDataStore = DataStore2("PointsDataStore")
	PointsDataStore.Parent = player
	
	local varFolder = Instance.new("Folder")
	varFolder.Parent = player
	varFolder.Name = "vars"

	local playerAlive = Instance.new("IntValue")
	playerAlive.Parent = varFolder
	playerAlive.Name = "playerAlive"
	playerAlive.Value = 0


	local leaderstats = Instance.new("Folder")
	leaderstats.Parent = player
	leaderstats.Name = "leaderstats"

	local wins = Instance.new("IntValue")
	wins.Parent = leaderstats
	wins.Name = "Wins"

	local points = Instance.new("IntValue")
	points.Parent = leaderstats
	points.Name = "Points"

	local function winsUpdate(value)
		wins.Value = WinsDataStore:Get(value)
	end

	winsUpdate(defaultWins)

	WinsDataStore:OnUpdate(winsUpdate)

	local function pointsUpdate(value)
		points.Value = PointsDataStore:Get(value)
	end

	pointsUpdate(0)
	WinsDataStore:OnUpdate(pointsUpdate)
end)

PSA: Don't use Instance.new() with parent argument

I’ve discovered a pretty bad performance issue in one of top games that has to do with Instance.new and wanted to write about this, since this is not obvious unless you know the system inside out. Tthere are several ways to create a ROBLOX object in Lua: local obj = Instance.new(‘type’); fill obj fields local obj = Instance.new(‘type’, parent); fill obj fields local obj = util.Create(‘type’, { field1 = value1, … }) If you care at all about performance, please only use the first option - I wi…

Your issue was that you were using the “Parent” parameter of “Instance.new()”, it’s strongly advised that you shouldn’t use it & instead opt to set the “Parent” property explicitly as I did.