Page MenuHomeFeedback Tracker

Config files not applying
Assigned, NormalPublic

Description

Rented Fragnet Private Master server 23.94.241.18:****
Config files not applying on restart.
Custom Time: 2015/7/9/9/10
Time acceleration enabled at 8 hours.
Time persistence Disabled.

On restart, time is 80% night time regardless of resets.

Details

Severity
Minor
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Category
General
Steps To Reproduce

Consistent inability to apply custom configurations.

Event Timeline

Havoek created this task.Dec 1 2018, 8:02 PM

Since the infamous patch we had on the 22nd of November you can't change the ServerTime anymore. Open your "init.c" file and add the following line right at the bottom of the the weather settings section:

GetGame().GetWorld().SetDate(2018, 6, 12, 7, 3);

The weather section of your file should look like this:

void main()
{
Hive ce = CreateHive();
if ( ce )

ce.InitOffline();

Weather weather = g_Game.GetWeather();
weather.GetOvercast().SetLimits( 0.0 , 1.0 );
weather.GetRain().SetLimits( 0.0 , 0.0 );
weather.GetFog().SetLimits( 0.0 , 0.25 );
weather.GetOvercast().SetForecastChangeLimits( 0.5, 0.8 );
weather.GetRain().SetForecastChangeLimits( 0.1, 0.3 );
weather.GetFog().SetForecastChangeLimits( 0.05, 0.10 );
weather.GetOvercast().SetForecastTimeLimits( 3600 , 3600 );
weather.GetRain().SetForecastTimeLimits( 300 , 300 );
weather.GetFog().SetForecastTimeLimits( 3600 , 3600 );
weather.GetOvercast().Set( Math.RandomFloatInclusive(0.0, 0.3), 0, 0);
weather.GetRain().Set( Math.RandomFloatInclusive(0.0, 0.2), 0, 0);
weather.GetFog().Set( Math.RandomFloatInclusive(0.0, 0.1), 0, 0);

weather.SetWindMaximumSpeed(30);
weather.SetWindFunctionParams(0.1, 1.0, 50);
GetGame().GetWorld().SetDate(2018, 6, 12, 7, 3);
}

This will set the time to 7h30. It's the only workaround until the fix that chaos

Geez changed the task status from New to Assigned.Dec 3 2018, 3:44 PM
Geez added a subscriber: Geez.

Hello Havoek and thank you for the report.
This is an issue we are aware of and we are looking into the issue internally.
Regards,
Geez