Search the Community
Showing results for tags 'grad'.
Found 2 results
[Request] GRAD Persistence + ace medical
FenixDK posted a topic in ARMA 3 - MISSION EDITING & SCRIPTINGHI everyone, I wanted to start this thread, because I am sure I am not the only one who faces this problem and I think it will be beneficial for many out there, as not everyone is using a proper database to save the mission progress, so I think it would be great if someone who knows how to do it will contribute. It has to be noted that even though I have close to 0 experience in programming, I am fully aware of how much effort this request may require, but I believe in altruism 😊. Setup: GRAD Persistence and advanced ace medical system. Problem: GRAD does not save ace medical state of the player upon disconnect/return to lobby, which means if the player is injured or unconscious, he can return to lobby and then get back in the mission fully recovered. Possible solutions (from easiest to hardest): 1. A script that will disable “abort” button if the player is unconscious. Something like this (I didn’t test it yet, but I will do so today). This is a workaround which does not really solve the problem as alt+F4 is still available, but it will reduce the number of returns to lobby. I guess that I can play around on my own with the script referred above and adjust it to recognise ace unconscious, but if there is a more elegant solution, it would be great. 2. A script/addition to GRAD that will save ace unconscious parameter before player leaves to lobby/quits and upon player’s return will either set the player unconscious or kill (I think the kill is better and more fair as it will exclude healing the wounds upon return). 3. An addition to GRAD that will save ace medical wounds and unconscious state before player leaves to lobby/quits and upon return will load the saved state. I know that this is will require a lot of time to implement, as GRAD developer has it in his backlog since 2018. 4. Feel free to add your option in this thread. Result: Whichever solution we will figure out here, it will be for everyone to use. If it will be possible to implement it in GRAD Persistence, I will reach out to the developer with this solution, so others can enjoy it in the GRAD package as well.
Trying to save variables within GRAD Persistence
Robert Tyburne posted a topic in ARMA 3 - MISSION EDITING & SCRIPTINGTrying to use GRAD to save a variable, which is to be referenced after the mission is restarted to be used as part of an if-then statement to simply delete the zone since it's already been cleared by players. The effect I'm going for is simple, which is a progression of clearing sectors by deleting marker areas (EOS zones) and planting a flag marker saying it's secure once the players destroy an object (like a transmitter). That so far has been simple enough: I'm attempting to set a public variable in the missionNameSpace, as that's what I think GRAD wants in order to save it properly. GRAD Config: For reference, the config is saving vehicles, containers, and markers created during the mission. Player position and inventory is also saved, in addition to credit count as I'm also using GRAD money menu. I use a remoteexeccall to get the save function to go, which hasn't failed yet with all the other data. Once the mission restarts, the following code is run from a separate .sqf called from the initServer.sqf I've also tried combinations of "safyrahnorth" == 1 and safyrahnorth == 1, but the error is that the variable is undefined. If I run the same scripts in the same session, it all executes fine. It's as if the variable "safyrahnorth" is getting destroyed as soon as the server shuts down, which makes me think I'm not executing the GRAD variable save correctly. I'm unclear on where I'm going wrong, and some extra eyeballs would be greatly appreciated. Or suggestions on approaching this differently.