Yes, that's right, with the imminent release of TDSM b36, Permissions will be available for all to use.  Here are the current features:

• Multiple inherited groups
• Group ranks
• Group prefixes and suffixes
• Build permissions (per group/per user)
• Chat colors
• Built-in chat formatting support
• Restrict auto-download (for authentication)
• Negative permission nodes
• Global/semi-global nodes
• Custom server nodes for server commands
• Chat color, prefix, suffix and separator allow for multiple groups, and are all assigned to user based off of group rank

Still coming:

• Separate user/group files
• Graphical permissions file(s) editor
• In-game commands

Now, how to use it?  Well, I made it to be almost exactly like Minecraft permissions plugins:

Groups:

the file starts out as such:
*groups:*Obviously.  I mean, really, how else would it start?  Unicorns?

The next node can be anything, but usually the name of the group would be useful:
groups:
    *Guest:*
After that, you start getting into the group information.  Usually, info is first:
groups:
    Guest:
        *info:*Which can contain any of the following: default, prefix, suffix, separator, build, color, rank

• Default is whether the group is the one guests are assigned to before registering; default value is false
• Prefix is the chat prefix (before the player's message); default is blank
• Suffix is the chat suffix (after the player's message); default is blank
• Separator is the text between the prefix and the player's message.  Default is ": "
• Build is whether the group/player is able to affect the environment at all; default is false
• Color is the user's/group's chat color; default is 255, 255, 255.  This can be specified either as a three number string (255, 255, 255) or as a hash string ('#ffffff').  Hex can be lowercase or uppercase, but must be in single quotes, as # is the comment character in yaml
• Rank is the group's rank.  Not applicable in User Info; default is -1

The other nodes that a group can have are permissions and inheritance.  Inheritance is a group that the group inherits permissions from.  Permissions is where the permission nodes are put.

The other nodes that a user can have are permissions and groups.  Groups is kind of required, otherwise a lot of the functionality is moot.  Obviously, that's where you put the groups the user is a part of.  Permissions are any extra permission nodes you want only the user to have access to.

So, all that being said, here is a simple example:

groups:
    Guest:
        info:
            default: true
            prefix: '[Guest] '
            suffix: ' - says a loser'
            rank: 1
            color: 200,200,200
        inheritance:
        permissions:
            - tdsm.who
    Member:
        info:
            prefix: '[Member] '
            build: true
            rank: 2
        inheritance:
            - Guest
        permissions:
            - tdsm.time
    Sponsor:
        info:
            prefix: '[Sponsor] '
            build: true
            rank: 4
        inheritance:
        permissions:
            - tdsm.give
    Moderator:
        info:
            prefix: '[Moderator] '
            build: true
            rank: 3
            color: 200,200,0
        inheritance:
            - Member
        permissions:
            - tdsm.kick
            - tdsm.ban
    Admin:
        info:
            prefix: '[Admin] '
            build: true
            rank: 4
            color: '#aa1111'
            separator: '~ '
        inheritance:
            - Sponsor
        permissions:
            - '*'
users:
    Herpina:
        info:
            color: '#ff0055'
        groups:
            - Admin
        permissions:
            - -tdsm.spawnboss
    Derpina:
        info:
            prefix: 'Herpaderp'
        groups:
            - Moderator
            - Sponsor
        permissions:
            - tdsm.op

Please note, there must be an extra newline at the end of the file, or it doesn't work right.  I'm trying to fix that right now.

Also note, the "- -tdsm.spawnboss".  That is a negative node.  Because Herpina is part of the Admin group, she inherits ALL nodes, both from plugins and from the server.  But suppose you don't want Herpina to be able to spawn bosses using the /spawnboss command.  You do a regular node, "- tdsm.spawnboss" and put a - right in front of it.  Make sure the space is between the two dashes.

Next note is that any info block values specified for a player are used BEFORE the group's info, e.g. Herpina is part of the Admin group, but her chat color ('ff0055') will be used instead of Admin's ('aa1111'), and Derpina's prefix will be Herpaderp, despite being part of the Sponsor and Moderator groups.

Finally, remember that you MUST use spaces for all your spacing.  YAML does not handle tabs at all, you will have errors.

DOWNLOAD
ZIP

Download and extract contents, as they are, into your server plugins folder.  This download contains the plugin, the example .yml, and the required YaTools library.

Oh, one more thing.  Server commands and their nodes can be found here:  http://wiki.tdsm.org/index.php?title=Permissions_Nodes

Most of these are self-explanatory as to what they're used for.  I'll explain what you need to feed each on in terms of variable types.  Type them exactly as shown before the = sign, and separate all arguments and values by a space.

-maxplayers = integer value; default is 4; max is 255
-ip = string of the ip address (form xxx.xxx.xxx.xxx) to accept connections from; default is 0.0.0 (any)
-port = integer value for the port to communicate on; default is 7777
-message = MOTD/Greeting message, a string
-worldpath = File path (either relative to the server or absolute) to the world data, must include file name (i.e. world1.wld)
-password = String, represents password to use to allow connections to the server; default null
-allowupdates = true/false, true to allow automatic update feature to run on startup; default true
-npcdoorcancel = true/false true to keep NPCs from opening doors, false to allow; default false
-seed = integer, custom seed to use; default -1
-mapsize = small/medium/large, when not using custom world generation, these generate new worlds in the default manner; default small
-usecustomtiles = true/false, true to use custom tile size when generating a world; default false
-maxtilesx = integer representing the maximum number of tiles per row horizontally; default 4200
-maxtilesy = integer representing the maximum number of tiles per column vertically; default 1200
-numdungeons = integer, the number of dungeons to generate while making a world if customworldgen is true; default 1, max 3
-customworldgen = true/false, whether to use numdungeons and numislands while making a new world; default false
-numislands = integer, number of floating islands to generate while making a new world if customworldgen is true; default 6, max unknown
-whitelist = true/false, whether to use the whitelist for granting/blocking server access; default false
-pidfile = string, path to the PID File (use unknown to me ); default null
-simpleloop = true/false, whether to use the in-testing simple server loop instead of the normal one; default false

Now, how you would use these is as follows:  say I wanted to start a server using port 7850, map size large, with two dungeons and 10 floating islands, using the simple server loop.  You would call the program as follows (don't forget to add "mono " before it if not using Windows):

Terraria_Server.exe -port 7850 -mapsize large -numdungeons 2 -numislands 10 -customworldgen true -simpleloop true

You must remember to set customworldgen to true if you want to use your numdungeons and numislands values.

Also note that using these arguments changes the values saved in server.properties, so if you're only doing one server, you only need to use them as you change them.  For multiple servers off of the same file, it's recommended to have a start script for each that includes the desired arguments.

Which, if you had still been on IRC, DeathCradle, you would have found out about.

First one:  On Windows, with debugmode = false, clients now freeze while connecting at "Requesting world information".

Second one:  One of two things happened:  A) You uploaded b15 without changing its version number, or B) You uploaded the b14 executable as the "b15" update, either of which results in an infinite update loop.

Hey, guys, with DeathCradle's permission, I have set up an IRC channel for us to talk on.  Dev talk, really (as any help questions could be useful to other users if posted on the forums).  But, if anyone can help, I'm sure they'd be willing to.

So anyway, join it!  #TDSM on esper.net

OK, so I'm trying to make a warp plugin, and I can't seem to figure this error out.  This is my onPlayerCommand override:
public override void onPlayerCommand(PlayerCommandEvent Event)
        {
            if (isEnabled == false) { return; }
            string[] commands = Event.getMessage().ToLower().Split(' '); //Split into sections (to lower case to work with it better)
            if (commands.Length > 0)
            {
                if (commands[0] != null && commands[0].Trim().Length > 0) //If it is not nothing, and the string is actually something
                {
                    if (commands[0].Equals("/warp"))
                    {
                        Player sendingPlayer = Event.getPlayer();
                        if(commands[1] == null)
                        {
                            Program.tConsole.WriteLine("[Warp]" + Event.getPlayer().name + "Player used Plugin Command: ");
                            sendingPlayer.sendMessage("Warp plugin, For Build: #" + ServerProtocol, 255, 255f, 255f, 255f);
                            sendingPlayer.sendMessage("For help, type /warp help", 255, 255f, 255f, 255f);
                        }
                        else if(commands[1].Equals("+"))
                        {
                            if(commands[2] == null)
                                sendingPlayer.sendMessage("Add warp error: format must be /warp + <warpname>", 255, 255f, 255f, 255f);
                            else
                            {
                                xml.writeWarp(sendingPlayer, commands[2]);
                            }
                        }
                        else if(commands[1].Equals("-"))
                        {
                            if(commands[2] == null)
                                sendingPlayer.sendMessage("Remove warp error: format must be /warp - <warpname>", 255, 255f, 255f, 255f);
                            else
                            {
                                xml.delWarp(sendingPlayer, commands[2]);
                            }
                        }
                        else if(commands[2] == null)
                        {
                            xml.warp(sendingPlayer, commands[1]);
                        }
                    }
                }
            }
        }And the error I get is:
Error Passing Event PLAYER_COMMAND to Warp
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Warp.Warp.onPlayerCommand(PlayerCommandEvent Event)
   at Terraria_Server.Plugin.PluginManager.processHook(Hooks Hook, Event Event)
Molokai Sent Command: /warp +
No such command!I'll keep working, but anyone got any idea what's happening?

I've been thinking about the permissions thing, and how there's no linking of usernames to accounts on Terraria, and a friend reminded me about Steam IDs, and so I ask, does Terraria transmit any Steam information back and forth that we could tie into to get true permissions (making game names irrelevant and possible to have permissions across name accounts)?

I'd love to be able to have a command you can put in the console to restart the server instead of having to quit and run it again.