v15 Release Question

I have a little question regarding using a base files/source for a new server

Which is better to use as base source:

[Only registered and activated users can see links. Click Here To Register...] or [Only registered and activated users can see links. Click Here To Register...]

K15 doesn't have ranking_dbf ( As the note say's it may can cause crash )
Blouflash Release has ranking_dbf ( Blouflash ranking question is: Is there any problem with the database of this release? )

I believe there is only one issue with ranking and can be resolved, which deals with a window crashing the user's client. It's been a while, so I do not recall.

If I remember correctly, Blouflash solves the issue with singleton's being updated (static initialization) with msvc compiler using a compiler flag telling them to use the older version pre-c++11 standard for static initialization. Unironically, easily solvable without said flag, and it's probably better to keep with the standard and solving it the other way (k22 does that). Reminds me when people used Zc:forscope- to not change any of the for loops, kinda dumb to do that not gonna lie.

Also, there's no reason to link legacy_stdio_definitions.lib. K22 solves this another way as well, and in doing so saves space on the executables.

The ranking in k22 can be re-enabled with __GUILDRANK.

Theoretically, anyone who says one or the other is all time better and "f ketchup", is on "Copium". The differences are minimal and nothing of functionality is really lost.

For instance, Ketchup uses std::string for the map of strings in scanner which I believe is what official used as well. This was swapped to CString in Blouflash and some other sources. Blouflash removes all calls to AddErrorMessage which is used for ffl_dump / the default exception handler that showed the crash stack trace in the log, and Ketchup doesn't remove those calls even though both don't have ffl_dump.

TextCmd_SetRandomOption is better in ketchup because you're allowed to use all the DST values up to 96 (which should be changed to MAX_DST or whatever its called from DefineAttribute.h) but Blouflash only checks for a few main stats. There are some fixes in ketchup already like MaxEmoticonFix, or if you're using /Piercing and the window isn't open already, it will open the window. Less memory gets allocated with Ketchup's source with uNumPad. (ketchup: 1000*10 bytes allocated for the array. Blouflash: 1000 * 10 * 8 bytes allocated for the array).

You're able to easily winmerge / beyond compare the two to see theoretically no major differences and most negative input is just people's hate boners.


As a developer, I think I'd personally use Ketchup's just because legacy_stdio_definitions isn't needed due to some 5Head added code and thread safe static initialization (as it should be in c++11 and above). If I wanted Ranking, I can add that back in.

Quote:

Originally Posted by M¿dScientist I believe there is only one issue with ranking and can be resolved, which deals with a window crashing the user's client. It's been a while, so I do not recall. If I remember correctly, Blouflash solves the issue with singleton's being updated (static initialization) with msvc compiler using a compiler flag telling them to use the older version pre-c++11 standard for static initialization. Unironically, easily solvable without said flag, and it's probably better to keep with the standard and solving it the other way (k22 does that). Reminds me when people used Zc:forscope- to not change any of the for loops, kinda dumb to do that not gonna lie. Also, there's no reason to link legacy_stdio_definitions.lib. K22 solves this another way as well, and in doing so saves space on the executables. The ranking in k22 can be re-enabled with __GUILDRANK. Theoretically, anyone who says one or the other is all time better and "f ketchup", is on "Copium". The differences are minimal and nothing of functionality is really lost. For instance, Ketchup uses std::string for the map of strings in scanner which I believe is what official used as well. This was swapped to CString in Blouflash and some other sources. Blouflash removes all calls to AddErrorMessage which is used for ffl_dump / the default exception handler that showed the crash stack trace in the log, and Ketchup doesn't remove those calls even though both don't have ffl_dump. TextCmd_SetRandomOption is better in ketchup because you're allowed to use all the DST values up to 96 (which should be changed to MAX_DST or whatever its called from DefineAttribute.h) but Blouflash only checks for a few main stats. There are some fixes in ketchup already like MaxEmoticonFix, or if you're using /Piercing and the window isn't open already, it will open the window. Less memory gets allocated with Ketchup's source with uNumPad. (ketchup: 1000*10 bytes allocated for the array. Blouflash: 1000 * 10 * 8 bytes allocated for the array). You're able to easily winmerge / beyond compare the two to see theoretically no major differences and most negative input is just people's hate boners. As a developer, I think I'd personally use Ketchup's just because legacy_stdio_definitions isn't needed due to some 5Head added code and thread safe static initialization (as it should be in c++11 and above). If I wanted Ranking, I can add that back in.

Thanks for your thoughts and suggestion, But im getting bother using k15 when i re-enable the ranking database that i can got a crashes issues in the long run. Im not a pro in sql and c++ that's why im really bother bout it. And you think if i didn't re-enable the ranking database the files will i still get a trouble in the long run? and about re-enabling ranking again i try'd to re-enable it now and i didn't get a crashes? what is the specific crash after i re-enable the ranking database?