Hi,
Well its me again. I have not "yet" been able to test the new version of this server that long. But in the five mins that I was testing the server today I did find some bugs and here they are:
*When a user get kicked out a channel, it tells why they was kick out and who they was kicked out by two (2) times. The user that was kick is not able to rejoin the channel, even if there was no ban set. When the user that was kick do the /names command it shows there name still in the channel. And they can't rejoin untill the server is re started/shutdown
*Have the server auto check the conf file every Xsecs/mins to see if something has been updated in the channel. That will be a lot easyer goto the tray right clicking goto controls and clicking on rehash.
* When you are IRCop and you try to use the /globops command it says that You are not an IRCop
* When you try to use the /locops command it say that you are not an IRCop when you are.
* When you kill a user off of the network. And when they reconnect they cannot join the channel(s) that they where last in when they got killed. This was not tested in two channel but in one #test on vbircd.
By the end of this week I should have a longer list of bugs (hopefully I won't). Becuase then I will beable to test it alittle bit more.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you icely2000 for reporting those bugs and I will check them out, about the "Have the server auto check the conf file every Xsecs/mins to see if something has been updated in the channel" I don't quite understand about that, if you are referring to having the server auto-rehash every so often on it's own is not really a good idea, because there is no need for the server to be rehashing unless there are actual changes which of course you could rehash the server via IRC with /rehash or do it via System Tray.
I will find the bugs you've posted and get them fixed, What IRC Operator mode were you using, just global IRC Operator(+o) or Server Administrator? (+A)
Now if you were just using local IRC Operator (+O), then I can see why /locops and /globops didn't work, because almost all IRC Operator commands check for Global IRC Op flag (+o) and never local IRC op flag (+O) which isn't a good thing, I will also see about changing that, now Only Global IRC Operators have permission to use /globops and many other IRC commands such as /AKILL, and so forth, but local IRC Operators can kill off people on the local server and /kline them.
Anyway I will try to get all bugs fixed and release the final vbIRCd release of v1.1.53 with all bugs fixed with in a week or so.
Again, thank you for reporting these bugs :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well as I was checking the source code of vbIRCd and checked out the CORE of the ircd, it found out that /LOCOPS and /GLOBOPS requires the IRC Operator only flag (+g), which +g gives you access rights to Locops and Globops commands. Just like Unreal requires that flag, plus when sending messages, users with +g set can only see the messages that are broadcasting over the server using /locops and /globops :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been done testing the server (commands mostly). And I found out that this ircd need to start working on state $+ able.
The bug reports that I'm about the list may or maynot be bugs. This is a notice to the users:
| ----------- Beta Tester Infomation --------------- |
| Windows: ME |
| Client: mIRC |
| Script: IRChat |
| vbIRCD Stauts: Still needs a lot of work on |
| sate $+ able |
| IRCop Fags used: ALL |
--------------------------------------------------------
Bugs Found:
1. Chat Server do not support /topic <channel>. This is something that most people who used mIRC uses. So it whould be nice if the server will beable to support this command
2. The command /chgname <nick> <new name> Does not work.
3. When you use the /gnotice <message> Command - Its send your Message two times and not once (1)
4. When you used /SAMODE <#Channel> +I it said that, the mode +I is a unknow mode to the server/network
5. When you make someone part a channel useing /sapart the channel that you made that user part from is kind of like lock down where noone can join/creat that channel.
6. When you make someone nicks change useing /fnick <nick> <New Nick> the channel(s) that he is/was in is no longer join able & the user(s) in the channel(s) cannot/will notsee that Persons new nick.
7. Server Notices do not get sent to people other then the person who sent the server notice
tron21net just in case you don't know its me (Michael) from the mirc message board. or internet_kid2000@yahoo.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Well its me again. I have not "yet" been able to test the new version of this server that long. But in the five mins that I was testing the server today I did find some bugs and here they are:
*When a user get kicked out a channel, it tells why they was kick out and who they was kicked out by two (2) times. The user that was kick is not able to rejoin the channel, even if there was no ban set. When the user that was kick do the /names command it shows there name still in the channel. And they can't rejoin untill the server is re started/shutdown
*Have the server auto check the conf file every Xsecs/mins to see if something has been updated in the channel. That will be a lot easyer goto the tray right clicking goto controls and clicking on rehash.
* When you are IRCop and you try to use the /globops command it says that You are not an IRCop
* When you try to use the /locops command it say that you are not an IRCop when you are.
* When you kill a user off of the network. And when they reconnect they cannot join the channel(s) that they where last in when they got killed. This was not tested in two channel but in one #test on vbircd.
By the end of this week I should have a longer list of bugs (hopefully I won't). Becuase then I will beable to test it alittle bit more.
Thank you icely2000 for reporting those bugs and I will check them out, about the "Have the server auto check the conf file every Xsecs/mins to see if something has been updated in the channel" I don't quite understand about that, if you are referring to having the server auto-rehash every so often on it's own is not really a good idea, because there is no need for the server to be rehashing unless there are actual changes which of course you could rehash the server via IRC with /rehash or do it via System Tray.
I will find the bugs you've posted and get them fixed, What IRC Operator mode were you using, just global IRC Operator(+o) or Server Administrator? (+A)
Now if you were just using local IRC Operator (+O), then I can see why /locops and /globops didn't work, because almost all IRC Operator commands check for Global IRC Op flag (+o) and never local IRC op flag (+O) which isn't a good thing, I will also see about changing that, now Only Global IRC Operators have permission to use /globops and many other IRC commands such as /AKILL, and so forth, but local IRC Operators can kill off people on the local server and /kline them.
Anyway I will try to get all bugs fixed and release the final vbIRCd release of v1.1.53 with all bugs fixed with in a week or so.
Again, thank you for reporting these bugs :)
Well as I was checking the source code of vbIRCd and checked out the CORE of the ircd, it found out that /LOCOPS and /GLOBOPS requires the IRC Operator only flag (+g), which +g gives you access rights to Locops and Globops commands. Just like Unreal requires that flag, plus when sending messages, users with +g set can only see the messages that are broadcasting over the server using /locops and /globops :)
I have been done testing the server (commands mostly). And I found out that this ircd need to start working on state $+ able.
The bug reports that I'm about the list may or maynot be bugs. This is a notice to the users:
| ----------- Beta Tester Infomation --------------- |
| Windows: ME |
| Client: mIRC |
| Script: IRChat |
| vbIRCD Stauts: Still needs a lot of work on |
| sate $+ able |
| IRCop Fags used: ALL |
--------------------------------------------------------
Bugs Found:
1. Chat Server do not support /topic <channel>. This is something that most people who used mIRC uses. So it whould be nice if the server will beable to support this command
2. The command /chgname <nick> <new name> Does not work.
3. When you use the /gnotice <message> Command - Its send your Message two times and not once (1)
4. When you used /SAMODE <#Channel> +I it said that, the mode +I is a unknow mode to the server/network
5. When you make someone part a channel useing /sapart the channel that you made that user part from is kind of like lock down where noone can join/creat that channel.
6. When you make someone nicks change useing /fnick <nick> <New Nick> the channel(s) that he is/was in is no longer join able & the user(s) in the channel(s) cannot/will notsee that Persons new nick.
7. Server Notices do not get sent to people other then the person who sent the server notice
tron21net just in case you don't know its me (Michael) from the mirc message board. or internet_kid2000@yahoo.com