I mean seriously, yesterday I’ve sepnt MY WHOLE DAY trying to solve stupid little bugs and errors in the Verse codes a lot of AIs gave me, now i am using THE LITERRAL EPIC’S CODES FROM THEIR SITE!!! and still it gives me not less then 7 errors !!!
I mean why epic made this whole guide with examples, and in the end just copy-pasta codes for people to use, and THE VERSE STILL GIVES ERRORS???
What can i do now???
I took some codes from here, did exactly what needed, and still:
I will admit it’s slightly confusing because they have using { PlayerStatistics } using { PlayerLeaderboard } in the final script which they didn’t show how to access, but it seems like you can just reference the player_leaderboards and player_stats_manager to access the unknown identifiers you’re getting. You’ll then have to change the code to things like PlayerStats(or whatever you name the reference).InitializeAllPlayerStats()
However, at the top of the article:
Persistence is one of the most advanced Verse topics, I would recommend not just copying and pasting code relating to it because not knowing what you are doing can create persistence errors down the line that will prevent you from publishing new updates. It’s something to make sure you understand completely before writing code using, these tutorials are just stepping stones.
So what can i do? i thought those codes they are sharing as “complete code” is enough to get the device the guide talked about just done. How can i try and practice it if it is not working?
Any idea on how to fix it?
I recommend going through the previous tutorial (Persistent Player Statistics) and then the leaderboard tutorial. This means not copy and pasting but reading through all the code and explanations to make sure you understand every line of code by the end. This is because if you have a line of code that you copied and don’t know what it does, 90% of the time it will come back to bite you, and as the case is with persistence, maybe stop you from being able to publish updates. If these tutorials are too difficult start with easier topics and work your way up (warforge and Graeme bull have great tutorials on youtube).
For base functionality, like I said above all you need is the other two scripts player_leaderboards and player_stats_manager (above where you copied the original script) to use all the functions you’re currently getting as undefined.
I’ve got it working by adding all the previous Verse files needed, but it STILL had errors in it, even tho i was using only epic’s codes alone. I manage to get something working without error by deleting some of the sorting algorithms that he didn’t recognize. tho inside the game it doesn’t work, at least i have a device with codes that are without errors, that’s a start for me
I would really like somebody to help me or explain how can i replace their “Score system” in side this “build your own race” just by recording player’s total elapsed time instead of the scores. i mean solo-man-racing system for just recording time and putting the player’s name with the elapsed time that’s all. it should me even simpler than what they have there, but i do not know the allowed vars or whatever it is.. so i cannot just learn it from reading their guide because it’s not an option there.
questing is, where can i learn all the available commands or variables and these stuff? i really want to learn but there it is limited to their purpose only.. i’ve red both the topics for persistency and leaderboards ofc, but cannot say i understand EVERYTHING in there.. im still new to this.
Any help please?
As far as learning all the functions you have available, it’s good to just read through the entire digest files (fortnite.digest, verse.digest, etc.) and take notes for yourself for what seems the most useful for you, build a cheat sheet that you have open while programming. It’s a lot of lines but after an hour or two you’ll have a lot more tools at your disposal
To be honest that was i was doing the whole day today i watched all his 8 episodes so far, still not sure how to make exactly the device i want yet, but i’ve learned a lot! maybe tomorrow
