mekonbekon's Forum Posts

  • You can add the timer plugin to the button - if you set the timer to regular you can then use it to spawn an enemy every x seconds:

    dropbox.com/s/23reuzoys26srap/buttonTimerSpawner.c3p

    Click the black button to turn the enemy spawn on and off.

  • Add the AJAX plugin to your project. To load the array file use the following sequence of actions:

    AJAX:Request yourArray.json

    System: Wait for previous actions to complete

    yourArrayObject: Load from JSON string AJAX.lastdata

  • In fact that example doesn't even need the "trigger once" condition in the first event.

  • This should work for you, no need to mention frame 2:

    dropbox.com/s/qwvrr0fylt405pf/mouseOver.capx

  • No problem, happy to help :-)

  • Hi,

    I would approach such a course by covering the basics of design, development and production in conjunction with practical exercises:

    Design

    • The core interactive game loop between player, input devices, computer, and output devices - this helps cement the idea that it's important to consider all components of the game loop when formulating a design, especially the player's ability and motivation.
    • Mechanics (the building blocks), Dynamics (how mechanics interact) and Aesthetics (coating dynamics with emotion).
    • How objectives married with constraints provides challenge. How goal conflict arising from divergent objectives creates interesting challenges.
    • Using progression loops and difficulty curves as methods of introducing new mechanics and challenges.
    • Types of performance reward and the criteria that unlock them (typically accuracy, speed and consistency of challenge completion).

    Production

    • The stages in production pipeline: planning, development, testing, publication.
    • Planning and communicating a concept: how to use diagrams, flowcharts, spreadsheets and written descriptions to capture your concept and share it with others.
    • Organising a project: folder structure (I like to use the ABCD system: Assets, Builds, Code, Documents); naming conventions etc.
    • Estimating scope: getting into the habit of planning ahead and setting realistic targets.

    Development

    • Useful tools: project management apps, art and audio packages etc.
    • Construct 3 overview: the key features of the software; how the event system works.

    This should give the students a solid foundation from which to build simple games. The topics can be drip fed into the course as and when they're useful rather than overloading the students with all of it at the beginning.

    Practical

    I would allow the students to pick one from a selection of the example or template projects from the C3 start page and help them modify and develop that into a complete game. In individual lessons I'd focus on how to implement useful reusable components such as score systems, health, lives, timers, levels, splash/menu/pause/results screens.

    Depending upon available time and the ability of the class I would introduce more complex but very useful features of C3 like functions, arrays, dictionaries, families and containers.

    Finally I would cover adding "juice" to a game - using audio and visual effects and animations to enhance player feedback and make your game pop.

    Ideally I'd aim for them to have something that can upload to the Scirra arcade by the end of course, so they can share their efforts.

    Hope that helps :-)

  • Also:

    1) In your new number function you're using Array Cur Value condition incorrectly - it only works in conjunction an Array: for each XYZ element condition.

    2) The repeat may pick the same co-ordinates twice so you may only get one number in the array.

    3) Using int(0,3) won't pick 3 and may put a number on X=0 so when you slide it will disappear off the array.

    Here's an example that I think gets closer to what you're after:

    dropbox.com/s/yu4sgvidmpocp32/slideArray.c3p

    Note that this only works if you're sliding to the left - if you change the slideX value to positive then there's a chance you can overwrite values as you slide, due to the order in which the For Each XYZ element condition proceeds.

  • No problem, happy to help :-)

  • The angle input field will only take an expression that resolves to a single number. If you are trying to set the angle of an object to point at the mouse position use the following in the field:

    angle(object.X, object.Y, mouse.X, mouse.Y)

    This will return the angle from the object to the mouse cursor.

  • I had a go at simplifying your code:

    dropbox.com/s/9r1s1hlwtcphf8p/spawnObs.c3p

    ...I've included comments in the code to explain the changes. The X positions that the objects spawn at comply with your current logic, although given the way you structured your events I'm not sure if this outcome is as you intended:

    In your event 4 you set g_posX to either 190 or 550; this means the first event in function makeobjs will not fire as g_posX is never 370. As a result your subsequent events are equivalent to setting g_posX using a single choose(190, 370, 370, 550) action i.e. 370 will be chosen twice as often as the other two positions. I've modified the actions to reflect this, but if that isn't what you wanted let me know what you need and I'll have another pop at it.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Hi, you need to place the conditions following the else into the same event block as the else.

    Also, if you're calling from a function you don't need the trigger once conditions.

  • The easiest way is to assign the Platform behaviour to the player and then increase the Jump sustain value in the behaviour's properties.

  • No problem, glad to help out :-)

  • Here's one way to do it, using platform behaviour to move the enemies towards the player and then bullet and rotate once they've been kicked:

    dropbox.com/s/m4rugrindid3aeo/KickEnemy.c3p

    arrow keys to move, space to kick.

    Tom

    mekonbekon free edition does allow you to export to the arcade

    Huh. Well shut my mouth! Thanks for setting me right.

    To be fair, I had a hunt all around the site before posting and couldn't see anything up front that indicated this was a feature of the free version, only a string of crosses against export options on the feature comparison list.

    I just had another look now, and the only reference I could find to this was at the end of the beginner's tutorial (HTML5 exports too it seems?). I'd have thought letting prospective users know they can publish and share their games in minutes would have been a key promotional point.