Skip to content
This repository has been archived by the owner on Aug 20, 2021. It is now read-only.

[Feature Request] Star/Stop Recording Functions #23

Open
byjokese opened this issue Sep 17, 2017 · 7 comments
Open

[Feature Request] Star/Stop Recording Functions #23

byjokese opened this issue Sep 17, 2017 · 7 comments

Comments

@byjokese
Copy link

byjokese commented Sep 17, 2017

A great idea would be to create a couple of functions for starting and stopping the recording. This way we can skip some moments of the missions that are not interesting, like people joining to an event, it may take 10-20mins for some big missions and co-op missions between clans to get started.

So having this possibility can be quite interesting. And should not be very complicated to implement over what is already done.

EDIT: I haven't seen them, maybe are already planned or implemented.

@alexcroox
Copy link
Owner

alexcroox commented Sep 17, 2017

Thanks for the suggestion! You'll be pleased to hear this is already in master/the version you are running. Just set this variable on the server in admin console or as part of your mission framework: aar_main_logEvents = false

Then set it back to true when you are ready to continue logging events.

@byjokese
Copy link
Author

each time is set to true it will create a new record on the DB, right? It Won't add them to the previous session, will it?

@alexcroox
Copy link
Owner

It won't create a new mission, it will simply pause or resume the logging of events to the same mission entry

@byjokese
Copy link
Author

byjokese commented Sep 17, 2017

So, there's no way for creating a new entry manually, unless restarting the mission. Copy.

What our group does normally are persistent missions, so we don't restart the server/mission. And we wanted to record only the mission itself, not the time in between missions. But even pausing it will create a quite long log of events as it can take a couple of weeks (6-7 missions until we restart).

Thanks for the info.

@alexcroox
Copy link
Owner

Ah makes sense, this is something I might add to the rewrite (currently going on in a different branch)

@byjokese
Copy link
Author

byjokese commented Sep 17, 2017

As you consider, it can be interesting.

Thanks for all.

@alexcroox
Copy link
Owner

I'm still interested in doing this and had a cursory look this evening, however it turned out to be a lot more complicated than I initially thought. We would have to loop through every unit and remove all their existing R3 variables before re-initialising. Not impossible, just time consuming to implement.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants