[Guide] how to setup your source.

I know i know there is allot of guides showing how to setup a source, but i am only going to show the basic things you need to fill to make your source work.

Note: the only reasion i am posting is to make sure people stop making thread and saying i cant setup,


Here is some basic things that public sources use.



1. server name

when you go to bin/debug/config, you will see your setup options there will be something like server name

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

2. KillConection.cs


allot of sources use this, and sometimes there is a option there to put your ip there like this source

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

idk if its right to use ip and everything in killconection some sources for example my don't have that option, but if you do make sure to fill that in.


2. app.config

sources use app.config, and sometimes its just something like this

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

and sometimes its like this

[Only registered and activated users can see links. Click Here To Register...] SO if its something like this then make sure to fill it in.


and some sources have a ip config in there program.cs where you need to put the ip in order to get it work.

Well that's all for now i hope this help,cya all.

How about, server.dat inside the client's folder? Should that be configured aswell ?- if Decrypted. If Encrypted - Loader !

Nice tut. Quite simple & Easy
+REP!

I was hoping this would be some hilarious post where the OP was going to be like, "Don't."

Does not work with mine :(

What about navicat? Most of the sources wont work if the server name in configuration table is not correct.

Quote:

Originally Posted by Deathmist What about navicat? Most of the sources wont work if the server name in configuration table is not correct.

did you look at the guide 1. ? XD

Quote:

Originally Posted by LordGragen. did you look at the guide 1. ? XD

I think what deathmist is trying to say is that your guide lacks some of the major details required for setting up a server. You don't specify what source the guide is for (just that it's for public sources which is incorrect), nor do you specify the tools required in setting up and editing the source and database. The source you're referring to is an edited version of Kimo's edit of TrinityCO. The tools required that you should probably show a guide for include: mysql community server, navicat or mysql workbench, visual studio express, framework 4.0, the conquer online client, conquerloader 5.2, etc. As for my KillConection.cs file that almost every public source now uses... I'm shocked that nobody's set it up correctly to use the configured mysql configuration. They're more using it to kill connections that aren't being closed properly, which isn't what it was created for. Anyways, that's out of the scope of this discussion. Your guide could really use detail.

Quote:

Originally Posted by Fаng I think what deathmist is trying to say is that your guide lacks some of the major details required for setting up a server. You don't specify what source the guide is for (just that it's for public sources which is incorrect), nor do you specify the tools required in setting up and editing the source and database. The source you're referring to is an edited version of Kimo's edit of TrinityCO. The tools required that you should probably show a guide for include: mysql community server, navicat or mysql workbench, visual studio express, framework 4.0, the conquer online client, conquerloader 5.2, etc. As for my KillConection.cs file that almost every public source now uses... I'm shocked that nobody's set it up correctly to use the configured mysql configuration. They're more using it to kill connections that aren't being closed properly, which isn't what it was created for. Anyways, that's out of the scope of this discussion. Your guide could really use detail.

I guess i will add ton of info later on but i don't really know much about the killcontetion so feel free to fill that in if you want.

Quote:

Originally Posted by LordGragen. I guess i will add ton of info later on but i don't really know much about the killcontetion so feel free to fill that in if you want.

Sure. The problem is that when you open a new mysql connection using a pooled configuration, it will keep the connection alive no matter what the server says (disposing it using GC will not work). Here's a quote I found supporting my claim:

"Even though you set the connection object to null and perhaps the connection object is collected, the internal driver object remains open against the server so that future calls to Open() will use a pooled connection and be very fast. If you want the physical connection to close then you need to disable pooling by setting pooling=false on your connection string."

The problem is, no server uses this feature correctly - they keep creating new pooled connections instead of closing and opening the existing connections. Handling the pools incorrectly creates this issue, and since I was inexperienced with MySql with my first custom source, I created a class that would kill the connections that were sleeping every few seconds. This is extremely inefficient and not the right thing to do. Either turn pooling to false, or create a proper threaded worker system for using the sleeping connections in the pool.

The class could be used to kill the connections after the server is done using them. Otherwise, it should not be used in the manor every public source is using it in.

Quote:

Originally Posted by Fang Sure. The problem is that when you open a new mysql connection using a pooled configuration, it will keep the connection alive no matter what the server says (disposing it using GC will not work). Here's a quote I found supporting my claim: "Even though you set the connection object to null and perhaps the connection object is collected, the internal driver object remains open against the server so that future calls to Open() will use a pooled connection and be very fast. If you want the physical connection to close then you need to disable pooling by setting pooling=false on your connection string." The problem is, no server uses this feature correctly - they keep creating new pooled connections instead of closing and opening the existing connections. Handling the pools incorrectly creates this issue, and since I was inexperienced with MySql with my first custom source, I created a class that would kill the connections that were sleeping every few seconds. This is extremely inefficient and not the right thing to do. Either turn pooling to false, or create a proper threaded worker system for using the sleeping connections in the pool. The class could be used to kill the connections after the server is done using them. Otherwise, it should not be used in the manor every public source is using it in.

what if i told u that i clear All the pools after executing certain Query, Or even dont use pooling feature Beside Closing the Connection after Each Query is Executed .. would i still need to implement this ?

I have NEVER seen a trinity source correctly use Fangs kill connection right

its doesnt require a magician to execute his codes .. all u need to run these codes using thread that run every exact period of time ... not a big deal

thanks for help