Hypnadogic Pup @Fuego@awoo.space

@QuestForTori the script object itself should have a destructor which is named ~script (or whatever the classname is) which calls a function Destroy().

Set a breakpoint on that ~script function and run in debugger. it will be called in a place you dont expect it to be. Then check the stack trace in debugger and it will show you what function caused its destruction.

I expect its changing the script and that change makes a new one and destroys the old and theres an old ref

@QuestForTori can you break on the destructor and check the stack trace? Are script objects like immutable?

@angrboda too real

@angrboda bottle caps??

@Tanuki thank youuuuuuuuu

@Tanuki I added two issues.

Instruction bug which I should probably handle, and the fact that we're slow as snuts which I dont know how to handle.

@mawr *out of

@mawr I dont know what you mean by "never look back", but I'm also fucks to give about version control today ;)

@mawr I mean... SVN is pretty straightforward...

@mawr its about 800 million x more complicated and obnoxious to use than it ever needed to be

Gods I hate git...

@QuestForTori mmmn... that is not a thing I can help debug :(

Good luck!

@QuestForTori whats the game written in?

@Tanuki ready for some NES emulator work? :)

@noxy@kitty.town you find a 12% return, you be sure to let us all know

@ddipaola leaves and rocks and doggos and the sun

@ddipaola machine code is source

There is no such thing as "closed source"