Shooting a gun

Getting Started Newbie Questions
#81

Sorry for the multiple answer, but I wanted to also suggest making a few simple examples using composer.*  before using it for game work. 

You need to have a solid grasp of how it works and when the various functions are called as well as the concept of will and did phases for show() and hide().

When you fully understand these things, using composer.* will make a lot more sense and be less mysterious.

At this time I can see you’re totally ignoring or not aware of the will/did phases.  This leads me to believe you’re treating composer.* exactly like storyboard.* and they are two very different beasts.

This is a great place to start:

https://docs.coronalabs.com/guide/system/composer/index.html

#82

I just tried this example on the corona docs :

-- example1.lua local M = {} print( "example1.lua has been loaded" ) return M -- main.lua local ex1 = require( "example1" ) ex1.testvar = "Hello World!"

That worked . I got example1.lua has been loaded in the simulator .

I tried the first test you gave me and this is what I did :

Main.lua : local M = {} local example1 = require "example1" -- or whatever you named the module file. example1.create( display.currentStage ) timer.performWithDelay( 1000, example1.destroy ) -- If this doesn't crash you're ready for the next test. return M

example1.lua :

– example1.lua

  

local M = {}

return M

I’m getting this error :

main.lua:8: attempt to call field 'create' (a nil value)

This is line 8 :

example1.create( display.currentStage )

#83

When I tried the code in main.lua and example1.lua the other way around I get this error :

loop or previous error loading module 'example1'
#84

am I suppose to only use one file for all of the code ? If so which file ?

#85

@brandon,

Let me put together a small example of what the module should look like and I’ll post it so you can use it as a framework to scaffold your code onto.

-Ed

PS - Welcome back.  I know you’re in and out of the forums and I sense you’ve been struggling and a bit frustrated at times.  This time I think you’ll make some progress and get some satisfaction out of the experience.

Posting back in a bit…

#86

Thanks a lot Ed . I will try harder than I did before .

#87

@brandon

Here is the code: https://github.com/roaminggamer/RG_FreeStuff/raw/master/AskEd/2017/12/brandon.zip

In this zip file are three folders:

  • 001_starter - A bare bones module with create(), start(), stop(), destroy() functions and some basic parts I think you should always have.
  • 002_sample_game - OK, not really a game, but more like a tech demo showing how to make something very simple with the module.  Go into main.lua and experiment with the start, stop, destroy calls too.
  • 003_integrated_in_composer  - Basically 002 put into a composer scene.
    • Warning: This composer.* scene uses my custom format to separate the will and did phases of show() and hide() into separate function calls.  So be aware it is a little different from the default sample you see on the Corona site.

Here is the ‘game’ in action:

https://www.youtube.com/watch?v=0x2GxoWwDGU&feature=youtu.be

#88

One last note.  I know I never answered your ORIGINAL question.

That was on purpose.  

I think the code for your gun is something you can solve.  The real problem is that I think you’re having some issues with scope and visibility as well as composer.* concepts. 

I think that if you use the module first approach you’ll self-solve the gun problem and be in a much better place for future work.

Cheers,

Ed

#89

Okay this is what I did .

In my main.lua file I put what was in the example’s main.lua file :

local example1 = require "example1" local group = display.newGroup() example1.create( group ) timer.performWithDelay( 4000, function() example1.start() end ) timer.performWithDelay( 8000, function() example1.stop() end ) timer.performWithDelay( 12000, function() example1.destroy() end )

and in my example1.lua file I put what was in the example’s game.lua file :

local physics = require "physics" local cx, cy = display.contentCenterX, display.contentCenterY local fullw, fullh = display.actualContentWidth, display.actualContentHeight local isRunning = false local layers local game = {} function game.create( group ) game.destroy() layers = display.newGroup() layers.underlay = display.newGroup() layers.content = display.newGroup() layers.overlay = display.newGroup() -- group:insert( layers ) -- This group contains all layers layers:insert( layers.underlay ) -- Bottom layer. layers:insert( layers.content ) -- Middle layer layers:insert( layers.overlay ) -- Top layer end etc...

When I did that I got nothing . Nothing should up on the simulator or in the console . I’m guessing everything went well .

When I did this in my main.lua file : 

local example1 = require "example1" -- or whatever you named the module file. example1.create( display.currentStage ) timer.performWithDelay( 1000, example1.destroy ) -- If this doesn't crash you're ready for the next test.

and I left the game file the same, I don’t have any problems . Should I move on or should I be seeing something on my screen ? 

#90

Or should I continue with test 2 and implement my game code ?

#91

Please zip the whole project up and share it here.   You can use the ‘more reply options’ to attach the zip file to your post.

#92

When you ran the app and did not destroy it, did it run properly?

If you feel your game is ready to play, then by all means move on to using composer.*

#93

Okay the problem is fixed with the bullet .

#94

So should I put everything in composer now ? Or develop the whole game and then put it in composer ?

#95

I would develop as much of the game as I could without ever using composer.*  Then, when you’re satisfied, integrate it.

Over time you will get better and better at developing and you can integrate earlier.

However, let’s ask ourselves what composer.* is doing for us…

It is essentially giving us an easy way to create scenes, where we can have some of these scenes:

  • Splash screen
  • Home (main menu)
  • Options (maybe an overlay, maybe a normal scene)
  • Play (the place the game is actually played).  This is where the game module is most used.
  • Game Over (a place to show scores and ads, etc.)
  • …

As you can see, while you are developing a game and working on its mechanics, you don’t need any of that. 

So just use the game module for as long as possible directly from main.lua and save yourself a big headache and a lot of wasted effort. 

Do your interfaces later.

#96

Alright thanks . 

#97

I’m trying to transition my zombie because I can’t do spritesheets . I have this code :

zombie = display.newImage("zombie.gif") local w,h = display.contentWidth, display.contentHeight local function listener1( zombie ) print( "Transition 1 completed on object: " .. tostring( zombie ) ) end local function listener2( zombie ) print( "Transition 2 completed on object: " .. tostring( zombie ) ) end -- (1) move square to bottom right corner; subtract half side-length transition.to( zombie, { time=1500, alpha=0, x=(w-150), y=(h-300), onComplete=listener1 } ) -- (2) fade square back in after 2.5 seconds transition.to( zombie, { time=2000, delay=9500, alpha=1.0, onComplete=listener2 } )

But I don’t see the zombie at all and in the console it says the transitions were completed . What should I do ?

#98

You are displaying a still image, I don’t think Corona supports gifs in images. If you go online you could find software that splits gifs into sprites. 

#99

I’m using piskel and it’s hard as hell

#100

I have a sprite sheet now but I don’t know what to do