Looks like one page got duplicated and there are no entries after ~750 hrs., so maybe one got left out?

They have a "max length", essentially, and hers overflowed that. The same things happens with super deathful long-lived characters at PK wins.

ALTER TABLE pbf_data MODIFY imm_comment VARCHAR(max);

Or something similar, plus the appropriate changes in code if needed.

(Please disregard if not feasible due to X, I know nothing about your code)

That stuff isn't a SQL database. Very little in CF is. The limitation has more to do with the maximum number of bytes various string functions or structures can work with or store. It's been a very low priority to refactor because it's messy code that works fine (per se) with the exception of the length limitation which isn't hit 99.9% of the time.

Both with PK Wins/Deaths and imm comments. Could this perhaps be sponsored in any way? Because it's like I'm paying for PBF and don't get the whole amount of info, which well... sucks

I understand that it's a rarity. The only problem is that the few PBFs that are hit with this limitation are the ones we want to see the most And they omit the comments from the most interesting parts of the char's life.

A fix could be to duplicate the IMM_comments code and make a IMM_comments2 to store comments after IMM_comments is full. Then publish both.