Their name and contents can be whatever you decide they are.
The only thing you need to change is whatever changes between the two patches! (client version... not the server source you're using). The packets themselves will change slightly between those two patches so you'll need to ensure all your offsets are still correct in your various packets (most likely hero information and entity spawn will be the main ones effected)
I told you exactly what you need to do for patch 5527. If you didn't message me to read what I have to say, then why are you still spamming me on every single social medium I belong to? I'm done seeing this ******* message. It's time you **** someone else off.
Edit : also, why are you updating your source to 5527 if it's already 5527? **** it. I don't want to know. You're someone else's problem now.
I told you exactly what you need to do for patch 5527. If you didn't message me to read what I have to say, then why are you still spamming me on every single social medium I belong to? I'm done seeing this ******* message. It's time you **** someone else off.
Edit : also, why are you updating your source to 5527 if it's already 5527? **** it. I don't want to know. You're someone else's problem now.
I think he simply doesn't know the word downgrade and want to go to 5375.
gratz for that but All u did is bypassing Password Encryption which Alot of ppls done this and iam Among them ..but it isnt Substituting Password Encryption for sure as i faced problem which is you can logging within any password ..Am not caring Much about upgrading source the much i care for making Stable / Well coded Source anyways GL
gratz for that but All u did is bypassing Password Encryption which Alot of ppls done this and iam Among them ..but it isnt Substituting Password Encryption for sure as i faced problem which is you can logging within any password ..Am not caring Much about upgrading source the much i care for making Stable / Well coded Source anyways GL
Could also just over-write the client password encryption versus cracking the new one.
For my old source I didn't even use any of TQs encryptions.. I used the SHA256 (or 512) of a hash made from the account and password. Worked just fine, and was more secure in my opinion..