Store Page
ATLAS
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews
ATLAS >  Workshop > Impulse's Workshop > LEGACY2019: Custom Item Stacks (Discontinued) > Discussions
LEGACY2019: Custom Item Stacks (Discontinued)
Description Discussions3 Comments0 Change Notes
 This topic has been pinned, so it's probably important
Impulse  [developer] 2 Aug, 2021 @ 12:08pm
Server admin game.ini settings
You need to adjust all game.ini files of all grid servers. The game.ini file is usually, depending on Grid Server subfolder (in this case A1), located at
Windows:
..\ShooterGame\Saved\A1\Config\WindowsServer\

Important:
You need to put this stuff into your game.ini of all servers of your grid,
do not put it into your gus.ini!

If you're playing on Blackwood (Singleplayer), you'll need to make the game.ini file read only to prevent the game from overriding your settings constantly.

Main tag to put above, but only once
[CustomItemStacks.Settings]

Available options
Those are default values, if you do not change them leave the option out of your game.ini
RevertChanges=false OverallStackMultiplier=1.0 OverallWeightMultiplier=1.0 SaveItemStatesCycleTimeSeconds=300 DisableDefaultItemSettings=false InitItemDelaySkipCounter=400 ItemInitStepDelay=50 SaveItemDelaySkipCounter=400 DisableCreativeModeProbing=false DebugCIS=false
Explanation on what this all means:
RevertChanges=false
Is used before you remove this mod from your server. This will edit all affected item classes and restore the original stack, weight and spoiling information. You need to leave your settings untouched so that this option can revert all affected items of course... only remove the settings after this procedure is done (Procedure: reverting changes, shutting server grid down, removing mod, clearing game.ini).

OverallStackMultiplier=1.0
Applies an overall multiplier on all active ItemSetting entries. If this multiplier is smaller 1.0 it reduces the stack size, if it's above then it increases the stack size.

OverallWeightMultiplier=1.0
Same functionality as OverallStackMultiplier, but affects the weight settings of all active items. This means for example if only default ItemSettings are active, each item has 0.1 of the normal weight. So the calculation if you want for example 50% weight reduction would be a setting of OverallWeightMultiplier=5.0. That would result in: 0.1 * 5.0 = 0.5

SaveItemStatesCycleTimeSeconds=300
This option modifies the frequency with which every item on your server gets checked and saved, so that the for example stack information can be loaded after a server restart again. This option should normally not be touched, 5 minutes are tested and good - and don't worry everything is executed with delayed loops so that your server won't feel any lag ;)

DisableDefaultItemSettings=false
If you don't want to use the default ItemSettings but only your own, then use this option and set it to true.

InitItemDelaySkipCounter=400
Determines how many creatures/ships/structures/players should be iterated until a delay step of 10ms is taken. This is a technique to prevent server lag but in the same time to increase the iteration speed. This option is clamped between 1 and 1000, but everything above 400 could potentially cause your server to crash due to UE detecting a runaway loop (If you use e. g. storage boxes with 400+ item slots).

ItemInitStepDelay=50
Is clamping between 10 and 1000 ms and states the actual waiting time between each init phase.

SaveItemDelaySkipCounter=400
Same as the option above "InitItemDelaySkipCounter", but for the writing item info part.

DisableCreativeModeProbing=false
If you don't plan on using the CreativeMode, then you can disable the weight testing with this option.

DebugCIS=false
This option is not required for a live server, it's only used for e. g. grid communication tests..
< >
Showing 1-1 of 1 comments
Impulse  [developer] 2 Aug, 2021 @ 12:09pm 
ItemSettings
The main part of this mod are of course the ItemSettings. The following lines are all default settings, if you do not want to change them leave them out of your game.ini - don't needlessly convolute your server settings!

Simply put your custom ItemSetting lines below the tag, and possibly below the other settings from the post above
[CustomItemStacks.Settings]

GoldCoin
ItemSetting=(Name=GoldCoin,ItemClass=/Game/Atlas/AtlasCoreBP/Items/PrimalItemResource_GoldCoin.PrimalItemResource_GoldCoin,MaxQuantity=100000,WeightMultiplier=0.007143,SpoilingMultiplier=,CustomItemName=,CustomItemDesc=,OriginMaxQuantity=1000,OriginWeight=0.2,OriginSpoiltime=0.0)

Click here to see the rest of the default ItemSettings[drive.google.com]

Explanation:
Name=GoldCoin
The name part is not required, it's only there to help you to understand which class path that line belongs to.
ItemClass=
This option is required and you need to give it the pure class path of an item, this can be a mod item too. The Blueprint' and ' parts should be removed.
MaxQuantity=100000
Here you can set the desired stack size of that item class
WeightMultiplier=0.007143
This multiplier reduces the original item base weight if it is smaller 1.0
SpoilingMultiplier=
If you leave this multiplier empty or don't put it into the ItemSetting line, it will default to 1.0; It works similar to the WeightMultiplier.
CustomItemName=
Define your own name for that item, if you don't use it you can leave it out of the ItemSetting line. It does not have a default value.
CustomItemDesc=
Define your own description for that item, if you don't use it you can leave it out of the ItemSetting line. It does not have a default value and the system won't apply custom descriptions if there is already one on the original item.
OriginMaxQuantity=1000 OriginWeight=0.2 OriginSpoiltime=0.0
Those are vanilla item stats, it is required to preset those values. All default ones do not need to be added to your game.ini as long as you do not put corresponding line into your game.ini. Why are those settings required? -> Since this mod is manipulating the actual item class on your server and a lot of servers have multiple grids running on one machine but only one installation of server files, it happens that in each grid the controlling singleton is applying it's weight multiplier... This means that e. g. grid A1 takes the base weight of 1.0 and multiplies its weight multiplier onto it (0.1) which results in 0.1 base weight. The second grid A2 does the same but now sees 0.1 as base which results in 0.01 as the new base weight of grid three and so on.... BUT with the settings above this issue can be prevented.
#1
< >
Showing 1-1 of 1 comments
Per page: 1530 50