Hi Sean!
Thanks for prompt answer.
Does it mean that after all Players disconnected I need to call RTSession.clearInterval() and RTSession.clearTimeout() for all active intervals in the script?
Ok.
Why in mentioned error does so simple message " "message": "Callback",". Usually, if a have any error in my code, I have more informative message.
Alexey Pozdnyakov
Hi!
I have a few questions:
1. What the strange message, in the realtime.log :
{
"_id": {
"$oid": "5888ca959650b504bc031f1f"
},
"server": "gsp-aeu-rt03",
"rtSessionId": "5888c78023791d04ca0b3d59",
"port": 5150,
"level": "FATAL",
"line": 289,
"source": "NewMatch.js",
"message": "Callback",
"connectedPlayers": {
"1": {
"tcp": "/203.80.210.134:48733",
"udp": "/203.80.210.134:46882",
"playerId": "5888b6c70a162ad63e84ad7d"
}
}
}
This message apears suddenly, and repeats many times.
And in this monent there are no clients connected.
2. How properly send message for specific peer in realtime API. In documentation mentioned that argument is array of integers
"signature setTargetPeers(Integer[] peerIds)"
In "Clock Synchronisation and Network Programming" tutorial setTargetPeers was called without arguments:
RTSession.newPacket().setData(rtData).setOpCode(101).setTargetPeers(packet.getSender().getPeerId()).send()
Thanks!