Once closed the Invites Screen, no more invites from the same Group are possible until relog.
Not sure, for what "Epoch_invited_GroupUIDsPrev" should be needed. Noticed no disadvantages by not compare it here
- Server was looking for Players with Groupuid after the UID was already set on the new member self. So the Player was sometimes found as first and has joined his own Group
- [["groupUidUpdate", _groupID], _x] call EPOCH_sendRemoteExecClient; was missing, so the Player had to relog to get the Groupuid variable -> Leaving group was also only possible after Relog
- added usage of params []
[Added] epochconfig settings (forcedVehicleSpawnTable,
forcedLootSpawnTable) to force specific vehicle or loot tables.
[Changed] Removed "Alpha" from debug monitor
[Changed] Add flag to enable database unit test. enableUnitTestOnStart =
1 in epochconfig.hpp to enable
Update redis-server.exe to latest version: 3.2.100 from:
https://github.com/MSOpenTech/redis/releases
More accurate to define for Players (bugging through a wall and falling down or hanging stuck in a corner)
In EPOCH 0.4, ServerVars was set to [""] in case of wrong _varscount.
If you have it on your character, you are not able to set SpawnPoint.
SO I added a check, if spawnlocation isequaltype []
More accurate to define for Players (bugging through a wall and falling down or hanging stuck in a corner)
In EPOCH 0.4, ServerVars was set to [""] in case of wrong _varscount.
If you have it on your character, you are not able to set SpawnPoint.
SO I added a check, if spawnlocation isequaltype []
More accurate to define for Players (bugging through a wall and falling down or hanging stuck in a corner)
In EPOCH 0.4, ServerVars was set to [""] in case of wrong _varscount.
If you have it on your character, you are not able to set SpawnPoint.
SO I added a check, if spawnlocation isequaltype []
