Variables sync about skungee

[TheLimeGlass]

You can't do this with it's own Syntax or Configuration, but you can set up indices to grab from.

set {_server} to current server
set network variable {server::%{_server}%::something} to "something"

#getting
set async {_something} to network variable {server::%{_server}%::something}

[Tyberhertz]

I have now tried to customize a script for your script but somehow it is not yet ..

logfile:
[18:23:23] [Thread-195/INFO]: [Skungee] Recieved packet: UPDATEVARIABLES with data: proxy.playerdata..punkte with settable data: [type=string, data=[-128, 1, 49]]

error:
[17:44:06] [main/INFO]: [CHAT] {_server} can only be set to one object, not more (sync.sk, line 79: set {_server} to current server')

Skript:

on quit:
	set network variable {proxy.playerdata.%{_uuid}%.punkte} to "%{playerdata.%{_uuid}%.punkte}%"


on join:
	set async {playerdata.%{_uuid}%.punkte} to network variable {proxy.playerdata.%{_uuid}%.punkte}

[TheLimeGlass]

Ok there are a few issues.

1.) A variable sync feature between servers is an enhancement, added enhancement lable.

2.) There is a bug where the current server syntax returns multiple rather than single, added bug label.

3.) In your script you provided, you're not setting the local variable {_uuid} before you use it, so you're setting a blank variable you will never be able to grab again, creating wasted space in the database.

[TheLimeGlass]

The multiple return error has been fixed in 1.1.0

[TheLimeGlass]

And the variable sync suggestion is a duplicate of #34