lynxy/vnet

VNet Repo

vnet's Issues

Channel flags

Channel flags need to be implemented

Strings config file needed

All strings in the project need to be loaded from an external file. This allows localization and custom strings. Use some function that uses String.Format() to display these strings

Banned users should never hear a response

Banned users should never hear a response. Socket level

Invisible users

Need to implemented invisible feature so we can start writing our code to take that into consideration

Wildcarding

Wildcarding needs to be redone. The current implementation looks rather sloppy, and only works for List, not User, which would be desirable as well so you don't have to type out the full name of a user for a single-user command.

Regex checks needed for usernames and channel names

Savable config data needed to check usernames and channel names against a custom regular expression

Allow locking of a channel

Channels should be able to be locked by mod+, or protected with a password by op+

Channel owner timeout

Add an Owner timeout; that is if an Owner spends more than 15 minutes out of channel, s/he will lose Owner and the next in line will become new Owner

Check for flooding

Flood checking. Three types of floods:

1. Fast connections from same IP
2. Any type of chat message spammed too fast
3. A total packet count flood. Exclude binary packets (eg uploading icon)

Voice ability

Lowest priority: Enable voice capabilities on VectorNet

CommandHandler.cs needs restructuring

CommandHandler.cs is quite messy and rather inflexible code. It needs to be redesigned. No more "ExtractChannelFromParameterOne()" stuff - it should be intelligent! Consider looking at command parsers in other projects

/op command

As of now, /op performs a check to make sure there is only 1 operator in the channel (if the user is an operator). Is this even needed? Investigate the matter

Whispering/ignoring/etc invisible users

Should invisible users (or perhaps just invisible mod/admin) be able to be whispered? Or should the whisperer get the "user not found" error if s/he can't see their whisper target (but message goes through anyway)? In which case, perhaps there would be a "session" which the admin/mod can close at will which allows certain users to whisper them without seeing the error message.

Wildcards for usernames in commands

Need to discuss how wildcarding will work. Eg, on Lynxy's old server, the command "pop":
/pop Lynxy* channel
/pop *@ALL channel

Unban users from channel when channel empty

Channels that do not get closed upon last user leaving do not properly unban all users