Air units won’t be quite as threatening as they were in Starcraft, where Mutalisks could singlehandedly win a game by killing all of your gatherers. This game will have no gatherers, so the main advantage air units will have is mobility.  Maps will have cliffs spread around the map, making the advantage come down to something more than unit speed.

Notice that, when you have no gatherers, map control becomes irrelevant, as you can just mass units and push out, without worrying about getting another source of minerals.

Instead of resources, I will introduce “production towers,” which are some sort of magicky-looking towers, spread across the map much like an expansion would be. You start with one sitting right next to your crawler, already aligned to you. For each tower aligned to you, you get a slight boost to production. How this boost will work is up in the air. It could be a flat reduction to build time, like -5 seconds production time to everything (anything taking less time to build than the towers would reduce just build instantly), or it could be fractional, or logarithmic (diminishing returns).

The towers start as neutrally-aligned. In order to convert one to you, you must bring your crawler, or units totaling 15 x (how many towers you have + 1) supply to the tower (within a certain capture radius), so if you’re going after your second tower, you need to bring 30 supply’s worth units with you. Regardless of how many towers you have, the crawler will completely fulfill the requirements. Then, you must have all those units sit there (they can fight) for 2*(number of previously owned towers) minutes, as a timer ticks down. This timer will not tick down any faster if you have many units near the tower. Your opponents also won’t be notified unless they actually have vision of the tower, in which case they can see the timer on the tower. If you have units near a tower while it’s building, but not enough to fulfill the requirements, the timer will freeze where it is. If you remove all units from the tower, the timer ticks backward at twice the rate it went up. Once the timer completes, the tower becomes erect and gets a set amount of HP. Note that, each of these quantities (2 minutes per tower, 15 supply, etc) is up for changing during testing.

As a side note, any timers you have running will show up at the top of your screen, in your color, and display its status. If you’ve scouted an opponent’s tower, his timer will appear just below where yours would appear, except running in the opposite direction (if your timer is a bar filling from left to right, your opponent’s appears as a bar filling from right to left), in his color. Clicking any of the timers will bring the screen to center on the tower.

You can contest your opponent’s towers, too. It is possible to have timers for two or more factions running at once. Say one player holds a tower until it is nearly done, but then leaves. An opponent can come in and start occupying that tower, starting his own timer. If something like this happens, you and your opponent’s timers both appear. If both you and your opponent have units in the vicinity of the tower, both of your timers stay frozen, regardless of who has more units. If you abandon a tower while both you and your opponent have timers running, your opponent will have his timer progress normally while yours will drain at 3-4x the rate instead of 2x, as if it were simply abandoned. Additionally, as long as you have any timer running on a tower, you will be granted full vision within the capture radius of the tower. If your opponent decides to station long-range units just outside of the capture radius, you’ll be in for a rude surprise.

Once a tower is erected, it becomes more vulnerable. You can abandon it completely without losing the benefits or worrying about a timer. However, it can be attacked. To capture the tower from your opponent, you must first destroy the tower by depleting its HP, then force out all opposing units to start your timer. You can also simply pull out and force your opponent to recapture it. The viability of such a tactic will depend on how much the tower was reducing build times.

Though winning the game officially requires that you destroy all your opponent’s units, removing the opponent’s towers can be enough to force him to give up.

Also mentioned in the previous post, an RTS with mobile bases would be difficult to balance. For me to explain why, I have to explain proxies.

Keep in mind that, unless otherwise noted, I’ll be discussing Starcraft: Brood War for most of my examples.
It’s an RTS with simple rules but incredible depth, and it’s the one I’m most familiar with. While games like Dawn of War have extra mechanics like cover, I plan to model my RTS after Starcraft, to a degree, because the simplicity of Starcraft’s rules has also led to that much more creativity. If you really feel unfamiliar with Starcraft, or want to find more information than the bare minimum I’m putting here, visit the Teamliquid Starcraft Wiki.

In Starcraft, you’re “expected” to place your tech buildings and your production buildings inside your base. That’s the safest place for them, and it consolidates all your stuff in one area so that whatever unit you’re using to build them won’t have to run too far out (unless you’re zerg, in which case your builder morphs into the building), and it lets you focus on one area of the map whenever you want to crank out another round of units.

The text below the page break is an enormous aside about proxies. If you want to read it really badly, click ‘more.’

Anyway, back to the main point. If you think a bunker rush is scary, imagine this. Your crawler is a colossal mobile unit with a passable attack. The current mechanic for it has it able to move, attack, and produce units at the same time. (This was not the mechanic used in C&C 4, though. There, your crawler would have to unfold into an immobile building with no attack while it pumped units.) So, you pick the faction with the units that are the fastest to produce. As you’ll see in my later posts about the available factions, this will be modeled heavily after the Starcraft Zerg. To avoid lawsuits, (Hah!) I’ll call this the Swarm. So you take your Swarm Crawler and march it toward the middle of the map, producing units all the way. As your units pop out, you send them to every part of the map to scout your opponent, who is likely teching to the next available unit (the poor sap, he’ll never see it coming!). By the time your hulking crawler makes its way to the enemy crawler, you’ll have a small but scary force of Swarm units, while your opponent has not made the best use of his production time. Your units outnumber your opponent’s, so your crawler’s HP will have a slight lead over that of your opponent’s crawler. Eventually, after a battle of attrition your crawler comes out on top. Your opponent’s only defense is to do exactly what you are doing, and that makes for a boring game.

I’ll admit, C&C 4 did a good job of preventing this sort of cheese. Since you have to turn your crawler into a building to create anything, this kind of rush is just out of the question. If your opponent tries to rush, you turn your own crawler back into its unit form to give your army the upper hand. However, this honestly feels a bit stiff to me. I want a crawler that can reinforce on-the-fly. If the crawler can move, but not attack, then you’ll run into problems when your units are produced piecemeal and lack the crawler’s support.

My favored solution is to have the crawler able to attack, but not move - or move really slowly - while it produces units, and be completely helpless when researching tech. This would force the attrition rush to be made with an inferior force, while the opponent would be able to flee if you insisted on parking your crawler nearby.

Rushing is still an option. If you gain an understanding of the timings of the game, such as when a certain unit is slated to appear, you can in theory create a large force and attack your opponent while he’s halfway through researching some powerful tech, forcing him to cancel his research to defend his crawler and delay his tech. Since time is the only resource in this game, it could be a major setback. The crawler’s function will have to be determined through extensive testing, but for now, this seems to be the option that can provide the most tactical possibilities.

PAGE BREAK WAS HERE

But sometimes, people will stick their tech or production somewhere else. This is generally only an option early game, and it’s often a form of cheese: an attempt to end the game early by catching the opponent off guard, since you’ll be at a disadvantage if the attack fails. I mentioned hiding tech earlier. Zerg can’t really hide tech that well since they only have one place to stick their buildings early game. Protoss and Terran can hide buildings, but they generally go about it differently.

The Protoss has two options to hide tech: the robotics tech tree, and the Ttemplar tech tree. With the Templar tech tree, you keep your gateways (production facility) and cybernetics core (basic tech) in your base, but you send out a single probe (worker unit) to some odd corner of the map, sometimes behind the mineral lines of an uncommonly-used expansion, and throw down a pylon, Citadel of Adun, and the only building you’re actually gunning for, the Templar Archives. Once that finishes, you pray you don’t get spotted and build Dark Templar-devastating units that can’t be attacked unless your opponent sees them with other special units. Then you use your invisible psionic alien ninjas to go kill everything in your opponent’s base, while there’s nothing he can do about it. If you get scouted and you can’t do enough damage, you’re pretty much doomed since you cut back on probes so you could get DT’s out faster.

So this would probably be a horrible time to discuss any other RTS. Which is why I’m doing exactly that.

The one I have in mind is Command and Conquer 4. I heard about it from a friend, who is a big fan of the C&C series but hated that game on sight. His biggest gripe with it was its MMO-like format. As you play online, you gain experience points, which you spend on an upgrade tree of sorts. He knew he hated it just for the MMO part. When I found out more recently that C&C 4 did away with resource gathering (Tiberium can now either be used as a bomb or redeemed for upgrade points), and that your main base, a mobile crawler, respawns if killed. From what I gleaned off the Wikipedia article, the win condition isn’t army annihilation, but keeping control of a number of control nodes.

While I agree with my friend that combining an MMO (Massively Multiplayer Online) with an RTS (Real Time Strategy) isn’t a good idea, and I agree with other people that respawning in an RTS just feels wrong, I think the idea of a mobile headquarters has promise.

When compared to a traditional RTS, a mobile base would bring drastically different gameplay. I’ll be using Starcraft: Brood War as a basis for comparison. A mobile base would do away with resource gathering by necessity of map design; having resource deposits everywhere would clog the map. You’ll only have one base, so there would be no point in moving it to a new location until your current resources run out.

A mobile base RTS would bring more focus on scouting, map control, and army composition. In Starcraft, once you locate an opponent’s main base, you could generally keep tabs on them by hovering an observer (cloaked scouting unit) over his base or using a comsat (radar) scan every once in a while. Of course, there are some exceptions. You’ll have to keep tabs on where your opponent is expanding by periodically running a fast unit around the map. A Protoss or Terran player can hide a tech building in some corner of the map, hoping to catch the opponent by surprise. A Zerg can put a building at a less-defended expansion, where it serves a dual purpose of hiding the tech and possibly clogging an entrance into the base.

In contrast, against a mobile base, you can’t get complacent about your scouting. After you’ve seen the opponent’s base, he can pack up and travel across the map, and you’ll be left in the dark if you just go back to the same spot.

Balance will be difficult, but that’s something that playtesters or developers can work out.
I plan to make some sort of RTS like this as a summer project, or at least once I’m done with college apps. For now, I’ll be coming on to post more concrete ideas I’ve had that I’ll probably wind up implementing.

Anyways, here’s what we’ve got this time:

A wonderful powerpoint made by me detailing the work I’ve done this summer! Enjoy!

Slides for SIMR

William

Oh, how true it is.

For a few hours today and the better part of last night, I’ve been working on a program to calculate a line of best fit. It was a code exercise that took much longer than it had any right to.

It’s not that the code itself was difficult. I use Visual Studio for my C# code, so I got the window and controls set up fast. The line of best fit can also be calculated analytically. Just find the formula for the least-squares error, take the partial derivatives of A and B, and solve the system of equations. My code worked perfectly fine for solving the problem and spitting out A (the slope) and B (the y-intercept).

The problems came up when I tried graphing stuff. First, I found out that the computer counts pixels from the top left, while I want the origin at the bottom left. But when I reflected the drawing vertically about the y-axis (the transformation was NEW Y = HEIGHT OF WINDOW - OLD Y), all the points disappeared. I had the help of my dad, and we spent about two hours staring at the code and getting nowhere.

Here’s the breakdown of what I did with that chunk of code today:

5 minutes: Figuring out that HEIGHT OF WINDOW should have been HEIGHT OF THE PANEL WHERE THE GRAPH IS ACTUALLY DRAWN, WHICH IS LIKE HALF THE SIZE OF THE ENORMOUS WINDOW ITSELF. Now there’s your problem!

5 minutes: Suddenly realizing the old code only showed a fifth of the data points and that now I’ve got 100 more to deal with.

20 minutes: Wondering why the edge of the graph kept getting cut off and changing the size of the points on the graph to see why. Turns out that the data just happens to have a lot of points congregated to the right.

10 minutes: Wrestling with syntax and about a dozen sets of parentheses to draw a y-axis.

10 minutes: Figuring out a way to expand the boundaries of the data set without having to worry about signs.

10 minutes: Wondering why my attempt to draw the least-squares regression line doesn’t show up on the window.

2 minutes: Adding 0,0 to the data set to force it to be included in the graph, then seeing the outlier skews the line way off.

3 minutes: Removing 0,0 and changing the graph range manually. Oh, looks like the outlier didn’t do much for the data anyway, and the line is off entirely.

15 minutes: Trying various fixes before noticing that it’d be best to remove the flip-by-y before making changes, since the flip complicates things.

5 minutes: Rewriting the line of code that draws the graph and remaking the arguments for the function from scratch. No dice.

20 minutes: Various remedies, all of which fail miserably, before sitting down to think and realizing that expanding the graphing range messes with the scale, so I need to add a few correction terms in to shift the line back.

5 minutes: Code-wrangling, which finally gives a line that works.

5 minutes: Drawing an X-axis.

Total time elapsed: 1 hour 45 minutes on a really short piece of code, plus the 2 hours from last night, plus the half an hour I used to write up this article.

Man, where’s the Ballmer peak when you need it?

-PKTT

In a school chapel meeting, I was awarded the Xerox award for innovation in science, which recognizes a student who uses innovative technology to reach students with information about science. I don’t have the letter close at hand, so the description is probably a little off.

Part of the description of innovative technology included blogs, so I suspect that one of our school’s teachers or administrators has been here. I suddenly think I should go back and edit profanity out of all our articles and replace them with substitutes such as loving caress.

-PKTT

This has been around for a while, and the event ends in just a few days, but here it is.

http://www.wolfire.com/humble

The humble bundle. Some of the best independent games around, being offered for any (positive) price, from a cent to a thousand dollars. Pay whatever you want, and you’ll get the download link instantly.

Try it out. It’s the ultimate in instant gratification.

-PKTT

http://www.tryengineering.org/play.php

Nifty extending, collapsible pens from Google- I didn’t get one, since they’d run out by the time I got around to asking for one. Basically, hitting a button on the pen makes the two halves of its cover fold up like gull-wings and turn the thing into a pen-shape.

Rubik’s Cube Keychains from Google - I suck at Rubik’s cubes, so I didn’t get one. After Google started running low on pens, they made people solve these first before giving them pens. It worked.

Team Buttons: We all got a crapload of these. Teams with a bit of money to spare would have them made and passed out. Our team made do with finger traps from a local store. Some teams handed out stickers (both practical, like a battery disposal reminder, and just for show) or fridge magnets. I got a mousepad from one team, with their logo and number on it. It’s one of those hard-cover mousepads, so I’m holding off on using it.

Demonic Ducks: These are rubber ducks of various colors, and with horns, that one team was handing out for “adoption” to keep teams from all over in contact. I got an orange one. His name is Super Sayan(sic) and he is a ninja.

A rat finger puppet: The rat’s fur is kind of dirty-looking.

Various teams also gave certificates that said “Thanks for being on our alliance” or the like. Our team got a framed certificate from 1572 or something like that. The demonic duck team was handing out tiny models of the playing field with ducks hanging from the towers.

Well, I’ve been gone recently, and I blame FIRST Robotics. Our school formed a team for the FRC, which is the main competition, for high school and with the largest robots. It’s not a battlebots-like competition, since FIRST encourages sportsmanship and all that good stuff. They have a new game designed every year, and this year’s was basically soccer, with a goal at each corner of the field, foot-high, trapezoidal speed bumps, and two towers with crawl space and ball return chutes. The idea was to score goals. Balls would be returned rolling off the towers. Extra points for hanging off the top or sides of the towers at the end of the game.

We started the team in mid-May of last year, and the fundraising and planning started at the same time. We ran into problems, since NASA’s rookie grant went to Valley Christian of San Jose instead. We ended up getting a one-week extension to pay the whopping $6,000 registration cost, $5,000 of which came from a surprise grant from Google, and the rest of which came through fundraising and donations. As a note for now, we also fundraised for the money that actually went into building the robot. We also got another $1,500 from Dale’s Hardware, where our school goes for its maintenance supplies, provided we name our robot “Dale” and give two demonstrations of the robot at the store sometime this school year.

We started off designing the robot in Solidworks. Though we admittedly spent a bit too much time on the design and not enough on actually experimenting on our robot, computer design did give a lot of help on knowing where to position things and how to size them.

Part of why we spent so much time on design was because we sent our computer design to our co-captain’s dad, for him to machine out. He had to ad-hoc part of the design, which made it get back late. In the meantime, the team put together the default kit that FIRST gave us. I wrestled with the code a bit and got it running. I proudly deemed this “the first thing I made that could kill people.” This got the response of “I like how you said first.”

Later, the team had put together the robot we were planning to use, and ran into spacing problems. This resulted in some stupidity involving plastic boards and a whole bunch of mis-sizing. After we (someone else got stuck with that job) ground down the excess plastic since the safety bumpers for the robot had to be flush with the robot’s body.

Either way, after some more code fiddling and sifting through documentation, I got pneumatics working. That is, the pneumatics control device (a solenoid if you actually know what it’s called) worked. Turns out the device that actually controlled the pistons had a dead valve. One of our mentors gave us a new one. Our robot could now stab people in the shins.

Fast forward a few weeks, and I’m pulling an all-nighter to get all the code in, so that the robot will be able to use all the features we put in just that night, like the ball kicker itself. When morning rolled around we found out the kicker wasn’t working, but we basically said “screw it” and shipped off the robot.

Silicon Valley Regional:
We unpack the robot and spend all of the first day from about 8am to 8pm trying to fix parts of the robot, edit code, etc. We ended up missing two of the matches the next day due to some outdated software and other issues, since we couldn’t pass inspection and get on the field without that stuff. We basically panicked the whole day as we frantically tried to fix the kicker and add a ball guard. Our robot also got flipped over about every other match. We placed around 35 out of 50, and won Rookie Inspiration, which is the “Little engine that could” award. We could make a robot, but couldn’t win anything better. Rookie All-Star went to some 4-H sponsored team, when it should’ve gone to Valley Christian. Seriously, one of the 4-H team’s robot features was listed as “coded entirely in C++.”

No crap, Sherlock. Have you ever tried to code anything in two languages at once? It’s impossible. The team’s robot and presentation were both shoddy and unimpressive. It’s all good, though; Valley Christian won Rookie All-Star at the next regional they went to.

We set our sights on Rookie All-Star again at:

The Las Vegas Regional:
First, I now hate Las Vegas, for sure. We panicked less, and finally got that ball guard/roller working, so we could hold the ball in place. We nixed the kicker and added 2 more motors to the drive train. It went better than at Silicon Valley, but we still missed an early match due to problems at inspection. I also had some coding issues with the drive train that I worked out eventually, and we found out our robot was ridiculously stable. Even with a faulty drive train, it could run over a bump.

The biggest problem we had was that, during our second or third match, our CRIO (essentially the CPU of the robot) broke for no good reason. It had never broken in Silicon Valley, and we had run the robot tethered in our construction area literally minutes ago. One reason the field crew suggested was the metal dust near it, which hadn’t caused any problems before and which we had never bothered to get rid of. It was aluminum dust from some grinding done to the chassis. Did I mention aluminum does not conduct well?

Either a tiny piece of dust suddenly and inexplicably got into the CRIO, or the field crew messed something up, since they mentioned we were the fourth team to have a busted CRIO that day. The team captain is looking into it and filing a claim.

We placed 41 or so out of 47 and won Rookie Inspiration, again. The team that won All-Star actually deserved it this time, though. They got a double ticket to the national event. They also ended up on the winning three-team alliance that gets sent to the national event in Atlanta, Georgia. All I can say is: Good luck with 971 (Last year’s national champions). They beasted all over everyone at Silicon Valley, and they’ll probably do the same at nationals.

All’s well that ends well, I guess. Our robot and a bunch of loose tools are probably at the school by now, and we’ll crack the crate open and dust off Dale. Only problem is, Dale’s hardware still hasn’t given us that $1,500 (the understanding was that they give us the money, and we just have to give demonstrations some time or another). We also need a new $500 CRIO (we’re looking into that), and we still have to give those demonstrations. Either way, it was a fun year, and I’m hoping we get to have a robotics team next year.

That being said, our school and students have no good mentors, so we’re pretty much a purely student-run team, so we have no chance in the competition. Our school could pay for extra mentors, but we’re already a little tight on money, so that may not be the best idea. Whatever happens, I’ll end up leading something, be it a robotics club or a MathCounts team. Here’s to next year.