First I should say that my beloved Car Wars implementation feels a bit irrelevant, now. :-) I did most of it and started making a real lib out of this instead. This is a hobby that I lost control over and took time off to finish.

computer game called AutoDuel, which was based on the same ruleset.
I haven't seen it, but... did that game really implement the whole rule set??

All exceptions and links between weapons, different loads in one magazine, variants of turrets like external weapon pods/rocket platforms/sponsons, different kinds of rockets and laser links, component armor etc, etc?? It implemented a real time game, so why should it?

(Update: I missed the text "it wasn't able to match the complexity of the full ruleset" about AutoDuel. Totally missed the argument.)

given the success of the AD&D computer gaming market, I cannot imagine that the current Car Wars ruleset would be that difficult to model.

It hasn't been done, as far as I know. And there were lots of computer people that loved it.

You have lots and lots of exceptions, etc. If you start implementing away, it will become really, really ugly. I started this as a hobby when I got the idea to model the cars as hierarchic structures and make them OO, so I could override behaviour everywhere. Then it becomes quite neat!

Also, the finished object tree would be relatively easy to extend so you can have "behaviours" like possible moves, taking damage and when it is legal to shoot (and hit). Ergo, something that could play the game, too.

(-: That said, I was at the Nordic Perl Workshop this weekend. I got a feeling there were a dozen people in the room that could throw something together over a weekend. :-)

Ruleset modeling has a ton of real-world uses.

There should be real world uses to make things easily that is very hard otherwise, but I have no idea which.

If I knew who it would be worth money to, I would probably have sold it because I really could use the money or a high paying job. :-)

(-: So, if you think up a good use, send a suggestion for enough money that I will go back on promising to publish it. It better be much, since I'd have to change name and move a long way. :-)

N B The previous paragraph was a joke. (-: I think. :-)

In reply to Re^4: RFC hierarchic modelling documentation by BerntB
in thread RFC hierarchic modelling documentation by BerntB

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.