Your friend Marcus lost his connection with only one roll of the dice remaining before he was about to lose the match. You draw your own conclusions.
Either way, they should not be allowed to negatively impact my reputation, or to cause me to get threatening messages from Miss Manners about loosing my playing privileges. Wow, talk about making a new guy feel welcome!
If you are sincerely seeking someone to help you administer your system, send me the source code for the software and I'll take a look at it. I am retired now but I have over 40 years of software development experience in a verity of programming languages. the suggestions I made seem reasonable, feasible, and appropriate based on what I know about how computer systems work.
Thank you for the offer,
It is simply not possible to draw ANY conclusions about an unfinished match, until you have invited the player to resume play with you and they have refused. It must be on a different occasion to the first drop, because if the person had their internet connection disrupted, they will appear to still be logged into fibs and ignoring you...but they are not there, fibs just doesn't know it because the correct logging out protocols were not followed.
My one and only absolute conclusion I can draw from 8 years of playing on fibs, is that the internet does not stop to check if you are one roll away from losing, one roll away from winning, in the middle of a match or simply sitting there shouting rubbish when it goes off. You think it is hard to get a player who dropped you on the last roll to resume - you try it with a player YOU dropped as you were one roll away from winning - they will think...serves you right pal and you wont be seeing me for a few weeks!
It really is as well to know these things before deciding on a suitable 'policy' to deal with disconnections.
Another classic thing that happens is that the player who has lost and is on the last move will send a move, or a resign and assume the match has finished...but it wont until both players complete the protocols for match finishing [done by the interfaces], if he simply logs off, the match is considered saved. Again, asking them to resume often surprises them, as they had no idea the game wasn't finished.
The prevention of new players racking up 100's of saved games is a good one - you are only allowed 7 or so right now, because you have low experience, but fibs will get more tolerant of you as you build up experience.
Of course, by then, you will know how to avoid and deal with droppers...and wont be getting so many
As to your offer of help, fibs is not open source, and is not randomly tinkered with - only essential updates are made.
Useful things you could do to show intent would be to help us resolve the 'interface' issue...go to sourceforge and pick up a half finished project, or write an interface from scratch, that tells the newbies all they need to know to stop them racking up saved games and guides them painlessly through the process....
Javafibs is the closest we have to the perfect interface - but there are hundreds of things can be done with it to make it a lot easier for newbies...but the original coder isn't prepared to make it open source. So take a look at that, and all the improvement suggestions in the javafibs thread [from users with lots of experience of what would really be useful] and get cracking.
Helping put together the perfect interface would improve things dramatically right now - and who knows, may give people the confidence in you to do more useful things back at the base
If all of that does not suit - try here...http://www.melbg.net/server.htm
these people are trying to do all you suggest from scratch - and could really use some help.
I hope that can be considered at least a little helpful
If you need more to cope with the problems which exist on fibs, that we have all had to learn to live with...ask when you see me there..