Page 18 of 21

Posted: Tue Sep 27, 2005 4:46 pm
by Protoman X
Pretty technical update here... New version can be found here or via the autoupdater
http://ouka.dip.jp/ChatServerE_510f_2005_09_27_1200.zip

New Command:
#admincmd setfirstnode <IP:TCPPORT>

[Example] #admincmd setfirstnode 219.45.xxx.xxx:6699

That command overwrites the original node information (82.195.155.5) and tries connecting to the specified <IP:TCPPORT>
That will be the first node that the server tries to connect to.
(This is for establishing a primary connection to the WPN)

However with this method if the specified MX room doesn't have a primary connection it is not possible to connect.*

If the specified <IP:TCPPORT> is invalidated then returning to the original node (82.195.155.5) is as follows:
#admincmd setfirstnodeoff

Because 09_27_1200 versions acquire node information at the connection destination when the first connection is made, it is possible because of the crowded condition that the original node will not connect easily.

*I assume this means you can set any channel host's IP and use them to get on the WPN since they're already a primary. In other words bypassing the cache servers altogether.

Posted: Wed Sep 28, 2005 5:46 pm
by Love
Tks all, my room is listing well now. Just sometimes... loses primaries to 0/8 nodes and room can't list but I know what to do. I leave it disconnected and try to connect 2 hrs later... then it will load with primaries 8/8. The past 2 days I was connected 18 hrs then 6 hrs no connection and then repeated next day... connected 12 hrs and then disconnected 2 hrs ... and then I tried to connect and it works again. Tks everyone.

Posted: Sun Oct 16, 2005 8:09 pm
by Protoman X
New Test version availible.

#admincmd chatpauseon / #admincmd chatpauseoff
With chatpauseon the messages of all users are disabled except for Host, CoHosts, and Admins.

new stuff to add to RCMSConf.txt
[Language]
$ChatPauseOn$="Chat Pause"
$ChatPauseOnNotify$="Now user's chat is suspended!"
$ChatPauseOff$="Chat Continue"
$ChatPauseOffNotify$="Now user's chat is available!"

The test version can be found here.

For those uncomfortable with test versions just wait until the autoupdater grabs the new version when testing is done :)

Posted: Tue Oct 18, 2005 4:53 pm
by JASON
Reccommended update here. Two bugs fixed, one minor and one major, definetly reccomend you updgrade to this newest version if possible :)

English
Japanese

Big Thanks go out to Ouka :)

Posted: Thu Oct 27, 2005 4:34 pm
by Protoman X
Test Version

Correction test of problem that caused redirecting to fail since WinMX 3.53 was released.

Redirecting other than the following commands would act as a usual kick.
Please use the following commands when you want redirect.

#usercmd redirectto <UserName> <ChannelName>
#admincmd /Redirect <ChannelName>

Japanese
http://ouka.dip.jp/ChatServerJ_520b_2005_10_27_1900.zip

English
http://ouka.dip.jp/ChatServerE_520b_2005_10_27_1900.zip

Posted: Fri Nov 11, 2005 2:04 am
by JASON
New update here for you all 20051110-1800. (autoupdate is picking up a previous version to this)
Three small bugs fixed in this version, colours in replaced words, the /kickip and /login commands.

Big Thanks go out to Ouka 8)


English
Japanese

Posted: Fri Nov 18, 2005 11:00 pm
by Protoman X
Test Version

Lots of customizable things added today.

The messages for /help and /server can now include colors.
(Ouka only mentioned those two specifically, but from the default settings he gave looks like you can add colors to most/all? customizable notice)


Add the following if you want to update RCMSconf.txt. If you're one of the folks who doesn't customize anything then just use the RCMSConf.txt that's provided in the zip file.

$HiddenListStart$="#c4#Listing Hidden user:"
$HiddenListEnd$="#c5#Hidden user listing complete."
$HiddenListNotify$="There is no Hidden user."

$IgnoreListStart$="#c5#Listing Ignore user:"
$IgnoreListEnd$="#c5#Ignore user listing complete."
$IgnoreListNotify$="There is no Ignore user."

$AdminListStart$="#c4#Listing Admin user:"
$AdminListEnd$="#c5#Admin user listing complete."
$AdminListNotify$="There is no Admin."

$PrimaryListStart$="#c4#Listing Primary Link:"
$PrimaryListEnd$="#c5#Primary Link listing complete."
$PrimaryListNotify$="There is no Primary Link."

$BansListStart$="#c4#Listing Banned user and associated IPs:"
$BansListEnd$="#c5#Banned user listing complete."
$BansListNotify$="There is no Banned user."

$ClearDelayNotify$="PenaltyList Cleared"
$ClearBansNotify$="BansList Cleared"

$SetVirtualUser$="Set Virtual User"




Japanese
http://ouka.dip.jp/ChatServerJ_520d_2005_11_18_1900.zip

English
http://ouka.dip.jp/ChatServerE_520d_2005_11_18_1900.zip

Posted: Sun Nov 20, 2005 5:36 am
by Casca
Many thanks Ouka & Protoman for the new customizable items. :D
Some of them where a request from me. But in the process at least a couple of them where removed: :(

$Passcode$="Passcode"
$PasscodeNotify$="Passcode Accepted: "

They now are showed in Japan version. :(

Obviously I can copy them from previous versions, but it will be appreciated if included again in new versions.

By the way.... I have seen that several items use the "Block" word and some use the "Brock" one. Is there a different meaning ??
Mi english is not so good sorry. :(

Anyway many thanks to Ouka y really appreciate its nice work... :)

link dont work

Posted: Sun Nov 20, 2005 12:28 pm
by Fast-007
that link dont work so download it here o click on this link




http://nanto2005.dyndns.org/files/ChatS ... 8_1900.zip

Posted: Sun Nov 20, 2005 12:32 pm
by Fast-007
Many thanks Ouka & Protoman for the new customizable items.
Some of them where a request from me. But in the process at least a couple of them where removed



do you feel happy now ?

Posted: Sun Nov 20, 2005 8:25 pm
by Casca
Although I am using WinMX 3.54 b4 and ChatServerE_520d_2005_11_18_19002.zip, te command:

#UserCmd /level <name>

Reports a WinMX 3.53 Client Name, instead of WinMX 3.54 b4. Is this a WinMX bug or a Server bug??

Posted: Sun Nov 20, 2005 9:28 pm
by Casca
Although I am using WinMX 3.54 b4 and ChatServerE_520d_2005_11_18_1900.zip ther command:

#usercmd /level <Name>

reports a Clientname WinMX 3.53. instead of WinMX 3.54b4. Is this a WinMX bug or a Chat Server bug ???

I checked the Ouka Chanel Server, and now Ouka Chat Server reports Status after Connet to WPN. Thanks Ouka :D

Posted: Sun Nov 20, 2005 10:04 pm
by Protoman X
It's neither actually. 3.53 and 3.54 both identify themselves the same way (as far as chat goes). The only differences between the two in chatting that I'm aware of is that 3.54 fixed a bug with displaying the channel list.
Casca wrote:By the way.... I have seen that several items use the "Block" word and some use the "Brock" one. Is there a different meaning ??
Mi english is not so good sorry.
The reason for this is because Japanese has no "L" sound. And the Japanese "R" is more of a cross between the English L and R. So the same sound is used for both R and L and is basically used interchangably in Japan for foreign loanwords. The same is true of V and B. Japanese has no V sound so it subsitutes B, since it's the closest approximation. The same with "th" and "su"

As a result you can get some pretty bizarre looking results in English sometimes that's generally called "Engrish". Check out http://www.engrish.com for some rather amusing failures to translate into english :)

Though... the same can be said for the addition of Japanese or Chinese characters to hats, shirts and tattoos found in the US or Europe, which are often non-sensical as well. Demon Bird Moth Balls anyone?



Image

Posted: Mon Nov 21, 2005 12:06 am
by Casca
Thanks Protoman for your explanation. I supposed it was some kind of translation problem, but I asked just to be sure. :D

it could be a sever problem

Posted: Mon Nov 21, 2005 2:01 pm
by Fast-007
it could be a bug

/level pbb000_44431

<> Messages: 158
<> Client Name: WinMX v3.54 beta 4 BendMX 3.9.9 Alpha 2
<> Channel Name: CHAT LATINO CANAL _AF7C88421A22
<> Stay Time: 17h26m47s [4m55s]
<> IP: 83.xxx.xxx.xxx [xx.Red-83-xxx-xxx.dynamicIP.rima-tde.net]
<> NodeIP/Port: 220.22.255.1:6257 [01ff16dc1871]



it's very strange , of course i do not want to reveal her real IP so i change it for xxx but the level show Winmx v3.54 beta