Metal-Crow @metalcrow@social.cleverlibre.org

⁣

And i can't even test it myself, i have to ask others who actually crash to see if certain changes stop the crashes or not. Of course, it's not reliably reproducible either.

man, hunting down crashes in my mod is a fucking roller coaster. Nope, it's not in the super janky and over engineered hotswapping system i had to develop from scratch that uses FROM debug code. Apparently it's in the 20 line basic feature???
Maybe?????

i'm going to have to fix that i think, especially if i want rollback to work

Looks like Amir figured out the whole double-dip iframes thing before i did, back in 2020! https://www.youtube.com/watch?v=uPd9zpoi6eA
Good to be validated, at least.

Finished adding a Red Eye Orb that allows invading all areas (basically WexDust), and incorporated the halberd running attack fixes into legacy mode.

The mod now uses the newest steam messaging API! Finally got everything fully working and cross compatible.

(all this is backwards compatible btw, which is a pain let me tell you)

I'll be curious by how much the new steam networking api reduces latency. It uses the steam relay system to route packets better (https://partner.steamgames.com/doc/api/ISteamNetworkingMessages), but in reality not sure how many ms that'll shave off.

once that's done the rollback netcode will have better tools to support it. Just about done with those 2 rn!

Current work has been rewriting the player connection handshake to use a different method that doesn't expose your IP, following up with replacing the steam networking with a newer version that has less latency, more supported tools, and doesn't leak your ip.

Also i finally got my anti-ban code working (probably) 🤞

Learning more about rollback netcode! I've realized that i'm going to have to remove a bunch of packets from the dark souls networking stack in order to get it to work, and have the client do more work on it's end. This network stack is so weird.

If you guessed "why are you saying you're unsetting everything (which is commonly 0) when you're actually setting it?" then good answer! I don't know either!

Potentially good news about my ban troubles, it may stem from being being a gigantic idiot! Hey kids, can YOU see the typo in this line?

At this point, the only explanation must be that they hid more detection code in another packet. But they're all named really boring things like "Bloodstain Message" or "Ghost Data". I guess i just gotta disable them all and narrow it down that way.

Update! Nope it still didn't hold up against a character with invalid equipment!
So far i'm 0 for 12!

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUGH

You love to see it folks! No ban!