Page MenuHomeFeedback Tracker

MAJOR - New cfgignorelist.xml change not working as intended
Reviewed, NormalPublic

Description

With the release of version 1.27, a change was introduced in cfgignorelist.xml:

<type name="Watchtower" cheatCheck="1"></type>
<type name="Fence" cheatCheck="1"></type>

The intended purpose of this change is unclear, but it does not appear to be meant for despawning player-built structures on server resets. However, this is exactly what seems to be happening.

A player on my server first reported that their fences were disappearing shortly after being built or after a server reset. To verify this, I tested the change on my LAN server. After constructing a wall and restarting the server with the above modification in place, I logged back in to find that the wall had partially despawned, leaving only the upper frames.

I then repeated the process without cfgignorelist.xml change and found that the wall remained intact.

If this issue is not addressed, it could affect thousands of players, leading to widespread frustration.

Details

Severity
Major
Resolution
Open
Reproducibility
Always
Operating System
Windows 7
Category
General
Steps To Reproduce
  1. Modify cfgignorelist.xml to 1.27
    • Add the following lines to cfgignorelist.xml: ` <type name="Watchtower" cheatCheck="1"></type> <type name="Fence" cheatCheck="1"></type> `
  1. Start the Server
    • Launch a server with the modified cfgignorelist.xml.
  1. Build a Fence or Watchtower
    • Construct a fence or watchtower as a player would in a normal gameplay scenario.
  1. Restart the Server
    • Shut down and restart the server.
  1. Log Back In and Observe
    • After reconnecting, check the structure.
    • Expected behavior: The structure remains intact.
    • Actual behavior: The structure partially despawns, leaving only the upper frames.
  1. Test Without cfgignorelist.xml Modification
    • Remove or revert the changes to cfgignorelist.xml.
    • Repeat steps 2–5.
    • This time, the structure remains intact after a restart.

Event Timeline

Geez changed the task status from New to Awaiting internal Testing.Mar 3 2025, 9:34 AM
Geez added a subscriber: Geez.Mar 3 2025, 11:43 AM

Hello GraceKelly.
Is build anywhere enabled on this server?

@Geez Yes, build anywhere was enabled on the server. However, in the area where I tested it, I don’t believe it allowed any builds that wouldn't normally be possible with vanilla settings, i'll attach my build data below"

  "BaseBuildingData": 
    {
        "HologramData": 
        {
            "disableIsCollidingBBoxCheck": true,
            "disableIsCollidingPlayerCheck": true,
            "disableIsClippingRoofCheck": true,
            "disableIsBaseViableCheck": true,
            "disableIsCollidingGPlotCheck": false,
            "disableIsCollidingAngleCheck": true,
            "disableIsPlacementPermittedCheck": true,
            "disableHeightPlacementCheck": true,
            "disableIsUnderwaterCheck": true,
            "disableIsInTerrainCheck": true,
			"disableColdAreaBuildingCheck": true,
            "disallowedTypesInUnderground": 
            [
                ""
            ]
        },
        "ConstructionData": 
        {
            "disablePerformRoofCheck": true,
            "disableIsCollidingCheck": true,
            "disableDistanceCheck": true
        }
    },
Geez added a comment.Mar 3 2025, 11:49 AM

Thank you!

Geez added a comment.Mar 4 2025, 2:18 PM

Hello again.
There is a workaround at the moment, you can bypass the issue by removing "cheat check" from the cfgignorelist.xml file located in offline mission folders.
Regards,
Geez

Geez changed the task status from Awaiting internal Testing to Confirmed Internally.Mar 4 2025, 2:19 PM

Heya @Geez just to be more clear to other users do you mean

A : Removing all of the below

<type name="Watchtower" cheatCheck="1"></type>
<type name="Fence" cheatCheck="1"></type>

B : Removing only cheatCheck="1"

<type name="Watchtower"</type>
<type name="Fence"</type>

To my understanding it would be A which what i have done personally.

Geez added a comment.Mar 4 2025, 3:44 PM

A would be correct but I believe B would not do anything either

  1. Build a Fence or Watchtower

Construct a fence or watchtower as a player would in a normal gameplay scenario.

I dont believe this is the way to reproduce. You have to put two (or preferrably more) fences as close to each other as possible. Setup 3-4 fence kits and then put the logs and build everything. When restarted, the walls will be completely gone. On official server without Build Everywhere

@Whoami your belief is incorrect, I tested this in an open field with fences alone and apart and it occured, given the steps provided has evolved into "confirmed internally" i believe its safe to say theyre correct.

I mean... Single fences dont despawn. It´s when you put them close to each other some of them disappear

@Whoami yet they do, the devs have even confirmed they do.

Ok, thats weird. But probably true if you say so.

But I have aproximately 100 walls built and only the ones put close to each other has despawned.

Why wouldn't they just disallow fence kits to be placed too close together? and why cant they ix the damage passing through walls/gates to the walls and gates behind them?

and remove granade launcher
and ban dupers/lag switchers/all other cheaters
and ban players who crashes servers on purpose

This is getting out of control

Geez merged a task: Restricted Maniphest Task.Thu, Mar 20, 11:40 AM
Geez changed the task status from Confirmed Internally to Reviewed.Thu, Apr 3, 4:36 PM

Fix has been released in todays patch, please let us know.