(post no longer available)

Help and Feedback Scripting Support
, ,
1

This post is old and no longer being updated.

2

I’m not 100℅ sure too but this is what i recommend. Add a print within your button.Activated connection to see if its multi-firing. Print the counter value on the client within the updatePlayerCount. Lastly, please remove the waits within the event in your serverscript they server no purpose. Also, print “counterValue.Value” on the server

1 Like
4

When you fire updatePlayerCount on the server just change the counter on the client

5

Now it seems to be doing this:

6

Its a two player only server right?

7

Yeah. I have no other servers that allow for more or less players.

8

A different approach that will 100% work.

  1. Set attribute under replicated storage
  2. Update this on the server

The code below is in a script under a text label. If in a serverscript you switch this attribute it will update to all players. You can change this code so It fits your script.

local Players = game:GetService("Players")
local RS = game:GetService("ReplicatedStorage")
	
	
RS:GetAttributeChangedSignal("ReadyPlayers"):Connect(function(...: any) 
	local ReadyPlayers = RS:GetAttribute("ReadyPlayers")
	local TotalPlayers = #Players:GetPlayers()
	
	local Str1, Str2 = tostring(ReadyPlayers), tostring(TotalPlayers)
	
	script.Parent.Text = Str1.. " / "..Str2
end)
9

This line is accessing a Counter unique to each player, not shared.
If that was someplace like; workspace.data.Counter they would share it.

11

So if I were to make a global value on the server, would the counter update through all player’s respective Guis?

12

Maybe … I just use data on the workspace. Don’t see why what you said wouldn’t workout.

13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.