Results 1 to 2 of 2

Thread: Persistent dedicated server step by step walk through?

  1. #1
    Kart Driver
    Join Date
    Dec 2015
    Posts
    18
    Platform
    PC

    Persistent dedicated server step by step walk through?

    Hi folks,

    I'm having a bit of a nightmare trying to setup a server controlled persistent dedicated sever that will display in PC mp session list on windows server 2012. Is there anywhere that has a step by step walk through to achieve this?

    I can connect to the server ok when the server does not control the game settings, tracks etc.

    Any help would be greatly appreciated..

    Regards,

    WOPR




    Code:
    
    //////////////////////////
    // Basic server options //
    //////////////////////////
    
    
    logLevel : "info"
    
    eventsLogSize : 10000
    
    name : "TEAM-53-RACING"
    
    secure : true
    
    
    password : "removed"
    
    maxPlayerCount : 32
    
    bindIP : "removed"
    
    steamPort : 8766
    hostPort : 27015
    queryPort : 27016
    
    sleepWaiting : 250
    sleepActive : 10
    
    
    
    ///////////////////////////
    // HttpApi configuration //
    ///////////////////////////
    
    // This provides http-based API and basic web-based controls using a built-in http server.
    // HttpApi is disabled by default, and if you enable it with everything else left to default it will listen only locally on 127.0.0.1:9000
    
    // Master enable/disable toggle.
    enableHttpApi : true
    
    // Similar to logLevel above but used only for libwebsockets output.
    // Note that all logging still goes through the main filter, so you won't be able to use more verbose logging here than the main level.
    httpApiLogLevel : "warning"
    
    // Interface name or IP where to bind the local http server providing the API and web-based controls.
    // This is the textual name of the interface as assigned by your OS, or IP address of the interface.
    // The default value is "127.0.0.1", change it to an empty string to bind the listen socket to all available interfaces.
    httpApiInterface : "127.0.0.1"
    
    // Port where the local http server listens.
    httpApiPort : 58000
    
    // Map with extra HTTP headers to add to HTTP API responses.
    // The keys are the conditions for adding the headers, the values are the headers to add.
    // There are no conditions supported yet, so just use "*" for a generic wildard for now, that will match everything in the future too.
    httpApiExtraHeaders : {
        "*" : "Access-Control-Allow-Origin: *"
    }
    
    // Http API access level overrides.
    // Each HTTP API endpoint defines its default access level, usually one of "public", "private" or "admin".
    // This map can override these levels to anything else. The keys are wildcard endpoint paths, and the values are the
    // access levels to use. The first path that matches will be used, processing them in the order as written here.
    // The wildcard patterns are case-sensitive and can contain:
    // - '*': matches 0 or more characters
    // - '%': matches 0 or more characters except for forward slash
    // - '?': matches 1 character
    httpApiAccessLevels : {
        // The default is empty, using defaults as defined by the endpoints themselves.
    
        // But you could for example use this to change all access levels to public (not recommended!)
        // "*" : "public"
    
        // Or this to hide the status from public
        // "" : "private"
        // "status" : "private"
    
        // And similar to hide the help and lists from public
        // "api/help" : "private"
        // "api/list*" : "private"
    
        // As you can see from the example above, the paths should be written with no initial or trailing slashes.
    }
    
    // Filtering rules for the access levels.
    // The default access levels are "public", "private" and "admin", but the httpAccessLevels above can define any additional levels.
    // This map then tells the server who has access to which level. It's a map from level names to filtering rules.
    //
    // Filtering rules are then specified as a list of structures, processed in the order as written in the config.
    // Each rule structure contains a type" and then type-specific fields. The supported types are:
    // - "accept": Accept this request, no additional checks.
    // - "reject": Reject this request, no additional checks.
    // - "reject-password": Reject this request and let the client know that a password is required, no additional checks.
    // - "ip-accept": Accept this request if it matches the "ip" mask in CIDR notation (for example, "192.168.1.0/24")
    // - "ip-reject": Reject this request if it matches the "ip" mask in CIDR notation (for example, "192.168.1.0/24")
    // - "user": Accept this request if it authenticates as given "user".
    // - "group" : Accept this request if it authenticates as given "group".
    //
    // User/group authentication is done using the standard HTTP basic access authentication (https://en.wikipedia.org/wiki/Basic_access_authentication).
    httpApiAccessFilters : {
    
        // Public rules. The default is to accept everything.
        "public" : [
            { "type" : "accept" }
        ],
    
        // Private rules. The default is to accept queries from localhost, queries authenticated as users in the "private" group
        // and to reject anything else.
        "private" : [
            { "type" : "ip-accept", "ip" : "37.59.46.152/32" },
            { "type" : "group", "group" : "private" },
            { "type" : "reject-password" }
        ],
    
        // Admin rules. The default is to accept queries from localhost, queries authenticated as users in the "admin" group
        // and to reject anything else.
        "admin" : [
            { "type" : "ip-accept", "ip" : "37.59.46.152/32" },
            { "type" : "group", "group" : "admin" },
            { "type" : "reject-password" }
        ],
    
    }
    
    // User list. Map from user names to passwords, in plain text.
    httpApiUsers : {
        "removed" : "removed",
        "removed" : "removed",
    }
    
    // User groups. Map from group names to lists of users in said groups.
    httpApiGroups : {
        "private" : [ "removed", "removed" ],
        "admin" : [ "removed", "removed" ],
    }
    
    
    //////////////////////////
    // LuaApi configuration //
    //////////////////////////
    
    // Lua API allows the server to be extended by in-server scripting in Lua.
    // The server is running Lua version 5.3, currently with no sandboxing applied to the add-ons. All standard Lua library functions are available.
    
    // WARNING: The LuaApi is not final and the following breaking changes are planned soon:
    // - Rename Lua addon metadata files from *.txt to *.json
    // - Remove default config from the metadata and put it into separate file *_default_config.json
    // - Separate config and persistent data, so that data saved by addons will not pollute the config files, and the config files will retain all comments from the default files.
    
    // Master enable/disable toggle.
    enableLuaApi : true
    
    // Root directory from which the Lua addons are loaded. Relative to current directory if it's not absolute.
    luaAddonRoot: "lua"
    
    // Root directory where the addon configs will be stored if written out by addons. Default configs are defined in the addon base text files.
    luaConfigRoot: "lua_config"
    
    // Root directory where the addon output will be written, once supported. For now the io functions can write anywhere, but this will be limited to this directory in the future.
    luaOutputRoot: "lua_output"
    
    // Names of all Lua addons to load. The addons will be loaded in the specified order. Each addon can list other addons as its dependencies, which attempt to load those first.
    // The server will load addons from directory specified in "luaAddonRoot", loading of each addon will start by loading its config from ADDON_NAME/ADDON_NAME.txt
    luaApiAddons : [
    
        // Core server bootup scripts and helper functions. This will be always loaded first even if not specified here because it's an implicit dependency of all addons.
        "sms_base",
    
        // Automatic race setup rotation.
        "sms_rotate",
    
        // Sends greetings messages to joining members, optionally with race setup info, optionally also whenever returning back to lobby post-race.
        "sms_motd",
    
        // Tracks various stats on the server - server, session and player stats.
        "sms_stats",
    ]
    
    
    ////////////////////////////////
    // Game setup control options //
    ////////////////////////////////
    
    
    allowEmptyJoin : true
    
    controlGameSetup : true
    
    // Initial attribute values, see /api/list/attributes/session for the full list.
    // These attributes will be used when joining an empty server via the borwser (if allowEmptyJoin is true) and as the intial attributes for the set_attributes and set_next_attributes APIs (if controlGameSetup is true)
    // The defaults set these values:
    sessionAttributes : {
        // The host player can control track selection if set to 0. Set to 1 to disable track selection in the game.
        "ServerControlsTrack" : 1,
    
        // The host player can change the vehicle class by going through the garage if set to 0. Set to 1 to disallow players changing the class.
        // Flag FORCE_SAME_VEHICLE_CLASS (1024) should be also set for this to make sense, otherwise players are able to choose cars from any class.
        "ServerControlsVehicleClass" : 1,
    
    
        "ServerControlsVehicle" : 1,
    
        
        "GridSize" : 32,
        "MaxPlayers" : 20,
    
    
        "Practice1Length" : 20,
        "Practice2Length" : 0,
        "QualifyLength" : 30,
        "WarmupLength" : 0,
        "Race1Length" : 15,
    
     
        "Flags" : 132376,
    
       
        "OpponentDifficulty" : 75,
    
        
        "DamageType" : 3,
    
       
        "TireWearType" : 6,
    
        "FuelUsageType" : 0,
    
        "PenaltiesType" : 1,
    
        "AllowedViews" : 2,
    
        "TrackId" : 354022214,
    
        "VehicleClassId" : -112887377,
    
        //"VehicleModelId" : 274862187, 987814806, 1161219858, 1353949246, 1401532035, 1452261378, 1884411907, -2025231366, -2020758805, -1365918055, -1170674276, -1166911988, -384044277, 
    
        "DateYear" : 2017,
        "DateMonth" : 5,
        "DateDay" : 22,
        "DateHour" : 13,
        "DateMinute" : 0,
    
    
        "DateProgression" : 1,
        "ForecastProgression" : 1,
    
        "WeatherSlots" : 1,
        "WeatherSlot1" : -934211870,
        "WeatherSlot2" : -934211870,
        "WeatherSlot3" : -934211870,
    }
    
    blackList : [ "blackList.cfg" ]

  2. #2
    Kart Driver
    Join Date
    Dec 2015
    Posts
    18
    Platform
    PC
    the server is showing in the server list ok

    TEAM-53-RACING Available 0/25 Password is required to join the server Users must be whitelisted Server is protected by VAC Windows 1.0.1.37

    I have also set the create game settings same as the ds config file?

    What could be the issue?

    Kind regards

Similar Threads

  1. One step closer to racing!
    By Raptor 660 in forum Project CARS on Playstation 4
    Replies: 51
    Last Post: 17-10-2015, 14:57
  2. One step for happiness, SMS.
    By TurboNoob in forum Multiplayer
    Replies: 2
    Last Post: 22-08-2015, 10:56
  3. How to transform Project Cars in one easy step!
    By mustanguk in forum General Discussion
    Replies: 24
    Last Post: 01-06-2015, 14:52

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •