Author Topic: FX Chat Server (Read 57070 times)

GhostShip · « **Reply #60 on:** February 22, 2006, 11:23:14 am »

Hmm learn something new every day

Cheers Willscotn

TheMacDaddy · « **Reply #61 on:** May 04, 2006, 11:10:19 pm »

ok i need a little help here if anyone can??

i use fxserve FXServer137

i am not on router and i have no connections issues with winmx
but i keep seeing this message when just one person trys to enter the room

[Admin Msg] (xxx.xxx.xx.xxx) Connection Failed | code -999

or

[Admin Msg] (xxx.xxx.xx.xxx) Connection Failed | code -1000

can anyone please tell me what this means and is there a way of fixing it?

it also happens with ouka and wcs so its not just fx that has this problem

KM · « **Reply #62 on:** May 05, 2006, 07:47:28 am »

if you get errors with any server when that 1 user tries to join - have you considered there could be a problem their end rather than your end? of course there is a whole load of things that could be wrong their end, changing client could fix it

*^*Åü§§ïëgïrl*^* · « **Reply #63 on:** May 11, 2006, 04:22:11 am »

We are having quite a few join attempts with the same -999 error. Sometimes affecting one user and sometimes affecting more. And then sometimes same user gets in but is denied entry after rebooting and trying to regain entry.
Also, redirecting seems to be an issue with some users 'sticking' in the old room. An /exile <roomname> won't move them, they just stay locked in the old room. On one redirect attempt I was unable to regain entry to the host room after closing my own, -999 error.

Is this a server bug, an ISP issue, PC related? Or is FXServer not really suited for a dynamic dial-up host

Stevi · « **Reply #64 on:** May 14, 2006, 01:00:52 am »

The error -999 is a server issue.

~~Josh~~ · « **Reply #65 on:** June 10, 2006, 10:55:01 pm »

For everyone having issues with the new patch and fxserver it has been proven that in fact it does not break fxserver!

https://www.winmxunlimited.net/tutorials/getfxserverconnected.html

GhostShip · « **Reply #66 on:** June 15, 2006, 01:06:41 pm »

New FxServer out folks

http://fxserver.p2pzone.net/

Quote

14-6-06 v.1.3.8

/setAdvOption ShowRefused=1. If you set to 0, when the server refuses a connection will not show the reason to the refused user. (for instance "invalid nickname")
/setAdvOption HideNoVoice=1 . If Admins don't want to read what devoiced users are typing.
/ChangeUniform <username> - Switches between the symbols @, +, and nothing. Username must be an Admin. If you don't enter the username, it will be applyed to yourself.
/ignore <username> Use this to ignore username's messages. Type it again to unignore.
/BlockCommand SetColour=0. Set to 1 if you want to prevent the use of /setcolour.
/BlockCommand ChangeUniform=0.and /BlockCommand Ignore=0. Same as above for /ChangeUniform and /ignore
/logout Quick reset of your access level. (still /setuserlevel <yourname> -A is working).

Several fixes and a quite annoying security bug eliminated.
Connection to WPN should now work again for those who haven't got the Piepatch.
Little restyling on the option window.
Added a help page for the server (also in chm format available for offline reference)

Nice to see its been updated to respond to those not wishing to use a host file, Cheers Fedez

GhostShip · « **Reply #67 on:** June 15, 2006, 09:20:29 pm »

It seems that FxServer is not working correctly or should I say has been damaged on purpose to not work with the the DLL fix.
This childish behaviour will mean that I will no longer post FxServer updates here and inform others not to use it.

None of the other server programmers has done such a thing and I expected better of Fedez, perhaps Sabre is a bad influence on him.

lnp · « **Reply #68 on:** June 17, 2006, 11:10:09 pm »

Can you please explain those changes in detail ? i am not that much of a technical genius, so i need the long version of what happened with FXS server. I have some problems with it blocking users saying "invalid nickname". Any idea what causes this ? Otherwise I might have to return to previous version

GhostShip · « **Reply #69 on:** June 20, 2006, 10:24:28 pm »

It seems Fede has seen the light.

Quote

Fede83 Date: 2006/06/21(Wed) 06:05

I decided to un-block the dll because i think every user has to be free to choose which side to take part of (and i apologize with users for having blocked it in the last version). But notice, i don't approve the winmxgroup members' behaviour towards who doesn't think like them. Not allowing the dll is bad? maybe it is, cause many of the users who chose the winmxgroup's patch couldn't use Fxserver anymore.
So, I will allow any of the two patches on my program. Any of the groups feel free to contact me if something has to be done on the server to make the owned patch work. But please don't ask me to interfere in any way with the rival or to prefer one side instead of the other.

This was all anyone asked for in the first place Fede.

reef · « **Reply #70 on:** June 21, 2006, 11:06:57 am »

well thats great to see....glad fede has changed his thinking as many other FXServer users will be glad to see...its never too late to do the right thing.So i assume a 1.3.9 is in the works???

cheerz

KM · « **Reply #71 on:** June 22, 2006, 12:02:30 am »

well i think it may be too late anyway, everyone has already come up with alternate solutions... either using older versions and blocking updates or switching chat server to one that works

GhostShip · « **Reply #72 on:** June 22, 2006, 10:59:34 am »

Here is the latest release folks

http://fxserver.p2pzone.net/

Quote

21-6-06 v.1.3.9

/blind <Username>.Analogous of /Ignore. This "makes blind" Username. It means that your messages will not be seen from that user. /ignore instead makes username's message invisible to you. /BlockCommand Blind=0 in order to forbid this command.

/addpassword and /changeuniform bugs fixed.
Dll patch unblocked

Its nice to see politics has been removed from this server and dll blocking that should never have been there has been removed.

Cheers Fede

»°Ð{¥}§°« *£õ®Ð* · « **Reply #73 on:** June 25, 2006, 04:40:03 am »

Question

I was using 1.3.2 the modified version of FX on this site and was able to bind port to allow wcs as well to connect to winmx
but now i have 1.3.9 the newest release and wcs now wont bind?

is there a way to bind them so i can do my motd files for both fx and wcs?

Thanks

SSJ4Gogeta216 · « **Reply #74 on:** June 28, 2006, 02:24:22 pm »

I run a [FXS][FXServ 1.3.9] Room and I have a Metis bot[2.70 test 6]. Btw,.,. thier both connected "WPN-Green light=good to go" On the [FXS] main front window I do have cheacked-in the following.."Local Host is always a Co-Host" and "Appeer as Admin".. Now in the [FXS] config file I have in there..

Code: [Select]

/DefaultAccess acCvJj
/addPassword adminpassw=A

Now in the Metis window I would type "/level"

Code: [Select]

[12:25:31] > /level
[12:25:31] < Your level is: AvcCatmpkKbBUwilLfnrqNMjJ*+@ Co-Host
[12:25:31] < Joined since: 11:05:01  27/06/06
[12:25:31] < Messages: 17
[12:25:31] < Your IP: xx.xx.xxx.xx

Not that it matters but I replaced my IP with xXx lol.. But annyways,.,. their is a (f) in the access level line, so this would mean that I can flood my own room. Also, in the normal WinMX chat window I did type /level and so I get the same results. Check this out,.,. in the MXC.xml file of Metis I found the following..

Code: [Select]

<BotFloodControl value="2000"/>
<DefaultCmdFloodProt value="40"/>

I did try the following (1) Putting a higher Number on both commands. (2) Removing the 2 commands.= Both of them got me nowere fast.. Can some one help?? hehe Now before some one ask..

Code: [Select]

What are you trying to do?
annnnnd why would you want to flood your own room?
AAaaand uuuhhmmmm What are you talking about? lol..

Alright I'll answer,. Im trying to put-up some room rules and some cool-tips about WinMX and maybe later some ascii Pic(s) ,.,.lol Now before I enterd in this topic I reserched in a couple of help sites, and the all advise the same thing,.,.,. that its not a good idea in the [FXS] Config file to add (f) to the defult "/DefaultAccess acCvJjf" and I agree, it would be a mess realy quick,.,Btw I only have this problem, my other Admin are working just fine,.,. so my next best guess is to create a usergroup Script that I the Co-Host can flood the room..but I can't script well,. infact can't at all. But I can come-up with some great Ideas tho.. lol.. so, plz could you help? Can some one reply this post with a Script? thx-a-lot.. you can reply, pm-me or stop-in ---> Anime¸.·´¯`·.¸._ÉÑÇÒÐË§_.¸.·´¯`·.4_216A14431A2E <--- latersszzz

Faithless_Sniper · « **Reply #75 on:** July 23, 2006, 12:08:03 pm »

i think FXServ is reasonbly good the only thing i would like to see is a menue where i can add the WPN connections for example

Peer 1 = IP ADDRESS
Peer 2 = IP ADDRESS
Peer 3 = IP ADDRESS
Peer 4 = IP ADDRESS
Peer 5 = IP ADDRESS

so that i can choose what servers i connect to

Lagerlout666 · « **Reply #76 on:** July 28, 2006, 02:15:21 pm »

I also have the same problem that aussie's girl published, I have stopped usin fx serve an moved to wcs advanced as the /redirect command never moved certain peep's, i started to think that it was down to certain charcter's in peeps name but i tested this with asci name maker on sometimes even my own bot wouldnt leave but a reboot of bot an bk in old room with same name an then redirect an it would go??
I dont understand why just every now and again members become superglued to the old room an it became so annoying losin member's i got rid, i liked fx serve an this problem has really put me off it an have become very happy wid my advance wcs but the other admin want a change bk and as a democratic room i have too look into if this problem is going to be fixed, or has been fixed, an if it has hidin the fact to keep my own way

(very democratic

)

Liquid · « **Reply #77 on:** July 28, 2006, 11:18:07 pm »

FXserver will not redirect those with Co-Host access
And many times people with Dynamic Ips do not get redirected for some reason im not sure of why
Co-Host access is being the same as the server so whoever has it cannot be moved unless that access is removed with
/Setuserlevel [name] -A
Resets teh access then redirect
It should work better but yea if theres probs just make sure like u exile them then
It might work for those left behind if they dont have the access Co-Host

Lagerlout666 · « **Reply #78 on:** July 28, 2006, 11:42:16 pm »

The exile doesnt work on them, its like they are superglued to the room, ive stopped using fx serve cause of this i just wanted peeps to know that at the mo the best word for this prog is BETA. i know their are trial's and errors with programming but if you look in the english part of FX serve fourum i posted this prob an it lies un replyed to i think this is a major problem as losing member's just aint good, I want peeps to no about this so instead of spendin pointless hours thinking its their error like i have changin everything an fightin wid firewall's; when its the server. Cause like most clever peeps before changin server they check out any fourums for any probs to plan or avoid.

Drove me mad, its a shame Hopefully wid postin this prob fede might fix quick cause in my eyes :shock: it dont work right and is useless to me

cord73 · « **Reply #79 on:** July 29, 2006, 10:36:32 pm »

hey all i ive been trying to help someone with fxserver heres the problem hes on a ethernet hub when he opens a room i try to get in it i dont but he can get his bot and himself in i have had other friends to see if they can get in but they dont succeed either if someone can plz tell me why would be great

Author Topic: FX Chat Server (Read 57070 times)

KM

lnp

KM

SSJ4Gogeta216

Faithless_Sniper

Liquid