From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32611 invoked by alias); 3 Nov 2003 21:21: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 32604 invoked from network); 3 Nov 2003 21:21:34 -0000 Received: from unknown (HELO garm.central.cmich.local) (141.209.15.48) by sources.redhat.com with SMTP; 3 Nov 2003 21:21:34 -0000 Received: from leon.phy.cmich.edu ([141.209.165.20]) by egate1.central.cmich.local with Microsoft SMTPSVC(5.0.2195.6713); Mon, 3 Nov 2003 16:21:33 -0500 Received: from localhost (unknown [127.0.0.1]) by leon.phy.cmich.edu (Postfix) with ESMTP id 8F0CD70017; Mon, 3 Nov 2003 16:21:27 -0500 (EST) Date: Mon, 03 Nov 2003 21:42:00 -0000 From: Eric McDonald To: Jim Kingdon Cc: xconq7@sources.redhat.com Subject: [OFFTOPIC?] Doc Chow (was Re: Windows Installer for Xconq) In-Reply-To: <200311032014.hA3KEHu25869@panix5.panix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 03 Nov 2003 21:21:33.0090 (UTC) FILETIME=[746D2820:01C3A250] X-SW-Source: 2003/txt/msg00567.txt.bz2 On Mon, 3 Nov 2003, Jim Kingdon wrote: > I guess that makes sense. Imfapp is half a mebibyte on my linux > system, and full sources seem to be about 5 mebibytes or so. Having I think I can get used to saying "mebibyte", but "kibibytes" really sounds like a brand of dog chow. Thankfully, a half a kibibyte (aka, binary kilobyte) is not known as a "kibble", in the way that half a byte is known as a "nibble". Otherwise, we would have all these Kibbles and Bits floating around. > the xconq sources are kind of useful in understanding how the game > works until/unless we get more documentation volunteers than we have > now. Yes. Absolutely agreed. If my motivation capacitor ever becomes sufficiently recharged (wrt documentation), I intend to mention the formulae used by each of the combat models for determining hits and misses and damage. Another good thing that could be done, imo, is using @ifhtml in the .texi sources, so that newer texi2html translators can include raw HTML (useful for including screenshots in the HTML versions of the docs). I still need to write up some things regarding compound terrain effects, but have been holding back because I think I should refine that code further to deal with my previously mentioned ideas about border and connector aux terains. > I'd call the options something like "Normal" (everything you need to > play xconq), "Designer" (includes files recommended for game > designers), and "Source" (includes xconq source code, for those > desiring maximum insight into xconq's functioning). I'll consider what you suggest. It's a dog's world, Eric