SylenThunder

Yep. Either a bad edit, or file permission issue. Details, as always, are in your logfile.

I believe it is in the setting options before you load the game, but I haven't turned my PS4 on in over a year now so I could be wrong.

Small correction here. Unity doesn't work well with custom set pagefile settings. Even if you have it set manually to always be larger than the 8GB minimum that Unity requires, it still seems to cause a problem when Unity goes to address the pagefile addresses. This will end up crashing the client, and usually gives a generic memory allocation error. (Even if the game client wouldn't even use the pagefile because you have more than enough RAM available.) Besides that, if you have Win 7 SP1 or greater, setting a custom fixed pagefile will decrease performance 90% of the time when compared to having it set to System Managed.

Most all of it. If it's super long because it's spamming errors, then you can truncate it after the first few sets of errors. Or try again and exit when the issue starts so it isn't super long. Also if it doesn't fit on pastebin.com justpate.it will usually work. This is all noted in the instructions you are expected to have read.

Go to the thread of the mod and ask there. This section really is for Vanilla game support. I don't provide support for mods outside of the thread for the mod.

A chunk is a 16x16 area. A region is 500x500 off the top of my head. Regions are stored in a specific file, and chunks are bits of the region. Neither reset on their own. Also note that using the chunkreset command in a20 is more likely to break the region file than not.

Also, just a reminder. Instructions on how to post your log are Pinned in this section. Always read the Pinned topics before posting.

Need a log.

2023-04-16T21:01:00 1238.241 WRN Spawned entity with wrong pos: [type=EntityPlayer, name=pocket951♥, id=100289] id=100289 pos=(0.0, 0.0, 0.0) Player profile corrupted. Maybe because of the stupid symbol in the name. Maybe for a number of other reasons. Most common is dying, not respawning, and the server/host shutting down. Second most common is alt-F4 exiting the client because you want to cheat death or something. Non-standard characters in names have been known to cause issues as well in the past. Tell them not to get so creative and just use normal alphabet characters. When they are joining, but before they are loaded, try teleporting them to valid coordinates. If that doesn't fix it, then nuke the player data and gift them exp/gear.

This shows successfully loading and exiting a local save with the Undead Legacy overhaul.

Offhand that looks like an older build. I would suggest upgrading to current. Or at least to a build before this week's releases. Also make certain you are not using a custom pagefile. It should be set to Windows Managed for all drives.

There is a Pinned thread regarding the MD5 issue with tips on how to avoid it in the Console Discussion section of the forum.

I wouldn't hold my breath. TFP has never been about giving away free exp. You put resources and energy into your blade traps, so they give you exp. Same for your friend. Same reason you don't get exp by simply making a field of spikes for zeds to walk across and die on.

Will need a new log then. The only issues I see in the log are a really weak system, and an error that appears to be related to incompatible data. Also note, you should exclude the client from security software. I suspect this might also be caused by the software interfering with the client's ability to access the data.

Exit the game, change the value, and then it should take effect whenever RNG rolls the dice on that. If a container has already been loaded with the old RNG, it would not be affected until that is reset in the next loot cycle.

It's still there.... <lootgroup name="groupApparelHats"> <!-- <item name="armorSantaHat" mods="dye" mod_chance="0"/> --> <!-- HOLIDAY_ITEM --> <item name="apparelSkullCap" mods="dye" mod_chance="0"/> <item name="apparelPressboyCap" mods="dye" mod_chance="0"/> <item name="apparelBallCap" mods="dye" mod_chance="0"/> <item name="apparelCowboyHat" mods="dye" mod_chance="0"/> <item name="modArmorSkullCap" loot_prob_template="low"/> <item name="modArmorPressboyCap" loot_prob_template="low"/> <item name="modArmorBallCap" loot_prob_template="low"/> <item name="modArmorCowboyHat" loot_prob_template="low"/> <item name="armorClothHat"/> <item name="armorFootballHelmet"/> </lootgroup>

It really doesn't matter how clear the screenshot is, the data contained in it is essentially useless. Will need a log to see the real picture.

Well it wasn't ever posted in the correct section anyway. I only saw it because I monitor the console section since I'm the last person that had major support ties here. In any case, since OP doesn't really want help, we can close this.

With this attitude, you're damn lucky anyone responded.

No, it's referencing a buff that doesn't exist in the default game. Or at least I was unable to find any reference to it in the client files.

It's pulling modded data from somewhere. 2023-04-05T19:52:56 527.368 INF RequestToSpawnPlayer: 171, Dreke_Grimnour, 5 2023-04-05T19:52:56 527.449 INF Created player with id=171 2023-04-05T19:52:56 527.562 ERR Buff Class not found for 'buffscoringevent' That's the start of your issues. So at a minimum this player data has stored cvars that do not exist in the Vanilla client.

I try to keep the posts updated when something like that changes. I probably need to make some information about where mod folders need to be located, since that is all changing over the last couple of builds.

In the Pinned FAQ thread... [sP] Where are my saves at? A guide to migrating save files.

Looks like corrupted player data on the server. I would restore it from a backup or just nuke it.

No, saves are too large. I believe Steam's upper limit is 1GB, and just the generated map for an 8k world is over half that. And that's only a recent development. A lil over a year ago your basic generated map was 1.2GB or so. That doesn't include any save data at all. It's just the basic world data.