Grimrock

The way I see it, this thread is about short questions / short answers which don't qualify for a long thread.

(...and sometimes I see new threads and I wonder why they were created as they don't require more than one or two answers )

minmay wrote:Well, what would you prefer? People answering the questions, or people saying "no, that question isn't simple enough for this thread, go away"?

that was a joke. I mentioned at the beginning of my comment, to just ignore me.
it was a commentary just on how overwhelming all this scripting is to absorb

The problem is that using a single thread for multiple queries is a spectacularly awful way of asking questions and getting answers. I'm also new to Grimrock modding, I read this whole thread (It took quite a while...) and the valuable content within it is simply not easy to find, and demands a certain amount of patience which most casual modders simply will not have.

It would have been much better to stick to the tried and tested method of asking one question per thread. This allows people to then easily browse the forum and find relevant information at their leisure, based on the thread's title.

As someone who has moderated another forum for over ten years, I'd recommend that this thread should be broken up into its constituent questions and answers. Yes, it's a bunch of work for a moderator, but the value to the community would be much greater. Long threads containing tons of hard-to-search information are simply not useful in the context of a forum, and should really be discouraged in my opinion.

gambit37 wrote:The problem is that using a single thread for multiple queries is a spectacularly awful way of asking questions and getting answers. I'm also new to Grimrock modding, I read this whole thread, and the valuable content within it is simply not easy to find, and demands a certain amount of patience which most casual modders simply will not have.

It would have been much better to stick to the tried and tested method of asking one question per thread. This allows people to then easily browse the forum and find relevant information at their leisure, based on the thread's title.

As someone who has moderated another forum for over ten years, I'd recommend that this thread should be broken up into its constituent questions and answers. Yes, it's a bunch of work for a moderator, but the value to the community would be much greater.

I thought the same thing...
97 pages of random questions and answers.
i could ask a question and have it at the last page but then if 3 more people ask questions before mine is answered, mine could get buried.
eve worse would be if someone said "your question was already asked by someone else and answered earlier" and then i'm supposed to read through 97 pages looking for my question?

i'm not criticizing the guys that answered the questions. I was joking when i said it was "simple to them, not so simple to me". I'm sure the answers really are simple compared to some of the scripts
i've seen in other posts

I admit i've been creating a lot of new threads lately, and i'm just glad nobody told me "don't ask that here, post it in the simple questions thread"

THOM wrote:You mean the editor? Did you had a look at file/preferences? You can change the key-commands.

To duplicate an object just use ctrl-c and ctrl-v... The new object will lie over the old one, but it is selected and you can move it by using the arrow-keys...

Thanks, I tried ctrl+D Alt+D Ctrl+Alt+Shift+D before I figured I'd give the obvious a try, I was too immersed in my 3D apps to even consider Ctrl-c/v!

What could cause this?

Isaac wrote:What could cause this?

Maybe the monster is already dead. Try checking isAlive()

Prints true.



** The monsters (visible above), are from spawners. They stand there idle until the pressure plate in front of their cell is activated; it calls the killMonster() function.

Update: Gets weirder... (same error)


This work-around does the job, but I've no idea what causes the error:

Sounds weird. I think the problem occurs when the monster is killed during the pressure plate triggered action. The problem should go away if you send a delayed kill message to the monster.

I'll try it.

This does work.

**Is there a simpler way to send a delayed kill than to spawn a timer connected to a function that calls .monster:die() ?

*** I think there is a clue here as well. I notice that .monster:die() can be called repeatedly, and the monster repeatedly dies ~is that normal?
https://www.dropbox.com/s/v87ag650epi58 ... 2.avi?dl=0
(It's not the timer; this works for the pressure plate as well. In the video, I first have the timer disable itself, then I comment that out, and restart the preview.)