Verse Persistence Issue: unique specifier on classes that lack the allocates effect

[CrankBoomBoom]

Hi everyone,

After the recent update to version 31.00, I’ve encountered a warning in the code for the player_stats_manager as outlined in
Persistent Player Statistics.

The editor is showing warnings for the unique specifier on classes that lack the allocates effect. The ecosystem updates also state this detail: v31.00 Ecosystem Updates], however it doesn’t provide a solution for existing classes that use the specifier.

Could I get some help on how to fix this?

Thank you!

[Fali (Fali_005)]

I think it is asking you to pass a constructor to your “DebugString” if you want, pass a little more of the fragment or the code and I will try to correct it

If you don’t solve it before!

[CrankBoomBoom]

Hi,

Thanks for your reply. The code is actually taken right out of the documentation for persistent players statistics.

StatType := module:
     score_stat<public> := class<computes><unique>(stat_type):
         DebugString<override>():string = "Score"
 
     win_stat<public> := class<computes><unique>(stat_type):
         DebugString<override>():string = "Win"
 
     loss_stat<public> := class<computes><unique>(stat_type):
         DebugString<override>():string = "Loss"
 
     # Instances of each stat_type you can use in your experience
     Score<public>:score_stat = score_stat{}
     Win<public>:win_stat = win_stat{}
     Loss<public>:loss_stat = loss_stat{}

In my implementation you can see the warnings:

Just to be clear, the code works. The issue is that unique specifier is going to be deprecated on classes that lack the ‘allocates’ effect:

Verse v31.00 updates

The problem is that there no effect specifier called ‘allocates’.

I’m just trying to get ahead of it before it becomes a problem. If I remove the <unique> class specifier then the code doesn’t compile.

Hopefully I’ve provided some more clarity.

Thanks again for your help!

[polytycoons]

Hello do you have a discord i can contact you ?

[polytycoons]

Did you find a solution to this ?

[JWRHarding]

I need a fix for this as well…

[Flak]

Moved to the bug forum. We’ll get someone to take a look and will let you know if we need more information.

[CrankBoomBoom]

Thank you, I’ll keep my eyes peeled!

[CrankBoomBoom]

Not really, I’m reworking the code entirely on my end to avoid using the specifier.

[Jimbohalo10]

hi,
The UEFN Feature template Verse Device Template fails so UEFN-Verse team will have to fix by the next version of Verse comes out

[esse123]

Could you please share the solution here too? Your reddit post got removed for some reason

[CHENSHUO.L]

Here I repost the solution, you can check:

Solution for Verse Persistence Issue: unique specifier on classes that lack the allocates effect

After the recent update to version 31.00, many people encountered the following warning: [image] This warning is mostly found in Persistent functions, as everyone follows the official documentation. However, the official documentation has not been updated and no solution has been provided. I don’t want my game dropping dead after the next engine update. I found some solutions to avoid this risk: 1. First, we need to remove all the <unique> effect from warning methods 2. Then, We need to ad…

[RhapidFyre (Melanie)]

This does solve the problem - Epic, can we update the wiki?

[CrankBoomBoom]

Hello and thank you for your post. I’m going to try it. If I have any useful updates I’ll be sure to let everyone know!

[marciocamello (VoVoZera)]

#change where is 
DebugString<override>():string = "Deaths

#for this
DebugString<override>()<transacts>:string = "Deaths

#add transacts

#in condition change this
if(Stat = StatType.Elo):
#for this
if(Stat.DebugString() = StatType.Elo.DebugString()):

#dont forget this if not instantiate yet

# Instances of each stat_type you can use in your experience
Kills<public>:kill_stat = kill_stat{}
Deaths<public>:death_stat = death_stat{}
Elo<public>:elo_stat = elo_stat{}
Version<public>:version_stat = version_stat{}