Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - b0undarybreaker

#1
Ah, right. I've been doing to much GML lately.
Also, I've realized that I've been going about this all wrong. I should be using map:on_obtained_treasure(treasure_item, treasure_variant, treasure_savegame_variable) instead.
#2
Oh, boy. I think at some point I might need to move this to bug reports. The if not card and cardchecked doesn't remove the pointer, changing it to if not card:exists() and cardchecked both spams the console and doesn't remove the pointer, and I'm just not sure if erroring while trying to index a value for entity:exists() is exactly the best thing because if it can't find the entity then it's doing its job. If there's something huge I'm missing here, please let me know, but I'm just not sure what's going on with this anymore.
#3
A friend and I looked the code over and realized what was wrong. It was erroring saying card was a nil value without it being map.card, but only after I picked the card up. To fix that, I added in stops for the loop:
Code ( lua) Select
function map:on_update()
  if not card and cardchecked then
    cardpoint:remove()
    print("Card removed!")
    cardchecked = true
  end
  if not gem and gemchecked then
    gempoint:remove()
    print("Gem removed!")
    gemchecked = true
  end
end

So the error doesn't spam anymore. However, it won't do the gempoint:remove() still. Do I need to do something to gempoint to make it work properly?
#4
For a quick note, this happens if it's just card:exists() as well, so it isn't the map.card that's the issue.
#5
Development / Detecting when a pickable is picked up
August 05, 2017, 08:27:14 AM
I have two pickable items named card and gem and I want to be able to tell when they're picked up and make pointers over each item disappear. I'm using this script to do that:
Code (lua) Select
function map:on_update()
  if not map.card:exists() then
    cardpoint:remove()
    print("Card removed!")
  else if not map.gem:exists() then
    gempoint:remove()
    print("Gem removed!")
  end
  end
end

However, when I do that, it errors Error: In on_update: [string "maps/street_arspace.lua"]:79: attempt to index field 'card' (a nil value), line 79 being if not map.card:exists() then. Any suggestion for what I'm doing wrong?
It also for some reason doesn't work without that extra end there. I'm not sure what's up with that.
#6
Much better. Thank you!!!
#7
I'm working on making a game with Solarus and I want the WASD keys to be usable for moving the character alongside the arrow keys, kinda like how you can use the demo mouse_control script and the arrow keys at the same time. Is this possible to do? I've tried making a script off of the mouse_control one but it isn't seeming to work. It doesn't help that d is a pause key, apparently. If anyone can point out where I messed up, I'd love to know. Thanks!

Code (lua) Select

require("scripts/multi_events")


local function initialize_wasd_control_features(game)

  local wasd_control = {}

  local is_key_pushed = false
  print("wasd control startup")

  -- Movement of the hero.
  local directions_pressed = {
      right = false,
      up = false,
      left = false,
      down = false
  }

  function wasd_control:on_key_pressed(key)
    is_key_pushed = true
   
  end

  function wasd_control:on_mouse_released(keu)

    is_key_pushed = false
    pressed_key = key
  end

  function wasd_control:on_update()

    local map = game:get_map()
    if map == nil then
      return
    end

    if is_key_pushed then

      pressed_right = sol.input.is_key_pressed("d")
      pressed_up = sol.input.is_key_pressed("w")
      pressed_left = sol.input.is_key_pressed("a")
      pressed_down = sol.input.is_key_pressed("s")

      self:update_direction("right", pressed_right)
      self:update_direction("up", pressed_up)
      self:update_direction("left", pressed_left)
      self:update_direction("down", pressed_down)
    else

      for direction, _ in pairs(directions_pressed) do
        self:stop_direction(direction)
      end
    end
    function wasd_control:start_direction(direction)

      if not directions_pressed[direction] then
        directions_pressed[direction] = true
        game:simulate_command_pressed(direction)
      end
    end

    function wasd_control:stop_direction(direction)

     if directions_pressed[direction] then
        directions_pressed[direction] = false
        game:simulate_command_released(direction)
      end
    end
  end
end
local game_meta = sol.main.get_metatable("game")
game_meta:register_event("on_started", initialize_wasd_control_features)
return true
#8
Ohhhhhhhh. Okay. The look of the tile preview to be half-wall and half-terrain confused me. Sorry!
#9
I'm splitting the ones I want to have as partial traversible tiles into separate tiles, but it takes the number of total tiles from 48 to 84, and it makes things excessively complex if I decide I want to move things around. For reference, I've attached images a map using the tiles and the tilesheet itself, with tile hitboxes shown. Optimally, each tile would just be a square, with specific terrain that dictates what parts of the tiles can be walked on, instead of having to split each full tile into smaller pieces to do it.
#10
Low walls are exactly what I want, but there's just a problem with them: there are only low walls in one direction. I can't have them covering just the left half of the tile or just the right half of the tile, only covering just the bottom half.
#11
Bugs & Feature requests / More tile ground types
July 13, 2017, 10:00:48 AM
I'm making a road in my project and I want the sides of the road to be half-traversible, half-wall. However, the only half-traversible tile grounds are corners and low wall. I want something like low wall, but for the top, left, and right as well. Would that be possible to do, and do you think it might be possible to be able to make custom tile hitboxes in the engine as well? It'd be really neat to be able to craft your own ground types by polygon out of the basic types.