Grimrock

SpiderFighter wrote:#stuff (is this for the One Room? Lemme know, please, and I'll change my concept, since you're going before me).

SpiderFighter wrote:It's definitely possible to do this all with plates, counters, and timers, but the most difficult aspect is clutter on the screen. When you have one plate with 25 lines radiating off it to different walls, it becomes extremely difficult to see the wall that you missed connecting to. Moreso, if you are using the same plate to close additional walls. Your best friend, as you've said, is graph paper. I'd recommend picking a direction (clockwise, counterclockwise) and sticking with that as you start connecting things. Regardless of whether you make the connections by hand or by scripting, though, keep your plates 3 squares away from any shifting walls or the player will be able to duck underneath them before they close (that is, two spaces between your plate and the wall).

Skuggasveinn wrote:

- Earthquake-ish sound, i will find a suitable sound for this as the current earthquake sound lasts forever

you can just redefine the current one with no loop

Code: Select all

defineSound{
       name = "earthquakenoloop",
       filename = "assets/samples/env/earthquake_01.wav",
       loop = false,
       volume = 1,
       minDistance = 1,
       maxDistance = 6,
    }

HaunterV wrote:

SpiderFighter wrote:#stuff (is this for the One Room? Lemme know, please, and I'll change my concept, since you're going before me).

It is.

HaunterV wrote:That's why I plan to 'assemble' the 'roomlets' in various parts of the map then slide them into position afterwards. So, when creating I'll make the layout of the 1st 'room' in the bigger main room. Then select it all and slide it to the top right corner, repeat for the other configurations - making them, hooking them all up, and then sliding them aside. Then I'll slide the 'roomlets' into place one at a time, stitching them together triggerwise where needed. This is of course tedious and prone to mishaps as there is no undo action in the editor yet so one false click and drag, and it'll all go up in smoke.

SpiderFighter wrote:It's definitely possible to do this all with plates, counters, and timers, but the most difficult aspect is clutter on the screen. When you have one plate with 25 lines radiating off it to different walls, it becomes extremely difficult to see the wall that you missed connecting to.

Komag wrote:Might be better to have a timer ticking along a tick counter which does different things at different times. Here is an example from the re-creation of the dance dance puzzle:

SpoilerShow

Code: Select all

danceTick = 0
function danceStep()
  dancePlate:setTriggeredByParty(false)
  if danceTick == 10 then
    danceSpawnerM:activate()
  elseif danceTick == 40 then
    danceSpawnerM:activate()
  elseif danceTick == 60 then
    danceSpawnerL:activate()
  elseif danceTick == 80 then
    danceSpawnerL:activate()
  elseif danceTick == 100 then
    danceSpawnerR:activate()
  elseif danceTick == 105 then
    danceSpawnerM:activate()
  elseif danceTick == 110 then
    danceSpawnerR:activate()
  elseif danceTick == 125 then
    danceSpawnerL:activate()
  elseif danceTick == 140 then
    danceSpawnerL:activate()
  elseif danceTick == 150 then
    danceSpawnerR:activate()
  elseif danceTick == 157 then
    danceSpawnerM:activate()
  elseif danceTick == 164 then
    danceSpawnerL:activate()
  elseif danceTick == 171 then
    danceSpawnerM:activate()
  elseif danceTick == 178 then
    danceSpawnerR:activate()
  elseif danceTick == 185 then
    danceSpawnerM:activate()
  elseif danceTick == 195 then
    danceSpawnerL:activate()
  elseif danceTick == 205 then
    danceSpawnerR:activate()
  elseif danceTick == 215 then
    danceSpawnerL:activate()
  elseif danceTick == 225 then
    danceSpawnerR:activate()
  elseif danceTick == 230 then
    danceSpawnerM:activate()
  elseif danceTick == 235 then
    danceSpawnerL:activate()
  elseif danceTick == 240 then
    danceSpawnerM:activate()
  elseif danceTick == 245 then
    danceSpawnerM:activate()
  elseif danceTick == 250 then
    danceSpawnerR:activate()
  elseif danceTick == 255 then
    danceSpawnerM:activate()
  elseif danceTick == 260 then
    danceSpawnerL:activate()
  elseif danceTick == 269 then
    danceSpawnerR:activate()
  elseif danceTick == 279 then
    danceSpawnerL:activate()
  elseif danceTick == 287 then
    danceSpawnerR:activate()
  elseif danceTick == 292 then
    danceSpawnerM:activate()
  elseif danceTick == 350 then
    danceDoor:open()
    danceTimer:deactivate()
    return
  end
  danceTick = danceTick + 1
end

the single timer nearby is set to 0.1 seconds and just keeps ticking away at the script, causing each spawn at the right time in sequence, etc. You could do anything you want at the different times.

HaunterV wrote:
this does sound like a more intuitive way of handling it as opposed to my previous method. So i would replace spawnerM with sd_rm_cfg_1_ ?

for ent in allEntities(level) do
  if ent.id:sub(1,12) == "sd_rm_cfg_1_" then
    ent:open()
  end

old_config = 1

function changeConfig()
  local configurations = {"sd_rm_cfg_1_", "sd_rm_cfg_2_", "sd_rm_cfg_3_"}
  repeat new_config = math.random(1,#configurations) until new_config ~= old_config
  for ent in allEntities(party.level) do
    if ent.id:sub(1,12) == configurations[new_config] then
      ent:open()
    elseif ent.id:sub(1,12) == configurations[old_config] then
      ent:close()
    end
  end
  old_config = new_config
end

HaunterV wrote:for C) can i put some sort of kill script? or kill entity in the on die part of its definition? as long as i name the script Entity that this thing uses?

or can i mutate that scan level script and when it doesnt find the monster it stops running? or something like that?