ID:11156
 
My weekend project is to get as far with guild stuff as I can. This is the best time for adding cool features, so I'd like to get your input.

Here is a revised mock-up of the guild settings page, taking into account your previous requests:



As you can see there, you are able to add all the Ranks you'd like, name them however you like, and give each one whichever permissions you'd like. This also shows how applicants will show up -- clicking the 'view' link will take you to a page with their application info and the ability to approve or deny them.

Are there additional permissions that should added?

Keep in mind that ranks don't have to be about permissions...you might choose to not give any ranks special permissions, but have ranks for other purposes. For example, a chess guild might base them on people's chess rankings without providing actual permissions to alter the site.

Comment early and often!

[edit]
Here's a revision, based on comments received today. Thanks in particular to Elation for some good ideas. My implementation of these, as usual, isn't particularly pretty, but we can improve it over time. The important thing here is figuring out what functionality should be available.



Changes from earlier:

- I removed the "Add Member" functionality, fearing exploits. People may create a 'funky' guild and add people without their permission, associating them with something unsavory. So instead we'll require a person to apply to join a guild.

- Added 'Applicants accepted as rank' setting. This allows you to set a rank as being able to accept applicants without being able to set the applicant's rank.

- Added the concept of inheritance to the ranks. Maybe someday we'll even show a DM-like UI...:)

- To keep from having a checkbox item for each possible privilege under each rank, changed it so only the chosen privileges for a rank are displayed, and you use a popup to add a privilege.
Looks good enough. Keep up the work, though. ;)
Are you beta testing these guilds in the batcave or something?

Oh yeah, lookin' good.
Its nice, but does this tie in with the "publishing" games thing ? (to get it out of unpublished) I'm getting rather confused on whats happening about that, the most I've got out of people is "it'll be related to guilds". I occasionaly post about it on the forums, but I never seem to get any answers.

If anyone can actualy fill me in on what the hell is going on about all this, It'd be greatly appreciated.
Are you beta testing these guilds in the batcave or something?

Yes...or we will be, once I actually implement them.


Its nice, but does this tie in with the "publishing" games thing ?

Our desire is to remove the existing concept of published, and make it so you can find games based on their being listed on Member sites and guild sites. So our Members and guilds will dictate what "published" means, in essence, and the BYOND Staff will get out of the business of having to review every game that is submitted. We are still working out some of the details of this.
Ah ok, thanks for clearing that up, it actualy makes a bit more sense now.
I'm looking forward to more screenshots of game-like processes.
there needs to be alot more permissions,

View Aplicants, Edit Aplicats, Accept aplicants that kind of thing. YOu don't want 1 person having control over the members or, everybody
YOu don't want 1 person having control over the members or, everybody

You can give multiple people a rank that allows them to edit everything (and of course the guild owner can always do everything).

But perhaps we should remove the "Edit everything" concept and instead have a few more settings, such as:

- Accept applicants
- Admin existing members
- Ban non-members
- Manage files

Perhaps we need a new setting that only allows applicants to be accepted as a certain rank (so someone can't add someone and let them trash everything).

We should also provide some logging that shows all the actions taken in the last month, so people have a harder time abusing privileges.

Thanks for the suggestion. Keep them coming!
You guys were talking about having it read your guild in games, so maybe you should have a checkbox like "Disable Guild Reading" so that games can't see what guild your members are in.
Deadron said:
So our Members and guilds will dictate what "published" means, in essence, and the BYOND Staff will get out of the business of having to review every game that is submitted. We are still working out some of the details of this.

Interesting. What about games like Hentai Hill?
I expect the staff would still step in to remove published games if they are reported by BYONDers, so I guess it's not a problem.

The rank + guild system looks good. Although the more variable, diverse permissions you add, the more cluttered it is going to be.

My suggestion would be this:

Each rank- such as controller, or blogger, or whatever you may choose, starts off displayed on the guild-settins page as just single words...like:

-Controller
-Blogger
-Grunt

Then, if you add in some nifty div-ing/javascriptin'/CSSin' or whatever allows for it, when you click the rank's names the settings assigned to each rank will appear.

So from what you see above, if you then clicked Blogger you'd see:

-Controller
-Blogger
[x] can post
[ ] can hire new members
[x] can ban non-members
-Grunt

Also what would be better, if it's not too much to ask, is not endless checklists of privileges and stuff, but drop down boxes.
So ranks start off having no priveledges, but you click "Add new priveledge" then select a drop down box that appears to have the specific ability (also would be the option to turn those abilities off, as I will show in my next point).
That would mean the screen wouldn't get clogged up with lots of empty checkboxes, but simply only display what the rank does have, being much more optimal in layout and space.

Also, if this isn't getting too complicated, "link" ranks into each other, like a parent/child system.

-Controller
-Blogger
-Major
[x] Can hire new members
[x] Can ban non-members
-Grunt
Inherit from [Major]
[ ] Can hire new members


So you see, the Grunt has everything the major does, except the things changed there.

I dunno how that could be layed out. Either have the "Inherit from []" option (that can be activated but does not have to be), or working like this:

-Controller
-Blogger
-Major
[x] Can hire new members
[x] Can ban non-members
---Grunt
---[ ] Can hire new members

So the grunt abilities would fold away inside the Major rank if you 'minused' the Major rank, and it'd inherit everything the major had, whilst also you could change specific parts of it.

Think the object tree system in DM.

You could have things like:

-Controller
[x] Can do everything
-Blogger
[x] Can make blog posts
[x] Can edit blog posts
[x] Can edit/delete comments
[x] Can edit CSS
---Reporter
---[ ] Can edit CSS
------Moderator
------[ ] Can make blog posts


Do you see the kind of thing I'm getting at?
The Reporter rank is contained inside the Blogger rank and inherits from it's parent (but cannot edit the CSS), and the Moderator rank inherits all from it's parent (the reporter rank), except all they can do is edit posts and comments.

It'd be a lot easier to organise things. It'd also be a hell of a lot more work on your behalf to get working, probably buggy for a while until it was fixed and stuff. But y'know, it'd rock.
Some good UI ideas. I'll take those into consideration.

My usual instinct for simplicity makes me not want to do a DM-style tree, but it might have some benefits. If we go that route, I'm not going to try and actually implement a visual tree, though...:)

Instead you'd just set a rank as the parent of that rank, and it would inherit those permissions. I will consider that.
Deadron said:
Instead you'd just set a rank as the parent of that rank, and it would inherit those permissions.

Yeah, that's probably more practical. People could then organise the lists however they wanted that way- it wouldn't be too hard for a person to out the whole blogger-reporter-moderator system by just placing each rank underneath eachother, anyway.

Keep up the good work. =p Or don't. I sort of don't mind either way. =/
But uh, keep up the good work.
Okay, I edited the post with changes based on the suggestions received today. Thanks!

Now to make things work...
I still think you should be able to choose if a game can read your guild or not. :/
I still think you should be able to choose if a game can read your guild or not. :/

That may be...but we haven't worked out the API for that feature yet, so I'm not attempting to include the option right now.
The question of the layout comes up however, in the blog posts it should show your rank.

Posted by: person, person rank

:/ to show other people how important or lame they are!
Excellent work, Deadron. :)
I hope they mysterious suits behind Dantom corp. are paying you for all that work...

If I can think of anything more I'll post here later.
Are you still thinking about the idea of having a GUILD_PASSWORD in DM so that we can access information about a guild in a game?

EX: Anyone that is part of my "Legendary Knights" guild, and that has a certain rank, will get suits, or something.

I just think having GUILDS interact with Games would be cool.

[BTW: Long time ago, I brought this up, so if you guys add it in, I would be greatful!]
An example of code for the following:
if(src.client.GUILD("The knights of dawn","23ase0832sdes23")
if(src.client.GUILD_RANK=="Member")
src<<"Welcome member!"


GUILD(Guild Name, Guild Password)
Page: 1 2 3