12-26-2022, 07:53 AM
3 hours ago, Stormax said:
I get this problem and i post this because it fix my problem i don'k know why its a problem for you.
Okay, it seems like you don't seem to understand the obvious problem here. You don't seem to have any knowledge about how to properly work with this codebase or any code in general it seems.
As you can see above already, the sources do not match at all. So your "fix" is not even going to work in the first place. You don't even know what kind of source he's using and you just throw a bunch of stuff at him that's not compatible. You would have known that this won't be compatible if you also just checked what you're sending him. There are multiple custom files inside of this engine and references to non-existing files outside the engine folder itself.
Here is an example for a custom file that is referencing another custom file in another project folder:
Quote
1>SRCDesign\Engine/Entities/DailyLoginData.h(9): fatal error C1083: Cannot open include file: 'common/header/def_daily_login.h': No such file or directory
Ok sure, you could send him this one file. But what then? Are you going to fix him all the packet problems that might occur or are you just going to ignore those? Are you now also going to send him a random, not matching, GameServer & ShareLib folder? At that point you can just sent him the entirety of the source code and he'd actually would have something that might work.
3 hours ago, Stormax said:
Pwesty give me his files im not the owner so i will not publish without this permission its normal i think bro.
So I checked the files a little bit and it seems like pwesty had his hands in this engine, so why are you sharing it then..? And if this isn't what pwesty gave you to fix that problem, why are you sharing a random engine folder in the first place? lol
3 hours ago, Stormax said:
Also why you dont publish this files for fixed this problem ? ?
You wanna know why I don't just sent him an random engine folder? Because it is just flat out dumb. The way to fix this problem is by identifying the problem and then resolving it properly. The proper procedure here is to debug the client to find out why it opens in background and closes after some time. If he does want to go through the hassle of doing it then he could ask for a different source or perhaps someone here is willing to properly fix it for him.
And there is also no reason for me to release "fixed files", because there are already multiple "fixed" sources on this forum that he could use instead. (like I said, if he wants to do that.)
Overall from this conversation here it's very obvious that you're still inexperienced yourself and that's why I'm explaining to you (and everyone else here that might think that this is a proper solution) why it's something you should never do. If you knew that there is an actual "fix" in there then you could post that fix alone, but you don't seem to know yourself what the problem is in the first place, same for the first problem he had.