Search the Community
Showing results for tags 'configuration'.
Found 3 results
Baby default behavior in GUS.ini Hello, I do a ton of breeding, people on my cluster do a ton of breeding. What do you always do when a new baby dino hatches? 1.) Set to not wander 2.) Set to passive (;) 3.) Set to ignore group whistles 4.) Set to not look at ally 5.) Unfollow (Y) Imagine hatching a thousand dinos, times x number of players.... That is a LOT of clicking. Suggestion: Have options in one of the .ini files to set default behavior for these options when a baby hatches, so people do not have to go through the radial menu of each dino for four to five times. BabyWander = false BabyBehavior = passive BabyIgnore = true BabyLookAlly = false BabyFollow = false
Tribute/Element Override Option I would like to see the option to transfer tribute items and element included as an override for unofficial servers. While I get that you folks have reasoning for not allowing these things on Official servers, Unofficial servers are supposed to be the Burger King option. I know the option to transfer tributes existed at one point, so I don't suspect it will be overly difficult to add that option back to crossark transfers.
As Xbox players and hosts we've never had access to the .ini files to control our servers. Everything for us was pretty straightforward in terms of configuring settings, but we were also fairly limited in the amount of custom configuration we could implement. All of that of course changed when hosted servers arrived on scene, which opened us up to a whole-new-world of possibilities and headaches. I wanted to create this guide to help alleviate some of the pain associated with altering the .ini files, and to dispel some of the apprehension associated with implementing custom configuration code. I spent days researching, hours writing code, and hours fixing some of the mistakes I made. I figured some of you folks might find some value in the mistakes I've made, and what I've learned through my trial-by-fire. What follows is a sectional guide on the use of Expert Mode, and how to configure some of the more common custom configuration elements. NFD vs. Expert Mode When you first access the Nitrado Admin Console, you will find that they have created their own version of the configuration menu we had when running PDS through our consoles. It's all very straightforward and simplified, and it will look pretty familiar. For most of the settings you will want to alter, this is by far the easiest way to go about it. I have dubbed their console, Nitrado for Dummies. This is not to say you are a Dummy if you use this, but it is a simplified means of configuring the server; thus, the moniker. If you run a single server, and are apprehensive about altering the .ini files, this might be your best option for server configuration. A few things to consider before deciding which configuration mode you want to proceed with: How you want to customize your server: If you want to implement changes to level progression or custom stats, the NFD interface can be very time consuming (I'll get further into detail about these aspects later on) How many servers you run: if you run more than one server, and intend to implement customization, the NFD interface is a massive time-suck. Is your apprehension justified?: The simple reality here is that, there isn't a major difference between engaging the NFD interface, and directly manipulating the .ini files. Just like the NFD interface, every line item in the .ini file is easily identified. As an example: NightTimeSpeedScale=.7 DayTimeSpeedScale=.7 TamingSpeedMultiplier=3.0 HarvestAmountMultiplier=3.0 HarvestHealthMultiplier=3.0 Note: When switching to Expert Mode, most of the configuration options disappear from the General Settings interface. You will also notice that Engine Settings is replaced by Expert Settings. When switching from one configuration mode to the other, settings do not usually transfer. If you have been using the NFD interface for any period of time, it is probable that most configuration settings will show up in the .ini files; however, custom level progression and other custom configurations may not. Be sure to scan the .ini files to ensure that your server is configured according to your desires, check it again, and then proceed. Expert Mode Sounds fancy, right: Expert Mode, dun dun dun. It's neither as glamorous or as ominous as it might at first appear. If you've made it through this wall of text, and are now ready to start tinkering with the .ini files, here is where we begin. First things first, let's identify exactly what we're working with, and what goes where. To activate Expert Mode, you will navigate to the General Settings interface, click the little box at the top, and then click save. Once this is done, the pane on the left will look like: Let's go ahead and click on Expert Settings, and take a gander. You will notice that you're now nose-to-nose with an .ini file. Pretty unimpressive right? Feel free to scroll around, and familiarize yourself with what you're looking at. You'll notice that not all of your settings are here, and that's because there is more than one file in this interface. Click the area highlighted in red, and a drop down will appear. Once there, go ahead and click on Game.ini, the click Load File. You will notice that there is an Engine.ini in the drop down, but it is blank, and has nothing to do with what we're doing here. You will make use of both files in this interface when configuring your server, as they both contain different game variables. You will want to acclimate yourself with both of these files, so you know where everything is when you need to alter a variable. Note: Under GameUserSettings.ini you are going to see all manner of things you might be tempted to tinker with. Avoid altering settings directly under the following sections: [/Script/ShooterGame.ShooterGameUserSettings] [ScalabilityGroups] [/Script/Engine.GameSession] Alterable variables fall below the following sections: [SessionSettings] SessionName=[US] Ark FTW-Ragnarok (this is the name of your server, and can be changed at your leisure) [ServerSettings] (many of the settings you found under General Settings are now found here, and they can all be altered) AutoSavePeriodMinutes=15.000000 (this can be altered, but I have read there may be some performance related issues in so doing, so probably don't) In order to make any changes to these files, you're going to need to completely stop your server. Once the server is completely stopped, you can make any necessary alterations to the .ini files. Once those alterations have been made, click Save, and then go have yourself a cup of coffee. Nitrado recommends that you wait around 4 minutes before bringing your server back up, as the backend has to make conversions. I also always run a server check any time I make any changes, which is probably a good habit to acquire. If you don't wait, you may end up with corrupted data, so wait the 4 minutes. Now, let's talk about some of the custom configurations you can make, and some of the resources I've found helpful. Level Ramp Overrides This is just a fancy way of identifying the option to add a custom level scheme to your server, and it works for both Players and Dinos. I'm going to break this down into three sections: Players and Dinos, Engrams, and Resources...oh my? Players and Dinos How you proceed here will be largely dependent on the type of server you run. Using the Overrides you can add more levels, reduce the total number of levels, and completely reshape the way you progress through those levels. Altering the Dino progression scheme is straightforward; not so much for players. The game reserves 30 levels for ascension, so you need to keep this in mind when you're deciding on a max level. The easiest way to explain it is: If you want a max server level of 150, after ascension, you will simply add 150 levels If you want a max server level of 150, before ascension, you will need 180 levels in total Ramps Another factor to consider is how you want your ramp to work. What is a ramp you ask? Simply put, it is the increase in experience required per level. You can effectively create any ramping scheme you want with the override. The vanilla progression system uses a progressive ramp with a steep curve towards the end. I use the vanilla ramp up through 115, and then a wave scheme thereafter. Maybe you want a linear ramp where each level requires the same amount of experience. The world is your oyster here, so do whatever feels good to you. Code Now let's talk a bit about code, shall we? The method for coding is linear, but it is time consuming. There is an override variable for both Players and Dinos, and you will need to create a block of code for each if you intend to create custom level schemes for both. If you elect to override the vanilla level cap and progression, your code block MUST start at level 0, and MUST include every-single level you want to have on your server. I made the mistake of starting my code block at a specific level, instead of coding every level, and I magically transported every logged in player to level 82. So what does the code look like? Glad you asked: LevelExperienceRampOverrides=(ExperiencePointsForLevel=5,ExperiencePointsForLevel=20,ExperiencePointsForLevel=40,ExperiencePointsForLevel=70 As you can see, there isn't anything overly complicated about the actual syntax of the code. If you've noticed something odd, however, you're right to be suspicious. Level 0. Well, there is no Level 0 in the game, so what on earth is that for? When you first spawn on the beach, you are already at level 1, so it seems odd that this wouldn't start at level 2, right? Level 0 in this code block represents level 2 in-game. So if you are coding these blocks, always subtract 2 from the max level: If you want 180 total levels, your code block will start at Level 0 and end at Level 178. Engrams Points Now that you've coded out your level progression system, what about engram points? Just like with levels, you can employ any engram point scheme your wee heart desires, and it is all linear: OverridePlayerLevelEngramPoints=8 OverridePlayerLevelEngramPoints=8 OverridePlayerLevelEngramPoints=8 OverridePlayerLevelEngramPoints=8 OverridePlayerLevelEngramPoints=8 OverridePlayerLevelEngramPoints=8 OverridePlayerLevelEngramPoints=8 OverridePlayerLevelEngramPoints=8 OverridePlayerLevelEngramPoints=12 OverridePlayerLevelEngramPoints=12 OverridePlayerLevelEngramPoints=12 Each line ties directly to a level, and in order. So, the first line is the number of engram points you gain at Level 0 in your level code block, and so on. Your engram points code block should match your level code block in terms of numbers: If you have 198 levels written into your code block, you will need 198 lines in your engram points block if you want each level to come with engram points. Resources The following are some of the things I found useful when setting up my server's progression scheme: Ark's vanilla level scheme from the Wiki Code Generator Tool Note that the level scheme is out of date, so you will need to adjust if you intend to use the vanilla progression scheme up through any particular level Also note that, the site has other tools for custom settings aside from levels and engram points Server Configuration Specifics from the Wiki More to follow...