Vanilla

FreeBSD version?

[Hidden Content] Here you go for libz.so.6 Sorry for that, the lib is missing in vanilla 2.1 but required. It'll be included in 2.2 @sema1995: It's already there but with another config-option. And it does not only affect item_proto. Mob_proto will be affected too. This feature is coming with 2.2 @Evor: Why should I? I'd but I'm not very sure about changing a working code if there's no need to. @Summex: I've already looked into it and it will definitely be a part of future releases. I hope to bring it with 2.2 @callmax: It'll not only be the movement speed. I'm looking into making other values changeable so you'd possibly change the attack speed or creating a starting gold e. g. Oh and the - hp fix made it into 2.2 along with some bug fixes for level, exp and yang.

Got some good and bad news. I've managed to get some work done on the source code. There'd be again a slight boost to the performance (and less memory consume). I've removed unused variables and now I'm about to clean the rest of the code. Every dependend library got a new cleanup. There are no errors left, only some small warnings with things I'm unable to change (since these libs are from YMIR and there's no source code to compile them). But they won't affect the stability so it's okay. Only small things. If this code runs stable I'm about to install new stuff one by one so it'll keep being stable. I'm aware of the issues you posted here and I'm about to fix them ASAP. And yes, some things YMIR did could possibly be exploited or leading into crashes you may have. It was a hard work but looking at the output of the compiler helps finding these lines (as mentioned earlier there's a floating point handling in the cube function but the output message uses %d which is clearly only for integer, not floating point -> crash). There are more things like this one and I'm about to find and eliminate them for 2.2 dbcache compiled clean without any errors. Even no unused variables anymore. If I can I'll make a test run of it and then as I mentioned earlier I'd release at least the dbcache.

Since I'm unable to test it (same reason why I can't continue or release the core) I may ask you if you've encountered the guild war crash. Please try it and tell me if there's a security issue so I can fix it until 2.2 Oh and cube should work well as it's intended. Even with floating points (there's a new issue related here but I managed to fix it in 2.2) it'd work now with 2.2

Hey, sorry but I'm not able to release 2.2 yet. There's much to do since all of you made some great ideas and I want to release a stable version with all the wishes you had. And since there are som stability issues and code optimizations left I decided to first finish the work before releasing a new version too early. But unfortunately I'm not able to continue my work this weekend so it'll take some time to release it. I guess I'll be finished within the beginning of next week. If you want I can upload dbcache for 2.2 so you can use the "no txt"-startup. @Grantix: No, 2.1 supports only text files. In 2.2 you can enable the alternative startup in you db conf.txt so it'll ignore text files and read everything from the database.

That's what I wrote in the last line. "You can just edit the Makefile to use gcc48".

That's not all. Edit /etc/libmap.conf and /etc/make.conf. Tutorial: [Hidden Content] You can just edit the Makefile to use gcc48.

I've installed compat9x on my system, but I'd add the needed libraries so you don't have to install it. @Efyn: The database starts and works without any problem, I don't see any use in changing something working. @Tim: My upload is really bad. So that's why I try to keep it in minimum size, sorry for that. @Amok: Sorry, thought you'd ask for binary-difs since I already stated that I won't release or show the source code (or parts of it) because I respect the work of the authors. That's why I thought you'd ask for binary dif's.

I want to apply the changes on the source directly instead of letting others patch it. You can still patch, if you want, but if you have any wishes you can just ask, I want to adapt the core to the communities needs. You won't need dif's if you can fully customize the gamecore.

please update your freebsd. 8.3 support is going to end in April this year. 9.0 is already deprecated and not longer supported. I recommend upgrading it since this'd cause some problems. Core compiled on FreeBSD 9.2. Should be compatible with 9.1 though, but I'd recommend upgrading to 9.2. I won't make compatibility with older versions since they're just too obsolete and I want to create a new basis. People should start using newer versions of FreeBSD instead of being stuck on old systems and maybe suffer from security vulnerabilities.

since your yang got resetted to 4,2kkk I guess there's some more behind that since it's the length of unsigned int. The command allows you to set such high values, but somewhere in the game source there's a restriction you seem to not have noticed yet. I'm not sure about it but maybe you can check the dbcache too. And look for syserr/syslog, maybe they'll provide you overflow-messages.

@PACIFICADOR: Good idea. I'll make this happen. How about a option to set the % you loose when you die (if you choose 0%, you won't loose exp anymore and there'll be no message)? And an option to define if player with a bad reputation will drop items on death or not. Or even drop gold on death? Let me read your opinion.

Are you using vanilla 2.1? #ldd vanilla_2_1 vanilla_2_1: libstdc++.so.6 => /usr/local/lib32/metin2/libstdc++.so.6 (0x2857b000) libm.so.5 => /usr/lib32/libm.so.5 (0x28678000) libmd.so.5 => /usr/local/lib32/compat/libmd.so.5 (0x2869d000) libz.so.6 => /usr/lib32/libz.so.6 (0x286b5000) libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0x286c9000) libthr.so.3 => /usr/lib32/libthr.so.3 (0x286d4000) libc.so.7 => /usr/lib32/libc.so.7 (0x286f6000) This is my output. You may check if the directory /usr/local/lib32/metin2 exists and upload the libs to this directory.

As I said, I will never add pm logging functions. Maybe I can allow logging pm's with suspicous contents, but who defines what's suspicious or not? Unless I have some clear ideas how to deal with this problem, I won't add such things. Allowing admins to create filters by themselves would lead into filters like "a" (so every message with an a would be logged).. My idea is to create a strike-system working with the banlist. If a chat message restricts against the items added in banlist, the message will be censored like you already know and the uncensored message is stored into the database. The user will receive a warning and after 3 warnings, automatic chatblock could be triggered (depending on how many warnings the user received). But I guess this system needs some improvement and a feature to remove old warnings so people won't get punished if they made small mistakes, typo's or got punished by a false warning. It's just an idea. Nothing I'll give my word to. @Mehti: I'm investigating the error now and tell you more about it. @Namikaze: There is a library error. /usr/local/lib32/libstdc++.so.6 is used by your server, but it'd be /usr/local/lib32/metin2/ Please use ldd as tim suggested on page 5 and report your results.

Did you check the database? Seems like the gamecore and the client recognizes your gold amount as long long, but the mysql-server can't store it so it'll overflow when you reload or buy something to refresh the values.

New information for v2.2 I've fixed a lot of issues! There were many conversions and warnings, I've fixed most of them. There are just some unused variables but I'm not too sure about them so at first I'm going to leave them and delete them later. Maybe, if they're really unnecessary, they won't make it to v2.2 which would be great. At least it should have more stability since I've changed a lot of unsigned to signed comparisons. There is some cool new stuff. I've changed the test_server_protect option to "new_test_server". Additionally you can now check the hosts (if you have some gm's with static ip's or let them only have gm rights if they connect through a special proxy). You can - of course - just not enable this setting (it's off by default) or just enable it and use *.*.*.* if you want every ip to use gm rights. For this I introduce a new CONFIG option to you: new_gm_host_check: 1/0 The new procedure for checking your gm rights does no longer depend on your locale. The new_test_server is only a setting for the gm rights! If the server is no test-server, it'll just use the default routine. If it's a test server this option will enable a checkup if the account is listed in your gmlist. If it's not, the user will automatically get HIGH_WIZARD. If he is listed, he'll automatically get IMPLEMENTOR. There's also a new security patch applied to 2.2 This one's targeting the API. It'll now set adminpage_ip to localhost if it's not defined or you're using the new CONFIG option: adminpage_no_localhost: 1/0 Additionally the whole API is disabled by default. Say goodbye to API tools. You can enable the API with the following CONFIG-option: adminpage_enable: 1/0

I will never add pm logging functions. private messages are private. The only thing I can imagine is logging messages blocked by the chat filter. @Maslovicz: Try to install my libs in the metin2-directory mentioned.

As mentioned in one of the previous posts I've looked for the internal ip. I'll provide a new CONFIG option to disable this checkup (and setting it like it's in the dif file to 0.0.0.0). the exe should work without any errors then. 2.2 will be released within this week, I guess it'd be something like Friday. But I'm not very sure, maybe earlier.

Thanks for your replies. There will be new CONFIG-options in 2.2: test_server_protect: 1/0 1 = enabled. 0 = disabled. For security reasons this option is enabled by default. If you want to run a test server, just disable it and everything will be fine. log_level: 0/1/2/3 0 = no logs will be created or used. 1 = logs will be provided in mySQL. Main log files will be used (command_log, hack-logs) 2 = All MySQL-logs are enabled. 3 = All MySQL-logs are enabled. Addtionally the server will create a syslog so you can monitor everything. By default the log-level is defined as 3. I'll work on the password limit. Inventory size and plugin system are future developments. I guess they'll only be present in 2.5+

Prepare yourselves for vanilla 2.2 changelog + moved from c++99 to c++11 + DB can now start without txt-files! + command_log works now properly + Putting things for 0 gold in the shop works now properly + 6/7 bonus works now properly + rewrote test-server module: If test-mode is activated all logs and information will be provided as you may remember it. But people won't be able to use admin commands (commands for IMPLEMENTOR) unless their account is written in the gmtable. This helps you keeping the damage low in case someone's getting able to enable the test-mode. Users won't be able to use implementor-commands unless you've specified they have the permission to. Please tell me what features you want to see in 2.2 so I can implement them before I release it.

I'm on it. Thanks for informing me about the bug. I'm going to change some huge things. In 2.2 it'll be possible to revert the new boot method back to the old so you won't need any txt-files for your database, it'll start by default without them. However, you can enable the new boot method by adding the following line into your conf.txt: TXT_STARTUP: 1   I'll check the 6/7 bonus.   @Rumor: Don't use such strange difs on the gamefile. The offsets are very different (as you can see my gamecore is about 42mb). Vanilla core is not compatible to difs for other cores. Can you tell me for what core this dif is? I'll try changing the issue in the src code and test it. I've also noticed the thing with 0 yang.   The data type is long long by default. But you can easily just use a lower gold maximum so it'd fit in with the integer datatype the binary uses. €: Recompiled db with c++11 and now it's working. Seems to be stable to me, but please be sure you try it yourself before you install 2.2 db on a public server (unless you're enabling the txt loading).

I'll have a look over the say-color-functions. I'm going to inform you if I've something new. Since I'm very busy it'll take a few days until vanilla 2.2 is coming. In 2.2 the dbcache will use the special lib-path too so there won't be any lib problems anymore.

I guess I'd try a overflow check and maybe raise the maximum hp so you'd possibly get more hp (but I don't know how the client will handle that though). To invisible bug: It's clearly the binary, not the gamefile. I joined on my test server and never had that bug (with 34k game I've received this bug everytime I respawned).

Game or db?

in v2.2 the bug with the query is fixed. Thank you for reporting the issue. I've also fixed the table name bug since 'name' is ambigous. I've changed the query so it'll select `name` which is clearly the column name. The first test also showed up a great progress. You won't need to have the package-folder anymore unless you wish to enable the function as I mentioned above. Next step is to make the dbcache more comfortable. I'll try to let it either boot from the txt-files or from the database. If no txt file is present, it'll automatically print a message and loads the proto's from the database instead of the txt. So you won't have the trouble converting anything. If you still like to use the new system, just feel free to do it. Also I'll change the binding of the ip in dbcache. It'll now listen to 127.0.0.1 by default unless you specify a new value. This will help to mitigate attacks on your dbcache if you have no firewall at all (it's a little bit cruel to let your server run without a firewall and no bind-ip specified, but maybe under some circumstances this'd happen. So the new dbcache will handle it for you).