LÖVE

• Sprite
  • Mobile
    • Player
    • Enemy
  • Item
    • Coins
    • Hearts

• Player
  • Mobile
  • Controllable
  • Jumper Physics
• Enemy
  • Mobile
  • AI Controlled
  • Jumper Physics
• Bullet
  • Mobile
  • Projectile Movement
• Coin
  • Collectable
• Heart
  • Collectable

davisdude wrote:I don't know if this exactly what you wanted, but here you go:

You can make a 'class' sort of thing. I'm not very good at explaining so here's a basic example of a rectangle 'class' builder:

rectangle.lua:

Code: Select all

rectangle = {} --creates a table called rectangle to store all of your variables
rectangle.__index = rectangle --creates a 'path' to take 

function rectangle.create( x, y, width, height, mode, color ) --creates the rectangles that you want, with the x, y, width, height, mode ( "fill", line" ) and color (as a table)
local rect = {} --creates a local table that puts all the values in a table
setmetatable( rect, rectangle )

rect.x, rect.y, rect.width, rect.height, rect.mode, rect.color = x, y, width, height, mode, color

return rect
end

function rectangle:draw()
  love.graphics.setColor( self.color )
  love.graphics.rectangle( self.mode, self.x, self.y, self.width, self.height )
end

main.lua

Code: Select all

require "rectangle.lua"

function love.load()
  rectangle = rectangle.create( 32, 32, 32, 32, "fill", { 255, 0, 0 } ) --makes a rectangle with the name 'rectangle'
end

function love.draw()
  rectangle:draw()
end

Eamonn wrote:

davisdude wrote:I don't know if this exactly what you wanted, but here you go:

You can make a 'class' sort of thing. I'm not very good at explaining so here's a basic example of a rectangle 'class' builder:

rectangle.lua:

Code: Select all

rectangle = {} --creates a table called rectangle to store all of your variables
rectangle.__index = rectangle --creates a 'path' to take 

function rectangle.create( x, y, width, height, mode, color ) --creates the rectangles that you want, with the x, y, width, height, mode ( "fill", line" ) and color (as a table)
local rect = {} --creates a local table that puts all the values in a table
setmetatable( rect, rectangle )

rect.x, rect.y, rect.width, rect.height, rect.mode, rect.color = x, y, width, height, mode, color

return rect
end

function rectangle:draw()
  love.graphics.setColor( self.color )
  love.graphics.rectangle( self.mode, self.x, self.y, self.width, self.height )
end

main.lua

Code: Select all

require "rectangle.lua"

function love.load()
  rectangle = rectangle.create( 32, 32, 32, 32, "fill", { 255, 0, 0 } ) --makes a rectangle with the name 'rectangle'
end

function love.draw()
  rectangle:draw()
end

....that's all an entity is!??! I thought it was something really complicated! So if I had a player 'class'(a player file) and required it and used it's update and draw functions, the player is an entity? If I had a ball falling, is that an entity? I think what Inny was saying was that you would have a generic type of entity base, and you would derive from that and in another file and make a more specific type of entity. It seems kind of like inheritance in C++ or Objective C. Anyway, I think I understand it now! Thanks everyone!

Entity = {}

function Entity.new(id, tag, grouptag)
	local o = {}
	o.Id = id
	o.Tag = tag
	o.GroupTag = grouptag
	o.Components = {}
	setmetatable(o, { __index = Entity }) 
  return o
end

function Entity:Add(component)
	self.Components[component.Id] = component
end

Movement = {}

function Movement.new(id, x, y, xv, yv)
  local o = {}
  o.Id = id
  o.X = x
  o.Y = y
  o.Xv = xv
  o.Yv = yv
  setmetatable(o, { __index = Movement }) 
  return o
end

function love.load()
	-- Create Player Entity
	entity = Entity.new(1, "Player", "")
        -- Add Movement Component to Player Entity
	entity:Add(Movement.new(1,100,100,5,5))
	
	
end

EvilSheepLord wrote:

Eamonn wrote:

davisdude wrote:I don't know if this exactly what you wanted, but here you go:

You can make a 'class' sort of thing. I'm not very good at explaining so here's a basic example of a rectangle 'class' builder:

rectangle.lua:

Code: Select all

rectangle = {} --creates a table called rectangle to store all of your variables
rectangle.__index = rectangle --creates a 'path' to take 

function rectangle.create( x, y, width, height, mode, color ) --creates the rectangles that you want, with the x, y, width, height, mode ( "fill", line" ) and color (as a table)
local rect = {} --creates a local table that puts all the values in a table
setmetatable( rect, rectangle )

rect.x, rect.y, rect.width, rect.height, rect.mode, rect.color = x, y, width, height, mode, color

return rect
end

function rectangle:draw()
  love.graphics.setColor( self.color )
  love.graphics.rectangle( self.mode, self.x, self.y, self.width, self.height )
end

main.lua

Code: Select all

require "rectangle.lua"

function love.load()
  rectangle = rectangle.create( 32, 32, 32, 32, "fill", { 255, 0, 0 } ) --makes a rectangle with the name 'rectangle'
end

function love.draw()
  rectangle:draw()
end

....that's all an entity is!??! I thought it was something really complicated! So if I had a player 'class'(a player file) and required it and used it's update and draw functions, the player is an entity? If I had a ball falling, is that an entity? I think what Inny was saying was that you would have a generic type of entity base, and you would derive from that and in another file and make a more specific type of entity. It seems kind of like inheritance in C++ or Objective C. Anyway, I think I understand it now! Thanks everyone!

No, not even close. The Entity/Component model is exactly as described above, so I won't go into it again but give another brief example. A "Player" entity or a "Bad Guy" entity is made of components. Each component gives that entity certain properties. Examples of components could be Movement, Animation, Collision, Controllable.

A VERY rough example:

Code: Select all

Entity = {}

function Entity.new(id, tag, grouptag)
	local o = {}
	o.Id = id
	o.Tag = tag
	o.GroupTag = grouptag
	o.Components = {}
	setmetatable(o, { __index = Entity }) 
  return o
end

function Entity:Add(component)
	self.Components[component.Id] = component
end

Movement = {}

function Movement.new(id, x, y, xv, yv)
  local o = {}
  o.Id = id
  o.X = x
  o.Y = y
  o.Xv = xv
  o.Yv = yv
  setmetatable(o, { __index = Movement }) 
  return o
end

function love.load()
	-- Create Player Entity
	entity = Entity.new(1, "Player", "")
        -- Add Movement Component to Player Entity
	entity:Add(Movement.new(1,100,100,5,5))
	
	
end

The idea behind this is you have a Player Entity which contains a component that gives this entity an X, Y coordinate position and an X, Y velocity(Xv, Yv)
This is just an example of the concept. You may wish to move X, Y into a position Component or just give all entities the X, Y property. It depends on the needs of the system and how complex you want to go. You would also create a 'System' or 'Manager' object(table) that will perform operations on your entity, for example a MovementSystem would take the Xv, and Yv, values and apply it to the x, y values. The 'DrawSystem' would draw the the entity based on the X, Y in the Movement/Position Component or however you want to break it down. As I said a very ROUGH Example.

Disclaimer: I have only been looking at Love2d and Lua for a couple of days now. If there is a better way to do things in the code I post please let me know. Thanks!