Recent Posts

Pages: 1 [2] 3 4 ... 10

Bugs & Feature requests / Re: Improve gamepad support

« Last post by alexgleason on October 14, 2018, 10:03:14 pm »

SDL_gamecontroller sounds like magic. Did this pull request ever happen?

Development / Re: Adding gamepad support to the title screen

« Last post by Diarandor on October 14, 2018, 08:29:31 pm »

A clean way to do that is to use general events:
http://www.solarus-games.org/doc/latest/lua_api_main.html#lua_api_main_events

Development / Re: Adding gamepad support to the title screen

« Last post by alexgleason on October 14, 2018, 06:56:08 pm »

This is a FAR simpler solution. If you're willing to just accept that your game has only one save file, you can start it up first thing, then you'll be free to use on_command_pressed in your menus. Nothing else but this is needed in your main.lua:

Code: Lua

function sol.main:on_started()
  local game = sol.game.load("save1.dat")
  game:start() -- This is where the magic happens
 
  sol.menu.start(game, solarus_logo) -- We're setting the menus to use the "game" we started above
 
  function solarus_logo:on_finished()
    sol.menu.start(game, title_screen) -- The title screen uses internal logic to reload the game once it's ready
  end
 
end
 

Development / Adding gamepad support to the title screen

« Last post by alexgleason on October 14, 2018, 04:24:20 pm »

Hey all, just wanted to share my progress with this. I ended up writing a script that gives default configs to any menu object:

scripts/enable_commands.lua

Code: Lua

-- ♡ Copying is an act of love. Please copy and share.
--
-- Use this script to pass in a game or menu object and have it set up
-- default keyboard and joystick controls so you can use `on_command_pressed`
-- as expected.
--
-- Usage:
--    local enable_commands = require("scripts/enable_commands")
--    enable_commands.enable(my_menu)
--
-- Then simply define `function my_menu:on_command_pressed(command)`
 
local enable_commands = {}
 
 
local function on_key_pressed(self, key)
  if self.on_command_pressed == nil then return true end
  if key == "space" then self:on_command_pressed("action")
  elseif key == "c" then self:on_command_pressed("attack")
  elseif key == "d" then self:on_command_pressed("pause")
  elseif key == "up" then self:on_command_pressed("up")
  elseif key == "down" then self:on_command_pressed("down")
  elseif key == "left" then self:on_command_pressed("left")
  elseif key == "right" then self:on_command_pressed("right")
  elseif key == "x" then self:on_command_pressed("item_1")
  elseif key == "v" then self:on_command_pressed("item_2") end
  return true
end
 
local function on_key_released(self, key)
  if self.on_command_released == nil then return true end
  if key == "space" then self:on_command_released("action")
  elseif key == "c" then self:on_command_released("attack")
  elseif key == "d" then self:on_command_released("pause")
  elseif key == "up" then self:on_command_released("up")
  elseif key == "down" then self:on_command_released("down")
  elseif key == "left" then self:on_command_released("left")
  elseif key == "right" then self:on_command_released("right")
  elseif key == "x" then self:on_command_released("item_1")
  elseif key == "v" then self:on_command_released("item_2") end
  return true
end
 
local function on_joypad_button_pressed(self, button)
  if self.on_command_pressed == nil then return true end
  if button == 0 then self:on_command_pressed("action")
  elseif button == 1 then self:on_command_pressed("attack")
  elseif button == 4 then self:on_command_pressed("pause")
  elseif button == 2 then self:on_command_pressed("item_1")
  elseif button == 3 then self:on_command_pressed("item_2") end
  return true
end
 
local function on_joypad_button_released(self, button)
  if self.on_command_released == nil then return true end
  if button == 0 then self:on_command_released("action")
  elseif button == 1 then self:on_command_released("attack")
  elseif button == 4 then self:on_command_released("pause")
  elseif button == 2 then self:on_command_released("item_1")
  elseif button == 3 then self:on_command_released("item_2") end
  return true
end
 
local function on_joypad_axis_moved(self, axis, state)
  if axis == 0 then
    if state == 1 and self.on_command_pressed then self:on_command_pressed("right")
    elseif state == -1 and self.on_command_pressed then self:on_command_pressed("left")
    elseif state == 0 and self.on_command_released then
      -- FIXME: Only release the last command?
      self:on_command_released("right")
      self:on_command_released("left")
    end
  end
  if axis == 1 then
    if state == 1 and self.on_command_pressed then self:on_command_pressed("down")
    elseif state == -1 and self.on_command_pressed then self:on_command_pressed("up")
    elseif state == 0 and self.on_command_released then
      -- FIXME: Only release the last command?
      self:on_command_released("down")
      self:on_command_released("up")
    end
  end
  return true
end
 
-- Enable on an item
function enable_commands.enable(item)
  item.on_key_pressed = on_key_pressed
  item.on_key_released = on_key_released
  item.on_joypad_button_pressed = on_joypad_button_pressed
  item.on_joypad_button_released = on_joypad_button_released
  item.on_joypad_axis_moved = on_joypad_axis_moved
end
 
return enable_commands
 

Then just run your menu through this, either in main.lua or in your menu script itself, like so:

Code: Lua

local enable_commands = require("scripts/enable_commands")
 
-- Ability to use game commands on these menus
enable_commands.enable(title_screen)
 
function title_screen:on_command_pressed(command)
  -- Handle commands here! No need to handle keys or joypad inputs.
end
 

It's a horribly verbose script! But it works. Normally the save file stores the controller config, so it creates a chicken and egg problem where you must create a save file before you can configure a gamepad, but need to go through the file select menu first. This partially works around that by assigning the Solarus default keyboard and joystick inputs to normal gamepad actions like "attack" and "action" etc. for a particular menu (the title screen).

What I think I'll actually end up doing is load the game before the title screen, and maybe let the player configure their input device here. My goal is to make the game playable on a platform like RetroPie where no keyboard exists. But this works for now.

As a side note, I think having 3 separate save files is overkill for most Solarus games. Unlike the days of Super Nintendo, most people have their own personal devices that can run Solarus, whether that's a laptop, desktop, Android phone/tablet, or Nintendo Switch. The exception might be a RetroPie device, but even then these often have hundreds of games and different people will probably be playing a different game during a different time. So, I'm going to focus on handling 1 save file at a time which will make things much easier.

Your scripts / Auto-assign an item to slot 1 if it's empty.

« Last post by alexgleason on October 13, 2018, 03:40:57 am »

This script is useful for when your character receives the first item of the game. Rather than making them equip the item, you can make it automatically assigned to slot 1. Adding slot 2 support probably wouldn't be too difficult. Here's the script.

Code: Lua

-- ♡ Copying is an act of love. Please copy and share.
 
require("scripts/multi_events.lua")
 
-- When the player obtains their first item, assign it to slot 1 automatically
 
local function item_obtained_cb(self, variant, savegame_variable)
  local slot_1 = sol.main.game:get_item_assigned(1)
  if slot_1 == nil and self:is_assignable() then
    sol.main.game:set_item_assigned(1, self)
  end
end
 
local item_metatable = sol.main.get_metatable("item")
item_metatable:register_event("on_obtained", item_obtained_cb)

Install it by creating the file scripts/item_auto_assign.lua in your project and pasting the above code.

Then, open scripts/features.lua and add this to the list:

Code: Lua

require("scripts/item_auto_assign")

I am assuming you're using the Solarus engine boilerplate code, which already includes the multi_events script.

Your projects / Re: Vegan on a Desert Island

« Last post by alexgleason on October 12, 2018, 06:39:45 pm »

I played Survival Kids for a few hours last night. It really is super similar to what I'm going for! I was surprised.

The way you can collect, use, and combine items was really illuminating. I think this will help me make some decisions about that. Thanks again.

I agree that it's too hard, though. I prefer to enjoy the game I'm playing instead of feeling like I'm constantly fighting for my life, haha.

Development / Re: Cutscene troubles (as menu)

« Last post by Christopho on October 12, 2018, 12:40:14 pm »

You stored the game on the cutscene table (cutscene.game), but you are trying to access it just with "game".

Development / Re: Cutscene troubles (as menu)

« Last post by Eyth on October 12, 2018, 11:16:01 am »

Tried it, I'm still doing something wrong...

When I have:

Code: Lua

local cutscene = {}
 
function cutscene:intialize(game)
cutscene.game = game
end
 
function cutscene:on_started()
--sprites, sol.audio.stop_music(), timers--
end
 
function cutscene:on_finished()
--timers:stop, hero:unfreeze()
game:set_paused_allowed(true)
end
 
function cutscene:on_draw(battle_surface)
--sprites and images--
end
 
function cutscene:on_command_pressed(command)
  if command == "action" then
    sol.menu.stop(self)
  end
end
 
return cutscene
 

...the engine says:"Error: In on_finished: scripts/cutscene.lua:13: attempt to index global 'game' (a nil value)"
I have to add, I made an "on_command_pressed()" event to test the scene, because it doesnt end itself for now.

So I still cant use game-events, what am I doing wrong?

Development / Strange behavior with game:on_command_pressed() and hero:start_attack()

« Last post by alexgleason on October 12, 2018, 02:26:23 am »

Not sure if this is a bug or user error, but I wanted to share.

My goal is to disable the "attack" command completely and use the sword as a standard item (with hero:start_attack()). In main.lua:

Code: Lua

function game:on_command_pressed(command)
  -- Disable attacking; the stick is a regular item
  if command == "attack" then
    return true
  end
  ...
end

However, when I swing the sword, I can actually still press and hold the attack button while the sword is mid-animation. This causes sword-loading to trigger. I'm baffled by the fact I can do this when I've overridden the attack command to "return true" whenever it's pressed.

I ended up adding this to scripts/meta/hero.lua to solve my issue:

Code: Lua

-- The hero can only swing the sword, nothing else
function hero:on_state_changed(state)
  if state == "sword loading"
  or state == "sword tapping"
  or state == "sword spin attack" then
    hero:freeze()
    hero:unfreeze()
  end
end

Freezing and unfreezing the hero when going into the sword loading state effectively disables that state, which is what I want. (In my game the sword is limited)