Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You will probably want to do some refactoring, as having a bunch of public functions in a single class and passing around that many parameters doesn't seem like a manageable solution. </p> <p>I would start by creating a <code>ShotPattern</code> base class or interface, with a class extending or implementing it for each type or category of shot pattern. The logic for how and when to fire bullets, and what kind of bullets to fire, would be handled by the <code>ShotPattern</code>. The <code>ShotPattern</code> could also affect the <code>Bullet</code>s after they are fired, to change their direction or speed, or even produce more <code>Bullet</code>s to create a splitting effect.</p> <p>The constructors for <code>ShotPattern</code>s could still take some parameters; the goal is just to reduce the repetition and keep a larger portion of the bullet generation logic internal to the instance. The <code>func</code> parameter in your <code>FireAroundArc</code> function is clever, and the same idea can be used by creating <code>ShotPattern</code>s that require other <code>ShotPattern</code>s as parameters. </p> <p>Each instance of an <code>Enemy</code> should keep track of its <code>ShotPattern</code>s, which in turn keep track of their <code>Bullet</code>s; that would allow clearing bullets fired by certain enemies, and the bullet creation pattern could move with the enemy.</p> <p>In terms of actually designing enemy attack patterns, there's a lot of possibility and it's a very open-ended problem. Having a solid architecture is important and will allow you to add more complexity without having to change as much existing code, but the general problem of creating patterns that are interesting, varied and challenging is beyond the scope of a Stack Overflow question.</p>
    singulars
    1. This table or related slice is empty.
    1. POCave Co. type game, shooting functions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USCheeseWarlock
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCave Co. type game, shooting functions
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COAs I have it now, each enemy does keep track of its `ShotPattern`, I just call it `Shoot`. That's an interesting thought, but i'm not sure how I would make the patterns extend it, I'll just have to think about that. Same with the `ShotPattern` affecting the bullets. Before I had it set up that the bullets took in parameters and would affect themselves. Thanks for the insight, I've got some thinking to do
      singulars
      1. PO
      1. USEvan Ward
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload