Capilson's Forum Posts

• • Capilson
  • 
  • • Joined 22 Jan, 2016
    • 
    • 1 topics • 2 posts
  • 1

  • 8 Jul, 2016
  • Quote

  Ok, thank you guys. I will opt for doing everything in one main capx, mainly because I feel quick testing of the levels is quite important for my game. I do plan on storing the levels in external files that the final game will then read.

  I liked the possibility that I might release the level editor to the players and doing everything in one capx definitely makes it easier. Thank you all for your suggestions!

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • Capilson
  • 
  • • Joined 22 Jan, 2016
    • 
    • 1 topics • 2 posts
  • 1

  • 6 Jul, 2016
  • Quote

  Hi everyone,

  I'm new to gamedev and I am currently working on only my second game. The core art and mechanics are already defined but now I've come to the conclusion that I will need to create a level editor for my game. However, due to the specifics of the game mechanics I want for the person in charge of level editing to quickly test the level. Ideally I will continue working on the developing the game, (sound, gui, additional mechanics, etc), in parallel with the person creating the levels.

  What I would like to is that when the level creator test plays the new levels, the gameplay would always be updated with the latest development stage, ideally in a seemless process.

  What process should I use?:

  • 2 different capx, one for the game and another for level editor, and manually update level editor?
  • define a common list of sprites, events, sounds etc that is shared by 2 capx? Is this possible?

  I am drawing a blank at this stage, I would appreciate any help. Thank you in advance.