Had a good talk with Gophur about the strat stuff today and pennies dropped for both of us. He moved his first brigade from “off map” and the effect was kind of undesirable. There was a 15 minute delay before it started a 3 hour trickle of supply. That’s not what he had envisaged. He wants much shorter times, but the problem is that any system with shorter supply time that undercut resupply are going to get gamed.
So I proposed that instead of discarding the resupply tickets when a brigade goes out of supply, I keep the resupply queue, but as each ticket came due for processing not deliver any vehicles, leaving a shortfall between absent and scheduled.
When the brigade comes back into supply, I simply schedule tickets for the outstanding shortfall, using the existing timer, and Gophur will probably set that to be like 5-10 minutes initial and maybe 30-90 minutes complete.
That nixes any annoying short-term supply “boost” mechanisms, but lets you get back into play after fair and due time.
The remaining aspect of all this is brigade movement. Frankly, I really can’t see much argument for trickling a brigade between two towns. So option #1 is a simple delay on the availability of equipment at a new town after a brigade moves there. Simple, efficient, clean.
Option #2 would be to divide the equipment up into groups and simply create tickets for these groups. Tickets can specify a number of units so it shouldn’t be too expensive, generating maybe a couple hundred tickets per brigade. Not quite so efficient or simple.
When I re-described the ticket system to Gophur I also showed off an admin command that dumps the top of the resupply queue for a BDE, but incredibly efficiently (it takes 2.03ms on the beta strat host with the current 1.26 supply system, it takes under 3us on the same hardware with 1.27). We both agreed it would be nice to add to the Weapon Select screen some indiciation of when the next supply delivery is scheduled. Since supply rules are much more streamlined now, this should take away a lot of the frustrating black-box confusion about “wtf is our stuff”.
And its mostly because Gophur and Bloo use the browser known as anti-IE. If FF can make it difficult, they will make it difficult. (Aside: I don’t understand people who buy into FF ‘because its not IE’ but still use Outlook. Hello? Thats buying a ticket to Soddom because you’re heard the folks at Gomorrah are a little queer). If I didn’t have to support FF it’d be a lot easier. (Some of the more complex tools display a dialog when viewed in FF: “This page requires a web browser to operate” – they work in Opera)
Got me an issue in the cell host to diagnose where occasionally a null pointer is somehow getting into a list of vehicles I’m about to send updates to, and a problem where periodically people just die. I’ve got the beta server sending chat messages to people when the host kills them, none of which get sent – so either I’m clobbering something … or the client is.
And we’re going to try and squeeze in a change to resupply that might let me provide some score for doing it.