GetSessionId API about rust-server HOT 4 CLOSED

@justin-lovell The reasoning behind the user-flag is to cover the possibility of the gRPC server crashing. By moving this state into the mission, the gRPC can retrieve it again after being restarted.

from rust-server.

3. If no value exists then set the value to the current unixtime (since flags can only contain bool or numeric) using something like os.time(os.date("!*t")) and return the value.

Alternatively, the unixtime could also be retrieved inside of the Rust part of the implementation via OffsetDateTime::unix_timestamp. This way, there wouldn't be any additional Lua part necessary for this feature, as one could simply re-use the existing lua methods for GetUserFlag/SetUserFlag from Rust.

from rust-server.

The selection issue of the UserFlag number might be a problem (never know about a conflict?) (never mind, I had a relapse and confused it -- it can be a string)

You could probably just store this as a start-up variable (initialized OffsetDateTime::unix_timestamp) within Rust and just return it directly? No need to jump down into the mission environment.

If the mission ends and starts a new one, reset could be triggered with handler.onMissionLoadEnd() chain.

from rust-server.

Implemented by @vivanov

from rust-server.