Force votes to be accepted

Discussion in 'Hosting Help' started by guenther, Nov 22, 2020.

  1. guenther

    guenther Registered

    Joined:
    Oct 5, 2018
    Messages:
    81
    Likes Received:
    71
    Hey everyone,
    is there a way to tell the server to auto-accept votes while only the admin or the server GUI can start ones?
    Thanks!
    Greetings,
    guenther
     
  2. Lazza

    Lazza Registered

    Joined:
    Oct 5, 2010
    Messages:
    9,442
    Likes Received:
    4,458
    Are you sure you need to start a vote in that case? You can probably just do what you're trying to do with an admin command, instead of voting.
     
  3. guenther

    guenther Registered

    Joined:
    Oct 5, 2018
    Messages:
    81
    Likes Received:
    71
  4. Woodee

    Woodee Registered

    Joined:
    Oct 4, 2010
    Messages:
    3,521
    Likes Received:
    614
    Call vote as admin should do it straight away I think. There is always an entry in the multiplayer.json that says something like votes can't be called if an admin is present.
     
  5. guenther

    guenther Registered

    Joined:
    Oct 5, 2018
    Messages:
    81
    Likes Received:
    71
    Already played around with that values, also I'm only calling the votes from the server itself, not the client GUI.
    Server basically ignores this commands.
     
  6. Woodee

    Woodee Registered

    Joined:
    Oct 4, 2010
    Messages:
    3,521
    Likes Received:
    614
    The dedi console should have next session buttons if you have access to that?

    [​IMG]
     
  7. guenther

    guenther Registered

    Joined:
    Oct 5, 2018
    Messages:
    81
    Likes Received:
    71
  8. Lazza

    Lazza Registered

    Joined:
    Oct 5, 2010
    Messages:
    9,442
    Likes Received:
    4,458
    I thought clicking buttons was just as easy as putting text commands in. I used the buttons where possible when running server automation tools, the commands were the plan B when a button wasn't available.
     
  9. guenther

    guenther Registered

    Joined:
    Oct 5, 2018
    Messages:
    81
    Likes Received:
    71
    Yeah, it's not that difficult to identify the button and click it. It's more tricky if the window hasn't the focus, as click events are invoked as actual mouse events with requiring the button to be real "clickable". And this causes the image to be required to be maximized, which is quite annoying.
     
  10. Woodee

    Woodee Registered

    Joined:
    Oct 4, 2010
    Messages:
    3,521
    Likes Received:
    614
    I see what you mean now.
     
    guenther likes this.
  11. Lazza

    Lazza Registered

    Joined:
    Oct 5, 2010
    Messages:
    9,442
    Likes Received:
    4,458
    I still don't follow, but I don't remember the dialog control manipulation I used. I was finding the server windows by name and then using standard windows coding to press the buttons by their ID - which for the most part didn't even change from rF1.

    It sounds like you're perhaps using a mouse control accepting language.
     
  12. guenther

    guenther Registered

    Joined:
    Oct 5, 2018
    Messages:
    81
    Likes Received:
    71
    Well, I'm using pywinauto, nothing exotic. The thing is only, that click events are always a mouse thing. And if your window is minimized/ hidden/ out of focus, this becomes a bit flaky.Thats my issue.
     
  13. Lazza

    Lazza Registered

    Joined:
    Oct 5, 2010
    Messages:
    9,442
    Likes Received:
    4,458
    Ok, yeah. My phone corrected 'scripting' to 'accepting' above, that might have been a bit confusing.

    I just had to revise what I was using (been a couple of years), I had an AutoIT script managing each dedi server window. I left each dedi instance up on screen (standalone server PC) so minimising wasn't an issue, focus didn't seem to affect functionality. It uses a command it calls ControlClick (takes the window handle, and a control ID). The notes do say sometimes controls will resist being clicked unless the window is already active, I never had an issue with that but I should say I had the script as a whole monitoring the window and keeping track of session status etc - so it was never going to try and restart the weekend or go to the next session at an inopportune time (like when the button may not be available) as it knew when the session had started etc.

    So sounds quite similar I would say (as far as how the languages manipulate the server dialog), perhaps a combo of the particular environment I was using being happier to stay responsive, and my rather in depth monitoring and logic that may have stopped it trying to do things at the wrong moment. Not sure.
     

Share This Page