Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Agreed. I've developed a game like this before ... years ago using C... which had it's own design issues (such as linking multiple peoples code together). Using perl, however, this might be relatively easy. You could have each person package their robot into, well, a package. Then have the main driving script load each one and execute them each turn.

I would suggest writing some modules for the basic functions: Moving, Scanning, Firing, Status. Each bot may ONLY include these modules, nothing else (if you want a feature that another package has, you must write it yourself and include it directly into your bot).

This sounds quite neat. I played Crobots for quite a long time and would LOVE to see something similiar in Perl.

But like with all games, you are going to have to allow enough variations that people stay interested. You might have the choice to include one type of "Firing" module over another. Or perhaps a "Moving::Hover" instead of "Moving::Treads". They both would have their advantages and disadvantages.

The different types of armor, weapons and movements should probably be categorized by a point value. Then each bot may include upto X number of points in accessories (kinda like weight restrictions in Mechwarrior).

Something to think about!

In reply to Re: Re: Perl Game, suggestions. by mr.nick
in thread Perl Tanks by SilverB1rd

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (2)
As of 2022-05-21 07:26 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (76 votes). Check out past polls.