Make per-user: MAX_CHAIN_DOCKING & MAX_CORES

    Erth Paradine

    Server Admln & Bug Reporter
    Joined
    Feb 15, 2016
    Messages
    239
    Reaction score
    58
    Request:
    Move the MAX_CHAIN_DOCKING server setting to a per-user setting, with server-wide default/minimum.
    Add support for a per-user MAX_CORES setting, with server-wide default/minimum. Enforce at times: blueprint spawn, fleet command/configuration, and root core entry.

    Currently:
    MAX_CHAIN_DOCKING has no truly effective use. Most docking chains vary from 3-9 layers deep, and there's no way to prevent abuse by newer players, while equally permitting more flexibility for mature/non-abusive players.

    MAX_CORES has no existing equivalent. On more than one occasion abusive players have created completely new accounts, and within hours of logging into the server have created and launched what they call a "bomb": 200+ core entities on rotator and/or rail dockers, logic-triggered, designed for nothing but causing whole-server lag - causing server instability and griefing our non-abusive players.

    Result of proposed:
    • The overall goal here is to minimize the impact of abusive/griefing players.
    • Organized teams of abusive players have logged-in, consolidated resources, and then proceed to grief.
    • By limiting cores on a per-player basis, we could grant more mature/seasoned players the ability to both spawn and fly larger and/or more complicated ships. While newer players would need to earn this privilege.
    • This also makes room for a "skill" mechanic often found in RPGs, where players must earn the privilege of flying larger and/or more complicated ships.

    Suggested Method:
    • Enforce MAX_CHAIN_DOCKING as a per-user setting.
    • Add support for and enforce MAX_CORES as a per-user setting.
    • Enforcement times: prevent blueprint spawning if core count exceeds permitted number, deny entry into root core if whole-entity core count exceeds permitted value, deny fleet configuration/creation if total core count exceeds permitted number.
    Rationale:
    • To minimize the impacts of newer abusive players, abusive/griefing teams, etc.
    • Help improvement overall enjoyment of the game by non-abusive players.
    • Reduce administrative overheads.
     
    • Like
    Reactions: Lukwan

    nightrune

    Wizard/Developer/Project Manager
    Joined
    May 11, 2015
    Messages
    1,324
    Reaction score
    577
    • Schine
    • Top Forum Contributor
    • Thinking Positive
    Can that person just not use a ship that was built by someone else with larger chains?

    How does docking with a public station work?
     

    Erth Paradine

    Server Admln & Bug Reporter
    Joined
    Feb 15, 2016
    Messages
    239
    Reaction score
    58
    Can that person just not use a ship that was built by someone else with larger chains?

    How does docking with a public station work?
    Wouldn't that be covered by "...deny entry into root core if whole-entity core count exceeds permitted value..."

    For counting cores, especially for topics such as public stations, how about counting from the docked entity outwards. This enables newer pilots (e.g. those with lower permitted core counts) to still control turrets on larger ships, whereas they haven't yet earned enough skills to control the entire ship. For an example of a similar mechanic already working in-game, cameras on factioned stations with personal flag cannot be entered by other faction members.