Jump to content

[ Dead Download Link ] Vanilla Core 2.4.1 [ We Need You ]


Vanilla

Recommended Posts

yes, db works also with txt. Please read the first post..

 

Please stop posting bugs that actually aren't.

Most of the bugs reported aren't and only are caused by misconfiguration or incompatibility with the client which isn't fully modified to bear some features you want to enable.

Please make sure you're configuring it right - if there are still errors, then first try to solve them and if you do then refrain from posting them as bugs if they're still not regarding to the core itself..

 

I'm currently working on some minor bug fixed like when you enable EMPIRE_CHAT: 1 it'd say that empire_chat is deprecated and not global_chat. Though the flag will still be correctly set (so for now you can still use empire_chat and it'll work but in 2.5 it'll be removed).

 

Also I'm currently creating a seperate branch to make further tests into new versions. Also I'm thinking about compiling a windows version.

 

I've now added my paypal email if you want to donate to the project. I appreciate everything you do ;)

  • Love 4

We are the tortured.
We're not your friends.
As long as we're not visible.
We are unfixable.

Link to comment
Share on other sites

Hey, dann war das wohl ein Quest Sache mit fertigkeiten neu verteilen aber kriegs immer noch nicht hin, nunja ne andere frage wenn ich global_chat anmache dann sieht das komisch aus wenn die ingame im normal chat schreiben 284JDJDJK////2237/DURD/// sowas in der art PN GEHT RUFEN GEHT NORMAL FAIL Sprachen alles auf P

Link to comment
Share on other sites

That'd be. I'm now reverting the change with the linker optimization since it doesn't give that much (and may even cause these strange bugs you mentioned) and turn gdb-support back on. It's more worth to have the full debug symbols (I'm currently pending test with a higher debugging level).

We are the tortured.
We're not your friends.
As long as we're not visible.
We are unfixable.

Link to comment
Share on other sites

The db crashes when I try to start the db. Sometimes it crashes, sometimes it works well. I put all good bookshops and Updates

 

I use FreeBSD 9.2 32 bits

 

gdb

 

c3e819eef1038faeacf021d7b22dc2e2.png

 

 

Syserr

SYSERR: Jun 17 14:24:41 :: pid_init: 
Start of pid: 1730

SYSERR: Jun 17 14:24:41 :: Start: TABLE_POSTFIX not configured use default

Syslog

SYSERR: Jun 17 14:24:41 :: pid_init: 
Start of pid: 1730

SYSERR: Jun 17 14:24:41 :: Start: TABLE_POSTFIX not configured use default
Jun 17 14:24:41 :: connecting to MySQL server (player)
Jun 17 14:24:41 :: CREATING DIRECT_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 :: CREATING MAIN_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 :: CREATING ASYNC_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 ::    OK
Jun 17 14:24:41 :: connecting to MySQL server (account)
Jun 17 14:24:41 :: CREATING DIRECT_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 :: CREATING MAIN_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 :: CREATING ASYNC_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 ::    OK
Jun 17 14:24:41 :: connecting to MySQL server (common)
Jun 17 14:24:41 :: CREATING DIRECT_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 :: CREATING MAIN_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 :: CREATING ASYNC_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 ::    OK
Jun 17 14:24:41 :: connecting to MySQL server (hotbackup)
Jun 17 14:24:41 :: CREATING DIRECT_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 :: CREATING MAIN_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 :: CREATING ASYNC_SQL
Jun 17 14:24:41 :: AsyncSQL: locale latin1
Jun 17 14:24:41 ::    OK
Jun 17 14:24:41 :: ClientManager initialization.. 
Jun 17 14:24:41 :: InitializeLocalization() - LoadLocaleTable(count:13)
Jun 17 14:24:41 :: locale[UNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE0)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jun 17 14:24:41 :: locale[UNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE1)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jun 17 14:24:41 :: locale[UNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE2)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jun 17 14:24:41 :: locale[UNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE3)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jun 17 14:24:41 :: locale[UNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE4)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jun 17 14:24:41 :: locale[UNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE5)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jun 17 14:24:41 :: locale[UNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE6)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jun 17 14:24:41 :: locale[UNKNOWN_KEY(SKILL_POWER_BY_LEVEL_TYPE7)] = 0 5 6 8 10 12 14 16 18 20 22 24
Jun 17 14:24:41 :: locale[LOCALE] = spain
Jun 17 14:24:41 :: Changed g_stLocale latin1 to euckr
Jun 17 14:24:41 :: SetLocale start
Jun 17 14:24:41 :: 	--mysql_set_character_set(latin1)
Jun 17 14:24:41 :: 	--mysql_set_character_set(latin1)

Any idea?

Edited by Metin2 Dev
Core X - External 2 Internal
Link to comment
Share on other sites

This thread is not for troubleshooting your problems.

Your fault is made by a misconfiguration.

 

I'm currently rolling back with the linker optimization and enable gdb-support.

 

It seems I can't find the issue with invisibility. For me it works fine without any bugs, that's why I can't test or reproduce the bug to fix it.

We are the tortured.
We're not your friends.
As long as we're not visible.
We are unfixable.

Link to comment
Share on other sites

It does support newer versions of gcc.

 

But it's compiled with gcc 4.9.1 so maybe a lib mismatch could cause your problem.

 

I'm fetching the other libs and upload them for you. Just put them into the /usr/local/lib32/metin2/ directory like the others. Maybe it's just a lib fault that's why it's getting incompatible (because some libs are fetched from /lib)

  • Love 1

We are the tortured.
We're not your friends.
As long as we're not visible.
We are unfixable.

Link to comment
Share on other sites

game.mysql_query

 

SYSERR: Jun 17 16:16:54 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''[1020543432rder by level desc LIMIT 10' at line 1 query: SELECT level,name,exp FROM player WHERE name not like '[1020543432rder by level desc LIMIT 10

 

 

this query working on navicat but not working in quest

 

 

https://metin2.download/picture/r3F9504x09DVmF8K988YXgTtGTP6KMUj/.gif

Edited by Metin2 Dev
Core X - External 2 Internal
Link to comment
Share on other sites

It seems I can't find the issue with invisibility. For me it works fine without any bugs, that's why I can't test or reproduce the bug to fix it.

 

File char_affect.cpp, function:

bool CHARACTER::RemoveAffect(CAffect * pkAff)

scroll a little bit down and find this portion of code:

	if (AFFECT_REVIVE_INVISIBLE != pkAff->dwType)
	{
		ComputePoints();
	}

after that, add:

	else
	{
		UpdatePacket();
	}

When the character attacks or skills against a monster/another player when it is still invisible, the bug shows up. It's caused by the explicit removal of the affect, as the affect flag is indeed removed from the character, but the client can't know that as it doesn't receive an UpdatePacket (which is handled internally in the ComputePoints function).

  • Love 5
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.