Oh, the pain of experiencing problems!!

A new, evil error has crept into my editor and is multiplying. The error first ocurred in my "game" but to pinpoint its curse, I tested it in a smaller test game environment.

I do this:

01. Start with Blank File.
02. Add a room.
03. Name a room
...that's it for Room Properties.

04. Add First Object
05. Name First Object
...here's where the mischievous imp crawls into the code...
06. Within Drop button in Interactions tab, under add a script, I enter a
Print command.
...here's where the devilish dwarf infects...

07. Add Second Object.
08. Name Second Object
09. Within Drop button in Interactions tab, under add a script, the First
Object's Print Command unwantingly appears.
10. I erase First Object's drop-script and enter in Second Object's drop-
script, which I want there.
11. Now, First Object's drop-script shows Second Object's drop-script and
not it's own, which I don't want.
...In otherwords, I can't create new objects with their own drop-scripts.

I searched the code for the simple test in WordPad, but code is right, even if it shows what I don't want to see.

The problem started happening after I right-clicked on an object in my game, clicked copy in the drop-down menu, and pasted a copy of it in the same room; I was making 3 pieces of fruit that share properties. The new, copied object appeared, but after that... destruction.

It's not my programming, obviated by the fact, I reloaded the editor and created the aforementioned simplified test to examine if the error was related to any bugs in my game. But in the simplified test, the same bugs appeared. Did my "copy action" infect the editor somehow? Weird as it may seem?

By the way, the cloning effect only exists in the drop-script and no other property/action/type. Plus, in my game, a whole slew of objects completed before the error appeared became infected with the cloning bug.

Damn dwarf!
What's goin' on?

-W.W.

P.s. I'm using 3.53 on comp w/ no internet conex'n to catch virus.

For some reason QDK fills in your drop script with the last drop script used. But my experience differed from yours on #11 as I was able to edit (or remove and replace) the second script and the changes stuck. In my case the code shown is the code written. I don't think the "copy action" is at fault or that your editor is infected. I think the problem is related to a couple similar bugs I have found in QDK. I also quit QDK and restart it once in a while to clear up these issues. Alternatively, if you just want a print command in the drop script, you can add that above the script area (Drop Details window) and there is no problem.

When I edit drop-script on Second Object the changes stick, but now First Object reflects new changes put on Second Object; a never-ending flip-flop effect. I've started, restarted, etcetera, but that doesn't solve the fact that objects written a month earlier are now screwed with. I understand my Print-option, but my code is becoming more complex command-wise. I've planned a new test: going into WordPad and writing the drop-script cold to see if that stops the issue. Reply back with any new info; it's greatly appreciated along with what you've already stated. I'll let you know the results of my test. Time to test...

Hey Alex, if you read this issue, something to consider solving for a future version. And thanks again. My childhood dream will not be destroyed!

W. Wyzwurd

I seem to remember reporting this bug a while back, when this was still new - I though it had been solved to be honest!
Have you tried copying the objects, and then saveing the game - then re-opening the game and editing the script?
It could be that QDK isn't paste-ing the files correctly, and is still using the old object somehow... This should be solved by saving the to code to file, closing QDK and then re-opening the file..

It really has nothing to do with pasting, I believe. As I stated in my first po.sting: I created two objects using the ADD button; therefore, each one was created separately; without conex'n. Unless my right-click copy-paste procedure stuck into the editor. I did realize that previous rooms, before I noticed the error, don't include 2 or more objects that can be dropped, so it could have been happening already. It's weird though: the autocopy stopped for some time, then restarted.? Then it started autocopying Take-scripts; then that stopped after a few troubles. The auto-swap-copy feature angered me, so I hard-coded a drop-script in WordPad and that stuck fine. My best guess is the troll screw'n with the program is getting more intelligent; although, destructive in its nature. If it bothers me anymore, I'll just smash my computer with a sledgehammer; that should work.

Much love to Alex for creat'n Quest.

Witch W.

Right...

I followed your steps, and it kinda worked until step 10.. When I changed the script in the second object - the first object still contained it's own script..
Not sure if it's because I'm in Linux or something though.
... I'll try and get on my laptop soon and try it out.

... and I have no idea what you mean by all that auto-copy stuff.

Auto-copy; as in "An annoying, unwanted feature that tears up a programmer's ASL script automatically, without instruction, by copying, or cloning, commands into a script-edit-screen in a QDK editor." I think my editor is hinting for me to DIE ROT!

-witch wyzwurd