ThermoDust 12 Posted September 23, 2016 Posted September 23, 2016 Is there a way to make it so access is not allowed from 2AM - 7AM? I tried but it complained about hours being greater.
ebr 16187 Posted September 23, 2016 Posted September 23, 2016 You can setup specific times that specific users can access the server so you just need to do the reverse. Can you explain exactly what you tried and what happened?
Happy2Play 9783 Posted September 23, 2016 Posted September 23, 2016 You can setup specific times that specific users can access the server so you just need to do the reverse. Can you explain exactly what you tried and what happened? @@ebr @@Luke Logic happened since the input become Allow access from 7am to 2am on a specific day and you can't do that as you are setting for example 7am Sunday to 2am Monday. So there is no way to grant access past midnight.
Happy2Play 9783 Posted September 23, 2016 Posted September 23, 2016 (edited) @@Luke Sorry you can't even set 7am to midnight since it is 12am and you get the same error, I see what you are saying you have to have multiple access times Midnight (12am) to 2am and 7am to midnight (12am) if we can get this to work. Or change to Everyday with two access times. Edited September 23, 2016 by Happy2Play
ThermoDust 12 Posted September 26, 2016 Author Posted September 26, 2016 I can't figure out the logic yet on how to pull this off. My goal is to restrict access between 2 and 7 am. I tried restrict 7AM to 12AM no go, then tried 7AM to 11PM with an additional 11PM to 2AM, no go. Plus for some reason it allowed me to add Sunday 7AM to 12AM the first time then when I tried to reproduce my process on another user it gave the error for time being greater. Is there a way you can add a switch to reverse the function to where it restricts based on the entered time?
ebr 16187 Posted September 26, 2016 Posted September 26, 2016 I think the issue is the fact that there are two 12ams and we aren't distinguishing between them properly. We could probably fix this quickly by making the last one be 11:59:59pm.
ThermoDust 12 Posted September 27, 2016 Author Posted September 27, 2016 Wouldn't it be easier to flip it and have it restrict based on the times given and not grant?
Luke 42083 Posted September 27, 2016 Posted September 27, 2016 No matter which one we choose someone is always going to suggest flipping it. This is what we decided to go with.
ThermoDust 12 Posted September 28, 2016 Author Posted September 28, 2016 Yes, but isn't it more logical to limit a smaller window than allow a larger one?
Luke 42083 Posted September 28, 2016 Posted September 28, 2016 Whether it's larger or smaller is entirely dependent on usage and will vary from one situation to the next.
ThermoDust 12 Posted September 28, 2016 Author Posted September 28, 2016 Then why not make a switch to offer both?
Guest asrequested Posted September 29, 2016 Posted September 29, 2016 Why not just allow us to type in the time? That way we can, as ebr suggests, type in 11:59:59. Wouldn't that simplify everything?
Happy2Play 9783 Posted September 29, 2016 Posted September 29, 2016 Looking at the policy.xml it is only looking at the hours 0-23. Tried modding the time in the xml but the time rollover doesn't work. It looks like rollover logic is need or adding 24 so you can set two access times 19 to 24 and 0 to 2. @@Luke there is the same dlgxxxxxxxxxxxxxx issues when a user tries to log in during restricted time. You have to click the Alert 6+ times to get it to go away.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now