Shogun

There's a WAF rule that does though. Thanks for pointing it out!

If that's the case then i wonder why so much complication, giving us 'pieces' of client instead of a solid one. Please Shogun, post the client in full compiled version I don't have time to test them or give you support for them, I'm sorry.

Thanks but this is already released here. [Hidden Content] Topic locked. Edit: I have been told that this map is reworked and therefore I'm opening this thread again. However, please use the proper forum next time. This is not a HowTo or a Guide.

This has been answered several times in this thread. You have to upgrade to FreeBSD 9.2.

Why are you posting about the same problem in 2 threads? Also where is your db and game output? You have a warning.

Some system used only in Korea

What I always wanted as a player is, the same game but deeper. Newer technologies let us do things that were not possible or too demanding in 2004 and we have tons of examples of gameplay variations in other mmorpgs. I want to be able to swin, or jump. I want enemies that display some sort of AI. I want grass (lol). I hope as people work more with the source we see more things that break the mould of oldschool/newschool.

In the third part of this tutorial we will learn how to see the user's original IP on nginx logs instead of Cloudflare's. First we have to rebuild nginx with the REAL IP module: portsnap fetch update cd /usr/ports/www/nginx make config build reinstall clean In the configuration screen navigate to the REAL IP module with down arrow and mark it for installation with the space bar. Then press enter to proceed with the building. Once it's finished we can add the following lines in /usr/local/etc/nginx/nginx.conf in the http part: set_real_ip_from 204.93.240.0/24; set_real_ip_from 204.93.177.0/24; set_real_ip_from 199.27.128.0/21; set_real_ip_from 173.245.48.0/20; set_real_ip_from 103.21.244.0/22; set_real_ip_from 103.22.200.0/22; set_real_ip_from 103.31.4.0/22; set_real_ip_from 141.101.64.0/18; set_real_ip_from 108.162.192.0/18; set_real_ip_from 190.93.240.0/20; set_real_ip_from 188.114.96.0/20; set_real_ip_from 197.234.240.0/22; set_real_ip_from 198.41.128.0/17; set_real_ip_from 162.158.0.0/15; set_real_ip_from 2400:cb00::/32; set_real_ip_from 2606:4700::/32; set_real_ip_from 2803:f800::/32; set_real_ip_from 2405:b500::/32; set_real_ip_from 2405:8100::/32; real_ip_header CF-Connecting-IP; Thereafter, we can restart nginx: service nginx restart Our visitors will appear with their real IP in the server logs now. If you are writing php code, remember to use $_SERVER["HTTP_CF_CONNECTING_IP"] instead of $_SERVER["REMOTE_ADDR"] to get the user's real IP.

auth/CONFIG check that PLAYER_SQL is pointing to account (not player!) database

syslog syserr...??

I said the apache php module, not apache. Apache by itself doesn't recognize php files.

This has nothing to do with Vanilla Core and why would anyone develop for an OS version that has no support?

Actually I made a tutorial like this for Eterhost Knowledge Base but I don't think I posted it here. I prefer to use ssh-keygen on the server though. [Hidden Content] Thanks for sharing.

Regarding the second... Assuming you already installed the apache php module, you need to add this in httpd.conf: <IfModule php5_module> DirectoryIndex index.php index.html AddType application/x-httpd-php .php AddType application/x-httpd-php-source .phps </IfModule>

They already get more ads than the registered users.

auth/CONFIG in PLAYER_SQL enter the name of the account database, not player

I don't understand what you mean

The 34k bin is packed with Themida, there isn't any virus lol. Get a real antivirus.

anything in syserr / syslog?

[Hidden Content]

What does mob_proto have to do with it? /e mob_exp rate /e mob_gold rate etc... [Hidden Content]

Change the rates in source? That's crazy there are are event flags for that and that you see are their default values.

In this second part of the tutorial I will show you how to take advantage of Cloudflare options to speed up or protect your website. The first thing that you should be aware of is the "I'm under attack" mode. This mode inspects every incoming request for malicious traffic, showing a captcha to the suspicious users to confirm they are human. This will block pretty much any Layer 7 ddos attack going against your site. Why not leave this mode on permanently? Well, some websites do this but in my eyes it's not a good idea to make every user go through the inspection process. You may also be punished on your google ranking for this, so I suggest enabling it only when you are actually getting attacked. Another security feature found in the setting is this one. I tend to leave this always on as I haven't heard of any false positives. Finally, for the experts, we have the Web Application Firewall, which is only available for paying customers. I think it's worth paying the Pro subscription for this feature as it will watch over SQL injections and other security vulnerabilities for us. If we have a custom made website which has not been tested thorougly for security, this is a must have. We can manage the firewall by turning rules on and off and watch for false positives in the Events screen which will show us every IP which has been challenged or blocked. It's recommended to have some knowledge of programming and security to make the most out of this feature. Remember that you can always turn features on or off for a specific part of your site by using the Page Rules option in the Dashboard. And this is all about the security features in Cloudflare. You can ask any question about it here and I will try to answer when I have time. Please do not pm me with questions related to this or any other of my tutorials or releases.

wherever you packed them on the client?

There's no font, that logo is hand drawn.