From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4100 invoked by alias); 18 Nov 2003 12:36:35 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 4080 invoked from network); 18 Nov 2003 12:36:35 -0000 Received: from unknown (HELO outbound28-2.lax.untd.com) (64.136.28.160) by sources.redhat.com with SMTP; 18 Nov 2003 12:36:35 -0000 Received: (qmail 12334 invoked from network); 18 Nov 2003 12:36:31 -0000 Received: from 66-52-252-3.sttl.dial.netzero.com (HELO vangogh) (66.52.252.3) by smtp04.lax.untd.com with SMTP; 18 Nov 2003 12:36:31 -0000 From: "Brandon J. Van Every" To: "xconq" Subject: RE: One Hex Combat Resolution API Date: Tue, 18 Nov 2003 12:53:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <001a01c3adc9$6e130d80$6401a8c0@Win2k> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-SW-Source: 2003/txt/msg00760.txt.bz2 From: Erik Jessen [mailto:ejessen@adelphia.net] > > I don't know what Tags and Values are in Python; it sounds > like fields & values in database tools I've used. I don't mean it as some Python term. I mean it as a bonehead "any old programming language" term. With the important provisio that order is not important. Python would be able to work with such constructs natively. > Rather than pass lots of parameters to the BE, I'd think I'd pass > - a list of involved units In my terms, a list of Unit Definitions. > - type of action taking place In my terms, a list of Environment Definitions. > The BE should be able to collect all the data it needs from the units > (location, status, etc.); from units locations, it could determine > weather conditions, range, etc. Ranged combat is beyond the scope of what I imagined for a BE. I imagine a BE as simply a one hex combat system, with something occupying a hex and something else trying to enter the hex. Ranged combat would be implemented by a projectile entering a hex, with some Environmental Definitions stated for line of sight, range from target source, intervening obstructions, or whatever. I don't think BEs should be in the business of complicated map traversals. I think they should be in the business of processing fairly simple, closed form results. That way, game designers can easily change them without scratching their heads too much. "One Hex Combat Resolution" is a more accurate term for what I have in mind, so that's the term I'll use from now on. OHCR. Cheers, www.indiegamedesign.com Brandon Van Every Seattle, WA Taking risk where others will not.