Help and Set Up for FXserv Version 1.3.9 by Fede83



Installation is simple, Just download the server from FxServ 1.3.9
Once you have the program downloaded, its best to make a folder for it in your program files.  You can do this by opening your My Computer, then open Program Files Folder.  From there click on the 'file' button on the top far left side and choose 'New > Folder'... then name it FXServer.
Now you can extract all the files from the FXServer.zip to your new folder you made.
If you use desktop shortcuts to open programs you can 'right' click the file named 'FXServer.exe' and choose 'Send to...  Desktop Create Shortcut' for easy starts later on.



To set your server up we need to first go into the 'Config.txt', so double click on that file.



Inside this file you will find all the different settings that can be applied to your server, I'll start from the top and give you a brief explanation of what each does.

Language=ENG or Language=ITA
There are two languages that you can run FXServ in and they are English and Italian,
just modify the last part of the text after the '=' to choose your prefer ed language.

/Port 1595
This is the port that FXServ will listen on for incoming connections.  
You have to choose a port that no other programs requiring access to the internet will be using, so don't try using the same ones as WinMX as it wont work.
Any port will work as long as its been forwarded in any routers/dsl modems/firewalls that require said.
Some fun port numbers are:
43926 = ABBA
57005 = DEAD
45067 = B00B
It will display these at the end of your room name, try them and you will see ;-)

/setchannelname Test Room
This is for you too choose the name of your room, I'm sure you already have thought of that as test room is a bit boring  ;-)

/topic Test Room topic
The topic is displayed after your room name on the WinMX Peer Network Chat page



This can be to explain anything about your room.
You can look at other room topics to get an idea of what to put for yours.

/setmotd Testing room\nWelcome $NAME$!
The Message Of The Day (MOTD) is the first thing a user sees when he enters the room, a lot of people put pictures etc in this part of the config.
You can mess about here and colour codes are able to be used here as well.
The \n means newline and the $NAME$ is the user who entered,
you can use this or change it up for your own room.

/TextFormat 1=#c2#<$NAME$#c2#> #c1#$TEXT$
Text format is how your text will be displayed in the room, you can configure this to make different  styles for different  user's giving all admin one colour or one style and members and operators (ops) another.
You can use colour codes here but it must contain $NAME$ and $TEXT$ or nothing will be displayed in the room.

/DefaultAccess acCvJj
Default access is what level a basic user joining your room will have on entry, obviously you don't want anyone entering your room to have admin access straight away
so you set this to a minimal setting, but don't forget to allow voice (v) if you change this as you don't want people joining the room and not being able to talk.

/DefaultFormat User=1
/DefaultFormat +=2
/DefaultFormat Admin=3

When you are creating text formats you can assign a standard user/ops/admin login a certain text style. You do this by setting the text format up how you like and use the corresponding number.

/addPassword agentpassw=blw+=2
This is where you create passwords for your admin and ops. The letter corresponds to what you would like that user to be able to do in your room.
Giving people high level access requires you to trust them.
Here is how you set it up:
/addPassword OurPassWord=blw+=2
Type the command first '/addPassword'
Then the Login/Password you want =
Then the Access Letters of what you would like the user to be able to do =
Then the text format number, as explained above each pass can have its own format.


Here is the Access System for FXserv:
> a - Action.
You can use the command /action text or /me text. This function serves for expressing an action. For example, /me goes to sleep becomes a text in third person.

> v - Voice.
It allows the user to write text in the chat or to be able to respond to other users.

> c - Color.
You can use the command /setcolour and colour codes. This will allow users to colour their text with the color code of their choice. The command /setcolour also becomes active with this allowed for that user.

> C - Capital letters.
You can decide whether or not to allow users to type in all capital letters or not (in chat slang typing in all caps is considered yelling).

> k - Kick.
It is the ability to kick users with the command: /kick <username>

> K - Kick.
Is to kick users including Admin/Agents. The command is /kick <username>

> b - Ban.
It is the ability to kick and ban a user or an IP using the commands /kickban <username> and /banip <IP to be banned>

> B - Ban.
It is the ability to kick and ban an user, including an Admin/Agent.
The commands /kickban <username> and /banip <IP> are similar, this access includes ability to use it on Admin/Agents.

> L - List Bans.
You can use the command /listbans Every time that someone performs a ban it will be added to the ban list. The /listbans command shows current bans in order starting with the most recent.

> U - Unban.
It is the ability to unban a user with the command: /unban <username> or <IP>.

> t - Topic.
You can change the Topic (command /topic) from within the chat window.

> m - Motd.
You can change the Motd (command /setmotd) The MOTD can be modified from within the chat window.

> w - Watch Commands.  
With this level you can see the commands of the other users (Watch commands). This level allows users to be able to read the commands typed by anyone including admins. Anything post '/' shows to users with this Access.

> i - Show IPs.
You can see user's IPs when they enter.

> l - Show Levels.
You can see the levels of the user commands in chat by using the command: /level <username>.
Allows the user with this access to view IP, Connection Type and other information about members.

> M - OpMsg.
You can see the Admin messages. The command: /opmsg <text for admins to read only>.
Those who do no possess the level or letter "M" are unable to see these messages.
This is just for the admins to talk to each other discussing room problems etc so should be kept to just admins.

> n - Notice.
You can use the command /notice to anonymously write in chat. Example:  
/notice #c2#<Room> #c1# This is how you fake the Room Talking if you have Notice Command ability.
<Room> This is how you fake the Room Talking if you have Notice Command ability.

> N - Newline.
You can send multiple lines with command: #NEWLINE# or \n.
This is useful for very long texts. Pretty much only useful for bots etc. not really needed for users.

> q - MaxConnections to Room.
This level simply allows a user to make multiple connections with unlimited nicknames or to be able to have quite a lot of clones.
This is used by admins to allow them to enter with Bots or other clients that help with the management of the channel.
This also overrides the /MaxConnections setting.

> r - Redirect.
This is the ability to redirect the channel to another (/redirect somechat_123456789012).
The redirect command sends all of your users to another channel.
It is a command for Admins only.

> p - Private Messages In Channel.
The ability to send private messages (in chat) with the command: /message <username>.
This is not anything else other than a private message.
It can only be read by the user who sends it, the user who receives it and the host of the chat, but only from the server window.

> f - Flood.
You can send flood messages (usually means more then 5 messages within a few seconds time).
Flood messages are enormous trouble for users.
It is best not to insert the letter "f" in the default access, but to reserve only it for admin or friends.

> j - View Kicked By.
Here you can choose if you want to publicly display the name of who performs a kick or ban

> J - View Name of Kicked/Banned.
The ability to see /kick and /ban messages.
This is similar to the above command however this option users will read /kick or /ban <username>
(without seeing who has performed the command).

> * - SetUserLevel.
You can change the access level of other users. (You cannot give a letter that you don't have)
This command allows a user to give a level to another user through the command: /setuserlevel <username> + Access Letter.
The user cannot give someone else a letter they don't have themselves.

> + - Symbol.
Places a + in front of their name in the user list.
This is so users can see who has levels set. (Admins/Agents)

> @ - Symbol.
Places a @ in front of their name in the user list.
This is so users can see who has levels set. (Admins/Agents)


/Users 0
With this you can set the server to show a fake amount of people in the room, setting it to 0 shows the actual number of people in the room.

/Limit 600
You can set a limit on the number of people that can enter the room, if you have a slow connection and your room becomes very busy traffic from people talking in the room can start to get high.

/TrimName 9
Trim name removes the numbers that are on the end of your nick name.
With the trim being nine it removes all the numbers at the end of your name YourName581_34867 but you can change this too any number below nine if you want to have numbers showing.

/MaxConnections 2
Max connections is the amount of times a person from the same ip can be in the room at the same time.
You need to set this so that you can take into mind the bots etc that you are going to have in the room, if you find when you have 2 things in the room and attempt to enter another it wont let it in, you will have to change this setting to suit your needs.

/Zone 3
Was used on the old peer cache network and can be left as 3.
It used to point to diffrent servers from around the world when frontcode was running WinMX.

/WpnConnections 3
This is the amount of primaries that the server will connect to allowing your room to become active and showing on the WinMX Peer Network (WPN).  I would set this to about 4-5 or maybe more if you wish.
Having more connections doesn't make your room show any better on the WPN and just uses up bandwidth, 4-5 should be a good mix of bandwidth and stability.

/ConsoleName Server123_23454
This is the name of the server as it shows in the chat room, you can make it anything you want but you need to keep the numbers on the end.

/ChatPassword
You can set a chat password for your room if you wish to set up a room for a private meeting etc and you can just hand the pass to certain peeps.


The following commands block a user from using these commands in the room and they can only be done in the server window.
If set to "0" they are Enabled, as "1" they are Disabled.

/BlockCommand Redirect=0
If set to "0", this will prevent anyone from redirecting the channel even if they have access level "r".

/BlockCommand Exile=0
Exile is the redirect command used to send a single user to another room with the command: /exile <username> <roomname>
If set on 1 any user can exile a user to another room.

/BlockCommand addPassword=1
This stops the addition of password or logins.
If set to "0" those who possess the level admin can add new passwords from the proper client.
(I would suggest always blocking this ability)

/BlockCommand Notice=0
This allows users who possess level "n" to write anonymously in the chat.

/BlockCommand SetUserLevel=0
This allows users to set user levels for other users as previously explained.
If set on "1" even those who have level "*" can't set levels for other users.

/BlockCommand ChangeUniform=0
If set on "1" this allows the use of the command /changeUniform (only for mod , admin and Cohost).
This command allows us to hide or make visible the @ or + signs to the side to our nicknames in list.
It can also be used to hide or make visible the sign next to another user's nickname, with the command: /changeuniform <username>
This is handy for monitoring the room while looking like a member with basic access but really having full admin access.

/BlockCommand Ignore=0
This blocks the command /ignore <username> which prevents users/you from reading any text from a user you do not wish to see.
If set on "1" it is not Enabled!

/BlockCommand SetColour=1
If set on "1" it stops the command /setcolour <color code>.
For example: /setcolour 12 (type /colour to visualize all the colors) allows you to write all your text with color number 12.
If set on "0" the command is active for everybody.


The following are options to automatically protect our chat, without the aid of a bot!
They are very useful functions for the management of a chatserver.
Set as "1" are active, as "0" inactive.

/setAdvOption HideNoVoice=1
This command set on "1" blocks all things that the user says in the chat window while he has had his voice removed, set to "0" allows admins and ops to still be able to see what that user is saying although normal users can not.

/setAdvOption ShowRefused=1
If this command is set on "1" it shows a message to all users in the chat room when another user attempts to unsuccessfully enter the channel.
It also shows the cause of the unsuccessful entry in the case of a nickname not allowed or if the user is in the ban list.
If set on "0" no explaination is given to the normal users in the chatroom.
The classic opmsg message will still appear only to the admin/mods along with the reason for unsuccessful entry.

/setAdvOption FloodKick=1
Activates the protection of Autokick, which automatically kicks all the users who send flooding messages without level "f".

/setAdvOption AllowInfiniteBan=1
This allows the use of an infinite ban.
All bans will be stored in the file "Banlist" inside the chat folder.

/setAdvOption FilterSpam=1
This is one of the commands that it allows us to avoid the fools who enter our chat to invite users to other chatrooms or websites.
If set to "1", users who spam the chatroom will be automatically kicked. Admins will never be kicked.

/setAdvOption ChatLog=1
This enables logging of the chat, so that we can go back and check anything that was said if necessary.

/setAdvOption SplitLog=0
This is an additional logging function.
If set to "1" the server will divide our logs into 24 hour increments.
This prevents the main log from getting too big as often occurs when hosting a room 24/7.

/setAdvOption AutoAdmin=0
This function is for the host of the channel only.
If set to "1", the server will automatically set us or our bot as cohost when we enter with WinMX or any client without the need to enter a password.

/setAdvOption checkNameCloning=1
If set to "1" the server will check for identical nicknames so that nobody can clone another person.
On some occasions a user may apprear to be in the channel and therefore if they attempt to enter again the server shows the message as follows if the user tries to still reenter the room with the same nickname.

25/03/06 02:27:55> simone137_26185 (100.0.0.1) Refused Connection (Cloned Name)

It is up to you to decide if it is the same user or someone attempting to clone a nickname.
You can use the "Whois" command in WinMX to check if the user is the same.
If it is the same user, the result will be user "offline" and therefore you will simply need to kick the old nickname in the list to allow the user to reenter the chatroom with the same name.

/setAdvOption NickColours=1
This command allows users to see coloured nicknames as the owner intended them to be seen.
If set to "0" the colours set in the Text Format section of the configuartion will be applied to nicknames.

/setAdvOption ColourCodesVisible=0
This function allows you to enable or disable on demand the visibility of colours in the channel.

/setAdvOption ViewJoinAttempts=1
If set as "1", this function shows Admins when a users attempt to join the channel fails.
It may be in the case that the user is banned because his or her nickname is not allowed your channel, or it could be due to other connection problems.

/setAdvOption RenameMessage=$OLDNAME$#c58 # has changed their nickname to $NEWNAME$,
This informs us that a user has changed his nickname.


The following are the messages that are shown when someone uses a password or login, or when a user surrenders the received levels and returns to normal user status!!
Change them to your liking

/setAdvOption Get@Msg=$NAME $it is admin
/setAdvOption Lose@Msg=$NAME $it is not admin anymore
/setAdvOption Get+Msg=$NAME $it is agent
/setAdvOption Lose+Msg=$NAME $it is not agent anymore

/setAdvOption LogLimit=5
This function sets the scroll of the server or the number of characters that our server will contain in the window.
If set as "5", 5000 characters will remain on the server and old text will be removed to make space for the new.
This can be set between 5 and 50 (the higher the number the slower it will be to execute the /reload command).
Therefore it is suggested to leave this set as "5".

/ShowRoom 1
If set as "1" the server will be visible on the list of WinMX channels.
If set as "0" the channel won't be visible and only those who know the exact name of the channel will be able to enter.

/Block @msn
This allows you to block offensive words like swear words etc and email companies.

/Replace fuck=f***
Instead of blocking the swear words you can also replace them like above. This can be very funny if you choose to replace popular words wid wacky ones.


Time to get started!!
Now you have configured the config file its time to get ready to start the server. Go to



you will notice that there is a host file here. This is the connection method that FXServe connects to when you open the room. The current host file has been known to throw up a error like this in the server.



The reason for this is the host file can't auto update and everytime peer caches go offline you will need to modify the host file. We have realeased a patch that goes into the folder instead like this



That auto updates and doesnt require you to do any other maintence, the patch can be downloaded from here:
Third Party Patch - Save this inside your FXServer Folder.

You shouldn't get this error again. If you do just close the server and re-open and it should work fine.


Open For Business!!
Now we have everything set up we are ready to start the server, double click on the FXServer Icon or your Desktop shortcut created earlier and the server will open looking like this



At the bottom in blue will have your room name, copy this name to the Filter bar in the Chat screen on WinMX and click join.
If you have problems joining the room it maybe that you have a router and you need to do loop back to get in.
Click here to follow instructions on how to enter your room via loop back.

You can now give people the name of your room and if 'Show Room' is ticked on the left hand side and the
address's in the box above are green then your room will be showing up on the list if someone does a search for it.
It can take up to a minute sometimes for the room to show on the list and for changes to take place, so before doing a search for the room leave it to be open for at least 30 seconds.

When you have the server open you can still make modifications to the Config file, but for them to take effect you need to type /reload at the bottom of the server.



Once you are in the room you will need to log in if you havent set it to 'Auto Login for Local Host' with this option /setAdvOption AutoAdmin=0.
To login you type /login <password you set> into the chat bar in WinMX.
Once you have logged in as admin, you have access to a group of options.
In the chat box again type /help and a list of option appear like this.



From here you have full control over the functions of the room.
You can change the motd topic, add passwords, well read the list you can do 'you name it' lol.


Known Issues:

The /redirect command:
When using /redirect to move everyone from one channel to another channel will often loose a few users, This often fails to users on a dynamic IP like DSL that will change frequently, and also when users are on a wireless router or a DSL multi/networked connection (having more than 1 pc using same connection) will either not move or will fall out and will not reach the destination.

The /exile command:
When using /exile to send a user from one channel to another channel will often fail if the user is on a dynamic IP like DSL that will change frequently, and also when that user is on a wireless router or a DSL multi/networked connection (having more than 1 pc using same connection) the user will probably not move.

Connection Errors:
When a user cannot enter the channel due to a connection error, you will see an admin message stating the users IP and an error code,
There are three main error codes, -5, -999, -1000
Error Code -5 We do not have the information on at this time.
Error Codes -999 and -1000 means that the user who is trying to enter the channel has some connection problems, his/her provider has got connection or stability problems, so the user isn't able to enter the channel, there is nothing the host can do about this.

Users Can't Enter
If people are reporting not being able to get into your room you need to check a few things.
The first being do you have a router or DSL modem with NAT. If you do have you forwarded ports like you had to do with WinMX?
Help with Routers/DSL Modems
Is the firewall installed allowing the program on the server port your using.
There are a few guides for setting up WinMX with diffrent firewalls and it is just the same for setting up the chat server but the chat server only needs one port opened for TCP.
Firewall Guides

Hosts's file not found.
This is because the host file that comes with FXServe needs to be manually updated everytime there is a change to the caches. As mentioned above we have released a patch that can be downloaded Patch Downloads and can be installed following the instructions above.



Thanks to Fede for writing a decent help file that we have used and expanded on. Thanks also go to Tiny and Max for writing this guide for help with FXServer.

©2005-2017 WinMXWorld.com. All rights reserved. Page last updated Sun Jun 18 2017