Validation error from outdated files in sys/versions (regression?)

flyingpigbaby · May 29, 2025, 9:49pm

Summary

I’m getting validation errors based on code within the sys/versions/XXXX which I assume is my latest published build. I can fix the errors by editing that code, but this needs to be done for each restart of the editor (I assume it fetches the build again).

This issue was present previously, but was fixed, this seems to be a regression of sorts: https://forums.unrealengine.com/t/validation-error-on-verse-files-under-sys-public-folder-that-are-giving-asset-identification-errors

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Verse

Steps to Reproduce

Have a published version with code that references some texture files e.g. T_MyIconTexture in some UI.
Rename the texture files, receive validation errors? Might require restarting editor.

Expected Result

Not to receive validation errors from published code which no longer exists in the project.

Observed Result

Platform(s)

Windows

Island Code

7142-4719-9129

Mineblo · May 30, 2025, 6:25am

Does your project contain verse persistence? also could you copy paste the full first message seen on the screenshot you provided

flyingpigbaby · May 30, 2025, 5:38pm

It does yeah, don’t see any errors relating to persistence though. I mentioned in the issue, but this is something that has happened before.

The errors are from code that isn’t in the project anymore, I’ll try and send the full error message later, but it’s mentioning something that doesn’t make sense.

Also to note, these verse errors don’t show up when building verse, it’s part of the project validation, the verse build works fine.

Mineblo · May 30, 2025, 5:42pm

Your verse persistence needs to be backwards compatible, you will most likely need to add that code back

flyingpigbaby · May 30, 2025, 5:48pm

The errors have nothing to do with persistence, the errors just mention assets.

Mineblo · May 30, 2025, 6:00pm

Could you plz paste all of the errors ? also if your verse file is missing that was persistent it will FAIL the backwards compatibility persistent check

flyingpigbaby · May 30, 2025, 6:06pm

I don’t think it’s got anything to do with persistence (none of the stuff I posted mentions persistence), all my persistent data is in one file and hasn’t been changed since that release, nor has the file been removed.

Here’s the missing error anyway:

Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/mob_manager_device.verse(16,5, 16,61) : Script error 3593: Definition (/brickwall@fortnite.com/MyProjectName/mob_overhead_data:)OverheadMaterial is accessible from subpaths of /brickwall@fortnite.com/MyProjectName, but depends on (/brickwall@fortnite.com/MyProjectName/Assets:)M_MobOverhead_material, which is only accessible from subpaths of /brickwall@fortnite.com/MyProjectName/Assets, /brickwall@fortnite.com/MyProjectName. The definition should be no more accessible than its dependencies.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthAbilities/Abilities.verse(16,45, 16,49) : Script error 3506: Unknown member `Heal` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthAbilities/Abilities.verse(29,45, 29,55) : Script error 3506: Unknown member `SpeedBoost` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthAbilities/Abilities.verse(46,45, 46,49) : Script error 3506: Unknown member `Stun` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthAbilities/Ability.verse(9,43, 9,47) : Script error 3506: Unknown member `Heal` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthStatusEffects/StatusEffect.verse(23,43, 23,47) : Script error 3506: Unknown member `Heal` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthStatusEffects/StatusEffects.verse(14,45, 14,49) : Script error 3506: Unknown member `Heal` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthStatusEffects/StatusEffects.verse(31,45, 31,51) : Script error 3506: Unknown member `Poison` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthStatusEffects/StatusEffects.verse(48,45, 48,50) : Script error 3506: Unknown member `Bleed` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthStatusEffects/StatusEffects.verse(65,45, 65,48) : Script error 3506: Unknown member `Ice` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthStatusEffects/StatusEffects.verse(84,45, 84,51) : Script error 3506: Unknown member `Webbed` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthStatusEffects/StatusEffects.verse(101,45, 101,52) : Script error 3506: Unknown member `Stunned` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/LabyrinthStatusEffects/StatusEffects.verse(133,45, 133,55) : Script error 3506: Unknown member `SpeedBoost` in `AbilityIcons`.
Fortnite Projects/MyProjectName/Plugins/MyProjectName/sys/published/Content/labyrinth_npc_device.verse(70,51, 70,68) : Script error 3506: Unknown member `NPCVendorParticle` in `Assets`.

flyingpigbaby · May 31, 2025, 4:43pm

After fixing the errors in the /sys/ verse files manually, I’m still unable to load in, yesterday it was giving cook errors, now it’s giving the occasional “network error” and showing “edit mode error” within Fortnite, no errors inside UEFN (apart from the validation issue mentioned in this post).

Just want to re-iterate, I am unable to launch a session in this project at all, it has been completely bricked following Thursday’s update.

Cook error:

Versace_Lemonade · May 31, 2025, 8:45pm

I too am getting the same error and not being able to load a session. I can’t find the script i removed to re-add to see if that’s the issue, but it did deal with persistence. I’m not sure how to proceed past this part to get it back running.

flyingpigbaby · May 31, 2025, 9:02pm

I’ve managed to get past the cook error now as there was an error that only appeared when I tried to create a private version.

However the original error on this ticket with the /sys folder is still present, I just have to replace files in that folder each time I try to launch a new session.

cmilo1357 · May 31, 2025, 9:08pm

I’m been having the same issue, I found a way around that maybe can work for you, after restoring to previous version the problem disappears, but after I close the project starts appearing again, so what I would do is check in the last changes before closing and restoring that version once I open the project again

flyingpigbaby · May 31, 2025, 9:12pm

Thanks, I’ll try that next time

flyingpigbaby · June 1, 2025, 2:16pm

The cook error has returned, I’m completely unable to launch a session. Also I’m unable to load into private versions and my published version gives me matchmaking errors.

nicoplv · June 2, 2025, 2:25pm

Same issue, impossible to launch a session and work on my island

Get 4 error logs.
3 of them report that a definition is more accessible than its dependencies, even though everything was working fine before the update.

C:/Users/Shadow/Documents/uefn-roguelike-project/UefnProject/Plugins/MainGame/sys/published/Content/Game/Scripts/Heros/damage_display.verse(32,5, 32,84) : Script error 3593: Definition (/loomio@fortnite.com/roguelikeproject/Game/Scripts/Heros/damage_display:)DigitMaterials is accessible from subtypes of damage_display, from subpaths of /loomio@fortnite.com/roguelikeproject, but depends on (/loomio@fortnite.com/roguelikeproject/Game/Materials:)DamageDigit_Opti_material, which is only accessible from subpaths of /loomio@fortnite.com/roguelikeproject/Game/Materials, /loomio@fortnite.com/roguelikeproject. The definition should be no more accessible than its dependencies.

C:/Users/Shadow/Documents/uefn-roguelike-project/UefnProject/Plugins/MainGame/sys/published/Content/Game/Scripts/Heros/damage_display.verse(32,5, 32,84) : Script error 3593: Definition (/loomio@fortnite.com/roguelikeproject/Game/Scripts/Heros/damage_display:)DigitMaterials is accessible from subtypes of damage_display, from subpaths of /loomio@fortnite.com/roguelikeproject, but depends on (/loomio@fortnite.com/roguelikeproject/Game/Materials:)DamageDigit_Opti_material, which is only accessible from subpaths of /loomio@fortnite.com/roguelikeproject/Game/Materials, /loomio@fortnite.com/roguelikeproject. The definition should be no more accessible than its dependencies.

C:/Users/Shadow/Documents/uefn-roguelike-project/UefnProject/Plugins/MainGame/sys/published/Content/Loomio/Text3D.verse(85,9, 85,107) : Script error 3593: Definition (/loomio@fortnite.com/roguelikeproject/Loomio/Text3D/char_prop:)Material is accessible from subpaths of /loomio@fortnite.com/roguelikeproject, but depends on (/loomio@fortnite.com/roguelikeproject/Game/Fonts:)NotoSans_Material_material, which is only accessible from subpaths of /loomio@fortnite.com/roguelikeproject/Game/Fonts, /loomio@fortnite.com/roguelikeproject. The definition should be no more accessible than its dependencies.

The 4th log is about a missing definition, but that’s expected. The class was removed from the game last week. There were no issues related to this before the update.

C:/Users/Shadow/Documents/uefn-roguelike-project/UefnProject/Plugins/MainGame/Content/Game/ModuleDefinitions.verse(34,26, 35,1) : Script error 3643: Missing definition in source package that corresponds to published definition (/loomio@fortnite.com/roguelikeproject/Game/Scripts/UiDefinitions/Menus:)card_types.

flyingpigbaby · June 2, 2025, 5:05pm

If you go into the /sys/version folder, you should be able to manually edit the .verse files in there to fix the issues it mentions (even if they don’t make sense), then you should be able to get past validation.

However, you many then encounter cook errors/network errors which still prevent you launching, which have happened to me, but it did fix it the other day.

flyingpigbaby · June 2, 2025, 5:33pm

Still getting the cook error today, here’s a log:

LogValkyrieRequestManagerEditor: Detected cook failure, cook job id 1537d52b-ec7b-457c-9b30-f43621e74fbf;5101e52d-79a2-4d35-b47c-9e472fbeb318
LogValkyrieRequestManagerEditor: Failed to get extended error information for cook job:1537d52b-ec7b-457c-9b30-f43621e74fbf, error:Failure ErrorCode=errors.com.epicgames.content-service.operation_forbidden, Message=This request is not authorized to edit referenced project, Raw={
  "host": "content-service.bfda.live.use1a.on.epicgames.com",
  "method": "GET",
  "path": "/api/content/v2/ticket/1537d52b-ec7b-457c-9b30-f43621e74fbf/details",
  "errorCode": "errors.com.epicgames.content-service.operation_forbidden",
  "errorMessage": "This request is not authorized to edit referenced project"
}

nicoplv · June 3, 2025, 8:03am

Thanks, for the information. I hope it will be fix soon, it’s not sustainable for me to keep making changes to the sys folder manually every time.

I have a few quick questions to better understand the problem:

Are you working alone on your project? We are a team of five, and I’m wondering if collaboration could be a factor
Are you using URC?
Do you have multiple maps in your project?
At any point, did you delete the sys folder? In our case, we don’t sync it because we assumed it was just a cache folder used to launch the session.

Niqk0 · June 3, 2025, 8:05am

Same problem for us. Impossible to launch a session. We can’t work anymore.

flyingpigbaby · June 3, 2025, 4:41pm

I am working alone currently but I’ve had other collaborators in the past, just no commits in a while from them.
Yep.
Just 1 I believe, shall double check.
I tried deleting it before to see if it helped, but it’s cleared/downloaded whenever you try to launch a session, so doesn’t change anything. I assume it’s a cache used to check backwards compatibility with persistence etc, seeing as it seems to be your last published version.

nicoplv · June 3, 2025, 6:10pm

Thank you, so you’re in a different “configuration”, but facing the same issue.

we are multiple working on the project
we don’t use urc
we have multiple maps in the project
we don’t sync the “sys” folder between everyone working on the project