Yes, but optionally. If you use realtime extern, then yes, I would include that. Anything that's done once at extern would be a candidate for being managed in realtime so that it's truly enforced. Plus, you could have radiation clearing in realtime, NavHaz dissipating in realtime, etc. Ports could upgrade exactly one day after they started, or Citadels upgrade. You get the idea. Because it's such a big change, it may be a v4 feature rather than v3. But it's something I've always felt needed to be addressed.

Right, that's what I'm thinking. And your last point answers my question about what to do with players joining corps. I don't think that's too big an issue. The player just needs to clean up fig deployments before he's allowed in.

So when you count total fig deployments for a Corp, you're counting both Corp and personal figs for all members of the Corp?

I would say yes.

That's the most clean approach.

I ran my script at different times of the day, normal was every 24 but never at extern. If I read in the logs that someone got caught I would set the timer to every 3 or 4 hours to keep them in line. Once there were no violations I would change back to once every 24. I only had one corp that was constantly over and we found that their script was miscounting, worked with them to fix the issue. Usually it was never more than 5 or so over, but with a threat of losing millions people tend to pay attention since that could be a game changer.

I ran another script that just policed the MSL's and Fed Space since I only allowed 1 Toll fig 4 sectors out from Dock/Fed Space/MSL's/Class 0's. If the fig was Offensive or Defensive even if 1 I had it automatically removed. This allows for people to freely move around and trade without paying toll after toll or being blockaded.


If you have over 500 when the check is done and you lost a gate worth of figs for not being in compliance you wouldn't do it twice. Well I guess maybe someone would.



Yep this is what I was saying in my first post.

Ok, I like that. It keeps them guessing. Of course, right now I only have two options for my version. Either extern or on the fly. If/when I add a realtime extern process, then I could do what you're describing. But for now, I think realtime is better than at extern.

Do you think that the restriction on placing figs in MSLs should be imposed as part of truce rules, part of a fig limit option, or both? I'm starting to see some crossover between truce rules and fig deployment limits.

I like the option of having both, building games are necessarily truce games. Most building games typically have a limited truce (15 or 30 days) then it is basically open season to attack/invade but still with rules set forth to allow players to join and get started.

Seems more like a truce rule to me.

Have you considered allowing (or even forcing) players to convert their personal assets to corporate upon joining a corp? This wouldn't just simplify the fig limit issue. It would also be convenient in other ways. And it would hinder cross-corping.

A single toll fighter should be acceptable for MSL, it is useful for buydowns at class 0 ports and the like.

What if it's an LLC? (snicker)

@V'Ger: It seems like a safe assumption that buydowns are going away...

That is one of the few areas of [almost] universal agreement that are clearly errors in the program, that buydowns are abuse and not a legitimate strategy.

how does one put shields on their planet without the ability to do a buydown?

I'm assuming he means buy outs and not buy downs. It would be ludicrous to think that port buy downs would be considered abuse.

ahh thanks... i should have realised

All this talk about fig restrictions .. a few sysops (myself included) have these script to monitor MSL and adj's for truce ... but what is missing is on the TWGS side .. a way to eliminate limps from sectors.

They will remain even with sweeper scripts.

just a bit of input.