#Greenfoot code examples how to

In a group of 3, that would mean 15 unique features. If you have your own features, they can be substituted for mine, but everyone MUST submit 5 unique features for their part of the game. Your job is to add more examples of loops into your game. Making a SmartBomb that tracks the closest Actor as its target.Previous FreezeBomb implementation (slightly different but also Freezes more Actors/classes than just the Brick).Fireball – A bomb which explodes into many directions (if the bomb was a RealMover it would not experience the rounding issues seen in the end of the video).Previously we had worked on similar loops, you may wish to have a look at these also:

#Greenfoot code examples how to

Now that (hopefully) you are warmed up to the idea of using loops, here is the last suggestion I have for you on how to use them in Greenfoot.Īdding an interface to effect multiple Actors (across different classes) – FreezingBrick

public void addLine(String name, int startX, int startY, int n, double dx, double dy).

public void addRandom(String name, int n).

Loops that need to be written can be found in the following methods:

Here is the demo video of your tasks in the WorldBuilder The exercises are intended to help you build your levels, they can all be found in the WorldBuilder Class From here you should be able to start making your game.

After this we’ll add some mandatory features that require more looping but the rest is up to you. This is the last round to “fix my code” so that you will now see a PlatformWorld/PlatformMover coming to life. This must included the main character itself so that it’s movement + the reverse movement will make it stationary but the background will move making it appear to move. Your next task is to fix the scrolling world so that all of the other Actors in the World move away from the main character whenever the window is moved (scrolling happens). If you are curious about how it is done better, one method is the Separate Axis Theorem. The methods you will “fix” are:Īs an aside… this is not a very efficient method for collision detection. Your first job is to complete the reactions a PlatformMover must have when it collides with a Platform. Otherwise, leave my code alone and subclass the file you would like to make additional features to or change the behaviour of. IMPORTANT – you should only fix the code where I have instructed you to do so. As you follow the lessons below you will edit these files so save it somewhere for future reference. Remember to ‘Compile’ when any changes are made.Here is the Skeleton framework for the Platform game that you will fix before you start your own adventure. If you wanted to change ‘Leaf’ to ‘Grass’ make the change in the line below. This takes you to the code behind the scenario. To do this, right-click on the class again and select Open Editor. Choosing a new image for a classĪnother edit might be to change the name of a class. The name of the class would still be ‘Leaf’. Then select the new image, for example a grass-like image. Selecting a new image for a class in Greenfoot If you need to change the image for a class, right-click the class and select ‘Set Image’. This code says that the class ‘Leaf’ is an extension of the class ‘Actor’, which means that ‘Leaf’ has inherited the states and behaviours of ‘Actor’. When the definitions are completed, open the editor by right-clicking the object and selecting Open Editor. Here, a ‘Leaf’ subclass is being created: Naming a new class in Greenfoot It is then possible to name the class and select an image. Right-click on the Actor class and select ‘New subclass…’ Creating a new subclass in Greenfoot To add a new class, create it as a subclass of the Actor class. They are mainly used to alter the look of the World, for example the size and background image. For example, the Actor classes can move and turn. There are a number of methods that can be applied to items in the different classes. In the image above, the WombatWorld is the sand background. In Greenfoot, the World class is the background. In the example above, the WombatWorld subclass is connected below the World class and the Wombat subclass is connected below the Actor class.

There are two main classes in Greenfoot: ‘World’ and ‘Actor’. Greenfoot’s two main classes, ‘World’ and ‘Actor’ In Greenfoot, the classes and subclasses are shown on the right-hand side of the window.