NationStates Jolt Archive


Problems banning in chicago

Serval Cat
04-02-2009, 19:52
Somethings not right with the regional controls in Chicago.
I try to ban Charity Hospital and it says this:

"Influence Cost Estimate

Either Ejecting or Ejecting & Banning Charity Hospital from the region would consume an insignificant amount of your influence. "

So I push eject/ban and get this:
"You don't have enough regional influence to do that."

Charity Hospital shows up on the ban list until I close and re-open the regional controls....then hes no longer on the ban list again! Help please.
Frisbeeteria
04-02-2009, 19:58
Gameplay problems should be reported via Getting Help ... which you did. The same people look at both lists, so duplicating your request here is unnecessary and redundant. Only game mods can fix this, and only game mods check Getting Help. It's the direct route.

That said, I don't know what the issue is. "Charity Hospital" appeared to be outside the region, so perhaps that aspect of the ban code wasn't seeing him or something. I've added that nation to the ban list, so your immediate problem should be solved.



Seriously, you needed to post this here, on your RMB, and in Getting Help? Both you and the other guy have tons of puppets, so it's not like either of you can effectively shut out the other. Must be one of those Gameplay things we mods just don't understand.
Serval Cat
04-02-2009, 20:28
Thank you for your help,I apologize for duplicate postings but I wasn't sure if my requests were getting through to who they needed to get to. And yes its a rivalry/gameplay thing you'd only understand if you played the way we do.
Like when update time comes and your getting invaded and can't ban anyone because the games glitching out...thats not fun.
Maybe a simple telegram saying the problem you lodged a request about 8 hours ago is being looked at would have prevented this. I'm sure theres even a way to automate the message when the request for help is received.
Frisbeeteria
05-02-2009, 03:04
Maybe a simple telegram saying the problem you lodged a request about 8 hours ago is being looked at would have prevented this. I'm sure theres even a way to automate the message when the request for help is received.

Sounds like a solution in search of a problem. I can remember maybe 5 similar incidents in the past 4 years ... and we've processed about 300,000 tasks in that time.