With the amount of time that can span between gathers filling we are running into a huge problem with users being away, closing the tab, or forgetting about the gather and AFK'ing without leaving. I have a few suggestions that could make the system more robust. Some of these may be more difficult to implement and be less beneficial.

1. Remove a user if they close the tab, use an `onbeforeunload` event to alert the user that this will happen
2. Highlight users that have been inactive (show as a lighter gray color) so we know they might be AFK
3. Alert AFK users and if they don't respond remove from gather
4. Use a steam bot to notify users in Steam when a gather is filled / they've been picked as captains

I will honestly help implement these if the admins agree with these and need someone to do so. I'm a web developer by trade.

semi says

With the amount of time that can span between gathers filling we are running into a huge problem with users being away, closing the tab, or forgetting about the gather and AFK'ing without leaving. I have a few suggestions that could make the system more robust. Some of these may be more difficult to implement and be less beneficial.

1. Remove a user if they close the tab, use an `onbeforeunload` event to alert the user that this will happen
2. Highlight users that have been inactive (show as a lighter gray color) so we know they might be AFK
3. Alert AFK users and if they don't respond remove from gather
4. Use a steam bot to notify users in Steam when a gather is filled / they've been picked as captains

I will honestly help implement these if the admins agree with these and need someone to do so. I'm a web developer by trade.

We need to talk about that but someone able to make such changes would be awesome.

Correct, I am unsure if we have any capable developers who can make such changes to the website's ruby rails code.

Simba says

Correct, I am unsure if we have any capable developers who can make such changes to the website's ruby rails code.

Rails?! *cries* ... In any case, I can help, even if I'm not a fan of Rails.

Does that mean you guys agree that the features would be nice to have? :)

I'm all for these changes (except maybe 4) and even want more changes to the gather system.

I'd prefer to have a pick 'em style like the reddit gathers where commanders volunteer and are choosing teams rather than the "best" players. At least you know there will always be a comm for each team and it's a person who wants to command rather than just volunteered by their gather team.

semi, get in touch with me. I'll talk to jiriki and csm to see what we can do. Thanks for the help and suggestions.

Yeah, #4 was a bit of a stretch and not something I'd even want to implement :). I'll get in touch via Steam!

Thanks everyone for listening.

semi says

Yeah, #4 was a bit of a stretch and not something I'd even want to implement :). I'll get in touch via Steam!

Thanks everyone for listening.

Hi semi,

It would be great if you could lend a hand. Please checkout https://github.com/ENSL/ensl.org/tree/develop if you'd like to open a pull request and i'll get them merged.

The site is currently running Ruby 2.1.3 on Rails 3.2.

The plan was to add better test coverage, refactor and at least upgrade to Rails 4.0 but lack of time is currently the blocker.

Cheers

csm says

semi says

Yeah, #4 was a bit of a stretch and not something I'd even want to implement :). I'll get in touch via Steam!

Thanks everyone for listening.

Hi semi,

It would be great if you could lend a hand. Please checkout https://github.com/ENSL/ensl.org/tree/develop if you'd like to open a pull request and i'll get them merged.

The site is currently running Ruby 2.1.3 on Rails 3.2.

The plan was to add better test coverage, refactor and at least upgrade to Rails 4.0 but lack of time is currently the blocker.

Cheers

Oh! I didn't know the ensl.org code was already open source. Cool! :D

semi says

With the amount of time that can span between gathers filling we are running into a huge problem with users being away, closing the tab, or forgetting about the gather and AFK'ing without leaving. I have a few suggestions that could make the system more robust. Some of these may be more difficult to implement and be less beneficial.

1. Remove a user if they close the tab, use an `onbeforeunload` event to alert the user that this will happen
2. Highlight users that have been inactive (show as a lighter gray color) so we know they might be AFK
3. Alert AFK users and if they don't respond remove from gather
4. Use a steam bot to notify users in Steam when a gather is filled / they've been picked as captains

I will honestly help implement these if the admins agree with these and need someone to do so. I'm a web developer by trade.

Good ideas but

Number 1)
the "remove user if they close tab" is too much
im closeing my browser to play ns2 cause its so resource hungry.
what means i open the gather page in the steam browser.

So can you remove them if they didnt open the page again in like idk 5 minutes instead of instantly.
(some people even restart their pcs cause of various problems)


Number 2)
Not sure how this is going to motivate people to join a gather if they see a lot gray people.
I dont think thats a good idea.

Number4)
I like this Idea a LOT
it helps to prevent number 2 and 3 and that is what you truely want instead of removing people from the gather.


Also we posted about the gather a lot earlier and i gonna highlight my concept again cause i think it might give some inspiration:
www.ensl.org/topics/1165#post_14762

so far good job and thanks for going it on.