Jump to content
Sign in to follow this  
SkrapssparkS

[PMC] /check-all

Recommended Posts

Would it be possible to have a command to check all modreqs on all our servers from any of our servers, much like how /list-all works? If possible do you see any major downside to trying it out?

  • Upvote 2

Share this post


Link to post
Share on other sites

If we shifted modreq to all point to one central database and added a column for server then this would be a lot more possible without risking any added lag.

  • Upvote 2

Share this post


Link to post
Share on other sites

/list-all was taken down due to lag ;)

But yeah this would be cool. I don't mind doing reqs on s or c but I don't normally play those servers so it's usually only when someone comes to p for an SOS.

Even something like /check c or /check s would be neat. Depending on which method is less buggy id love it.

Share this post


Link to post
Share on other sites

Idea: Not sure how do-able this is but it's an idea. When joining the server instead of being told there are open modreqs and to use /check to look at them, it should say something like "There are 5 P, 4 S, 15 C Modreqs open."

Share this post


Link to post
Share on other sites

It would be possible.  I would take a fairly fundamental change to ModReq though, but it could be done.

Share this post


Link to post
Share on other sites

It would be possible.  I would take a fairly fundamental change to ModReq though, but it could be done.

 

I've been toying with the idea of updating modreq to have clickable chat commands for claiming / viewing modreqs. If during this process we switched it to mysql and added a column for originating_server is there much else we need to consider?

 

This may well be one of my lazy sunday scotch and programming adventures, so I'm keen to work out the details ahead of time.

  • Upvote 2

Share this post


Link to post
Share on other sites

I've been toying with the idea of updating modreq to have clickable chat commands for claiming / viewing modreqs. If during this process we switched it to mysql and added a column for originating_server is there much else we need to consider?

 

This may well be one of my lazy sunday scotch and programming adventures, so I'm keen to work out the details ahead of time.

 

I was just thinking about trying to keep it still usable by other servers that don't have the multi server environments, etc.  I don't know if other people still use it, but it used to be used by others.

Share this post


Link to post
Share on other sites

I was just thinking about trying to keep it still usable by other servers that don't have the multi server environments, etc.  I don't know if other people still use it, but it used to be used by others.

 

Judging from the traffic graphs we are not alone in using it. However that shouldn't stop us from making changes to better fit our community. The option of using mysql or sqlite ( config option ) would solve one of the major problems some people could take with us moving to mysql. The addition of a server column wouldn't require a meaningful change for single servers, they would simply not use whatever command flag we set to show all server requests.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...