Skip to content
Snippets Groups Projects
  • Auke Kok's avatar
    c5c727d6
    Allow NodeTimer, ABM and block mgmt interval changes. · c5c727d6
    Auke Kok authored
    ABM's are hardcoded to run every 1.0s, NodeTimers are hard coded to
    run at every 1.0s. Block mgmt is running every 2.0sec.
    
    However, these timers can be better tuned for both higher and lower
    values by server owners. Some server owners want to, and have the
    resources to send more packets per second to clients, and so they
    may wish to send smaller updates sooner. Right now all ABM's are
    coalesced into 1.0 second intervals, resulting in large send queues
    to all clients. By reducing the amount of possible timers, one can
    get a far better response rate and lower the perception of lag.
    
    On the other side of the camp, some servers may want to increase
    these values, which again isn't easily doable.
    
    The global settings abm_interval and nodetimer_interval are set to
    current values by default. I've tested with 0.2/0.5 type values
    and noticed a greatly improved response and better scattering of
    nodetimers, as well as enjoying not faceplanting into doors with
    pressure plates anymore.
    c5c727d6
    History
    Allow NodeTimer, ABM and block mgmt interval changes.
    Auke Kok authored
    ABM's are hardcoded to run every 1.0s, NodeTimers are hard coded to
    run at every 1.0s. Block mgmt is running every 2.0sec.
    
    However, these timers can be better tuned for both higher and lower
    values by server owners. Some server owners want to, and have the
    resources to send more packets per second to clients, and so they
    may wish to send smaller updates sooner. Right now all ABM's are
    coalesced into 1.0 second intervals, resulting in large send queues
    to all clients. By reducing the amount of possible timers, one can
    get a far better response rate and lower the perception of lag.
    
    On the other side of the camp, some servers may want to increase
    these values, which again isn't easily doable.
    
    The global settings abm_interval and nodetimer_interval are set to
    current values by default. I've tested with 0.2/0.5 type values
    and noticed a greatly improved response and better scattering of
    nodetimers, as well as enjoying not faceplanting into doors with
    pressure plates anymore.