 December 27, 2007 - 5:15pm | Add some pre-configured packages (program selections), and have a base set of robot, with what at a quick glance appears to be pretty straight forward rules for modding. Although after looking at SF:KH Warship design, most anything seems simple.... ;-) |
 December 27, 2007 - 6:06pm | I like the idea of pre-defined. Makes it simple to add 'em to the game. |
 December 29, 2007 - 7:01am | The list is rather "complete"...I basically took the ADE bots and converted them into something simpler for B+ I haven't decided how many I'll retain, this is still in prototype stage. Most likely I'll revert back to the initial four I had belted out: Guardian (security), Provider (service), Sentry (combat), and Worker (maintenance) and rehash the programs list accordingly. Brains, Warbots, and Heavy Duty bots might be a bit complex for Basic games (and I intentionally left Cybots out for that very reason), and at the same time I doubt anyone in Basic will aspire to having farmer robots LOL. In a nutshell, the final robots list will be robot type, and available programs that define what they can do. No mission statements, no function definitions, etc...just a simple "it can do this and that upon command" type of deal. The # of programs restriction ensures that there won't be ultimate multi-taskers, like maintenance robots that can double as search and destroy units. That's not to say a maintenance bot can't be converted over to combat duty, but in so doing it will lose its primary maintenance bot programming to accomodate such features. Add to that, you'll notice the max STR/STA and DEX/RS ratings...makes them less than ideal for such duties in the first place. |
December 29, 2007 - 2:25pm | Maybe you can make the primary robots reflect the PSA's. For instance, I don't think it necessary to have both a guardian and a combat robot, as they are serving essentially the same purpose: fighting. So to compare to the PSA's, let's see what pops up: Military - Combat/Security Robot Technological - Mechanics/Maintenance Service Robot Biosocial - Medical and/or Environmental all-terrain Service Robot |
December 29, 2007 - 3:59pm | That's a thought...PSA applicable to the robots. I like it. however the Guardian and Security bots serve opposite ends of the spectrum. The Guardian is posted to stand watch over/defend an area (hence the need to be capable of absorbing more damage) while the Sentry is more for an offensive situation (hence the greater DEX score maximums to enable better ranged weapon combat). |
 January 4, 2008 - 3:45pm | Same general role, but different ways of handling it. If you are talking a robot that stands in a single position without moving, you are basically creating a turret. Your Guardian becomes a stationary weapon emplacement with a target/ID input. The difference would be at a program level (if there were to be two 'styles'), same body type but the "Guardian" has only target, ID and defend type programs where the Security has target, ID, defend, attack and evade type programs. The PSA parallel seems to be a good method for creating the basics, after all what is a robot for? Replacement of a person in a dangerous, tedious or expensive job. It follows that they have the same skill/requirement that we do. If not in favour of just a programming diference, you could divide them by making a heavy duty version of a body. This would also work for the biosocial variety where the standard body is the nurse/light duty type and the heavy body is the planetary rover. Heavy duty is more robust but less articulate to give a check/balance system for why they aren't all heavy duty do-it-all robots. "I reject your reality and substitute my own."
|
