Jump to content

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


Vanilla

Recommended Posts

Hey Vanilla,

there are some bugs in the new Gamecore V 2.4

 

The Belt-System going to be buggy also the Costume-System and all items like rings, windshoes, belts  and so on can't be used by a right click on it.

You can only use it when you draw it in the filed.

 

Here a screen:

lTyxf.jpg

Test Client 40250

 

With other Game-Cores I had no problems

 

Logs:

CH1:
SYSERR: May  2 23:31:48 :: heart_idle: losing 134 seconds. (delay occured)
SYSERR: May  2 23:35:29 :: CharacterSelect: no account table
SYSERR: May  2 23:35:29 :: Process: UNKNOWN HEADER: 124, LAST HEADER: 0(1), REMAIN BYTES: 4, fd: 26
SYSERR: May  2 23:35:59 :: GiveItemFromSpecialItemGroup: cannot find special item group 53515
SYSERR: May  2 23:38:28 :: Process: UNKNOWN HEADER: 124, LAST HEADER: 0(0), REMAIN BYTES: 5, fd: 26
SYSERR: May  2 23:38:29 :: Process: UNKNOWN HEADER: 124, LAST HEADER: 0(0), REMAIN BYTES: 14, fd: 26
SYSERR: May  2 23:53:57 :: Analyze: login phase does not handle this packet! header 17
SYSERR: May  2 23:53:57 :: Process: UNKNOWN HEADER: 47, LAST HEADER: 0(1), REMAIN BYTES: 4, fd: 26
SYSERR: May  2 23:56:57 :: Process: UNKNOWN HEADER: 47, LAST HEADER: 0(0), REMAIN BYTES: 5, fd: 26
SYSERR: May  2 23:56:57 :: Process: UNKNOWN HEADER: 47, LAST HEADER: 0(0), REMAIN BYTES: 14, fd: 26
SYSERR: May  3 00:00:41 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: May  3 00:01:37 :: pid_deinit: 
End of pid

DB:
SYSERR: May  2 23:28:30 :: pid_init: 
Start of pid: 1310

SYSERR: May  2 23:28:30 :: Start: TABLE_POSTFIX not configured use default
SYSERR: May  2 23:28:31 :: Load:  DirectQuery failed(SELECT login FROM block_exception)
SYSERR: May  3 00:00:43 :: Process: FDWATCH: peer null in event: ident 28
SYSERR: May  3 00:00:43 :: Process: FDWATCH: peer null in event: ident 30
SYSERR: May  3 00:00:44 :: Process: FDWATCH: peer null in event: ident 29
SYSERR: May  3 00:00:49 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: May  3 00:00:49 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: May  3 00:00:56 :: pid_deinit: 
End of pid

SYSERR: May  3 00:02:26 :: pid_init: 
Start of pid: 1741

SYSERR: May  3 00:02:26 :: Start: TABLE_POSTFIX not configured use default
SYSERR: May  3 00:02:27 :: Load:  DirectQuery failed(SELECT login FROM block_exception)

Client Syserr:
0503 00:13:17775 :: GRANNY: r:/granny/rt/granny_file_info.cpp(145): File has run-time type tag of 0x8000000f, which doesn't match this version of Granny (0x80000010).  Automatic conversion will be attempted.

Client Log:
0503 00:13:26504 :: ENABLE_NEW_EQUIPMENT_SYSTEM0503 00:13:26504 ::  0503 00:13:26504 :: 1110503 00:13:26504 ::  0503 00:13:26504 :: 00503 00:13:26504 ::  0503 00:13:26505 :: 00503 00:13:26505 :: 
0503 00:13:26505 :: ENABLE_NEW_EQUIPMENT_SYSTEM0503 00:13:26505 ::  0503 00:13:26505 :: 1120503 00:13:26505 ::  0503 00:13:26505 :: 00503 00:13:26505 ::  0503 00:13:26505 :: 00503 00:13:26505 :: 
0503 00:13:26505 :: ENABLE_NEW_EQUIPMENT_SYSTEM0503 00:13:26505 ::  0503 00:13:26505 :: 1130503 00:13:26505 ::  0503 00:13:26505 :: 00503 00:13:26505 ::  0503 00:13:26505 :: 00503 00:13:26505 :: 
0503 00:13:26505 :: ENABLE_NEW_EQUIPMENT_SYSTEM0503 00:13:26505 ::  0503 00:13:26505 :: 1110503 00:13:26505 ::  0503 00:13:26505 :: 00503 00:13:26505 ::  0503 00:13:26505 :: 00503 00:13:26505 :: 
0503 00:13:26505 :: ENABLE_NEW_EQUIPMENT_SYSTEM0503 00:13:26505 ::  0503 00:13:26505 :: 1120503 00:13:26505 ::  0503 00:13:26505 :: 00503 00:13:26505 ::  0503 00:13:26505 :: 00503 00:13:26505 :: 

King regards

 

Aro

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

  • Premium

next error:

/usr/lib32/libstdc++.so.6: version GLIBCXX_3.4.11 required by /usr/home/game2/muthafcka/db/db not found

 2014Files# uname -a

FreeBSD 2014Files.Viruz.tk 9.2-RELEASE-p5 FreeBSD 9.2-RELEASE-p5

 

There are some libs included in the package and you have to copy them too read the readme

Link to comment
Share on other sites

It's compatible with 40k locale_string.

 

Many bugs result into bad configuration and client modification.

Please only use the options when you implemented them in the client and make sure you enable them in a right way.

 

Lib errors are because you're using freebsd < 9.2 and don't installed the libs within the package.

  • Love 3

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

~ vanilla core will become open source soon!~

 

Dear dev's,

 

I'm gonna make a big change in the vanilla core project. As I find myself with less time to work on such big things, I decided to change it a little bit. There's always the problem with "backdoors" etc.. And I know you don't want to risk your server. And that's why I decided to make it open source. The source code will be released.

 

Does this mean that I'll drop the development of vanilla core?

-> Nope!

Though the source will be published, I'll continue developing. But now you can contribute, fix bugs etc. and send your solutions there too! So the development will make a bigger boost in the matter of progress. There'll be a "standard" vanilla core that'll receive further updates. Everyone can download the pre-compiled standard version OR the source of the standard version and adapt it to his/her needs.

I still respect the authors for doing their work. But hindering myself and hindering progress isn't helping anyone.

 

Will there be other projects?

-> Yes!

Of course I'm planning on doing more projects than before. Your donations just won't be only for the vanilla core, but also for the other projects I'll make in the future. In the past you've helped me a lot and I appreciate your donations which gave me motivation to continue my work. It's always good to see people thanking me for the hard work I've done in the past.

Anyways, there'll be a few more projects in the future. Expect leftover to be a new server and also I'm planning on creating clean vanilla-compatible serverfiles and a clean 40k vanilla-compatible client. They'll both be shared here of course!

Also I'm planning on creating other stuff and tools, which will be written mostly in c#. So brace yourselves! It's by far not the end of my projects!

  • Love 20

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

I have some problems.
I download 2.4 version and change name to db and game. Db copy to /db and game copy to /share.
And if i write /start appears:

and so all the time. What i'm doing wrong?
My conf.txt:
WELCOME_MSG = "Mysql odpalone"
SQL_ACCOUNT = "localhost account mt2 mt2!@# 0"
SQL_PLAYER = "localhost player mt2 mt2!@# 0"
SQL_COMMON = "localhost common mt2 mt2!@# 0"
SQL_HOTBACKUP = "localhost hotbackup mt2 mt2!@# 0"
TABLE_POSTFIX = ""
BIND_PORT = 15000
DB_SLEEP_MSEC = 10
CLIENT_HEART_FPS = 10
HASH_PLAYER_LIFE_SEC = 600
BACKUP_LIMIT_SEC = 3600
PLAYER_ID_START = 100
PLAYER_DELETE_LEVEL_LIMIT = 75
ITEM_ID_RANGE = 100000 2100000000

and my /db folder 

Sorry for my language but I do not write good English.

 

Link to comment
Share on other sites

So, where is problem, how can i fix it?
Autorun.log /db
 

AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
AsyncSQL: connected to localhost (reconnect 1)
CClientManager::InitializeMobTable:: 1169 mobs loaded.
CClientManager::InitializeItemTable:: 5742 items loaded.

syserr /db
 

SYSERR: May  5 01:16:23 :: Start: TABLE_POSTFIX not configured use default
SYSERR: May  5 01:16:23 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Column 'name' in field list is ambiguous
query: SELECT empire, pid, name, money, windate FROM monarch a, player b where a.pid=b.id
SYSERR: May  5 01:16:36 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: May  5 01:16:36 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: May  5 01:16:36 :: pid_deinit: 
End of pid

syslog /db

May  5 01:16:23 :: ItemIDRange: Build: 4210000001 ~ 4220000000 start:4210000001
May  5 01:16:23 :: ItemIDRange: Build: 4220000001 ~ 4230000000 start:4220000001
May  5 01:16:23 :: ItemIDRange: Build: 4230000001 ~ 4240000000 start:4230000001
May  5 01:16:23 :: ItemIDRange: Build: 4240000001 ~ 4250000000 start:4240000001
May  5 01:16:23 :: ItemIDRange: Build: 4250000001 ~ 4260000000 start:4250000001
May  5 01:16:23 :: ItemIDRange: Build: 4260000001 ~ 4270000000 start:4260000001
May  5 01:16:23 :: ItemIDRange: Build: 4270000001 ~ 4280000000 start:4270000001
May  5 01:16:23 :: Metin2DBCacheServer Start

May  5 01:16:23 :: ClientManager pointer is 0xffffc984
May  5 01:16:23 :: GUILD_RANK: Testowo                   1 18000
May  5 01:16:23 :: GUILD_RANK: ~ Metineth ~              2 16000
May  5 01:16:23 :: GUILD_RANK: Admini                    3 0
May  5 01:16:23 :: GUILD_RANK: PastaeBasta               4 0
May  5 01:16:28 :: [       50] return 0/0/0 async 0/0/0
May  5 01:16:33 :: [      100] return 0/0/0 async 0/0/0
SYSERR: May  5 01:16:36 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: May  5 01:16:36 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
May  5 01:16:36 :: MainLoop exited, Starting cache flushing
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.
May  5 01:16:36 :: AsyncSQL: closing mysql connection.

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.