The Dink Network

Reply to Re: editor_type() - values 2 or 4 nuke attached script?

If you don't have an account, just leave the password field blank.
Username:
Password:
Subject:
Antispam: Enter Dink Smallwood's last name (surname) below.
Formatting: :) :( ;( :P ;) :D >( : :s :O evil cat blood
Bold font Italic font hyperlink Code tags
Message:
 
 
April 25th, 06:57 PM
custom_simon.gif
SimonK
Peasant He/Him Australia
 
Nuked on future screen loads, yeah, thanks, that's what I'm seeing. So it's not just me, phew...

I finally figured out how I got around this 20 years ago, and it wasn't using variables or visions. I had a script attached to another sprite on the map screen, a screen with only 3 sprites, the snow covered tree, the rock and the snow storm. The rock script had a wait(100); and then attached the original tree script to editor sprite number 4, which I figure the game then assigns that number to the tree after it has been given a new life via the
editor_type(&hold, 4)
command.

I broke this by adding two flowers around the tree, in my attempt to provide a hint that this tree held a secret.

Now I'm using global variable and visions - yes I know visions are like your dirty cousin who bathes once a month, but I don't mind them. Then and again, I like riddles... so go figure.

Shame the engine treats editor_type() 2 and 4 this way. For me it would make more sense that the script stayed attached on a reload, otherwise these types are essentially the same as 3 and 5.