My script keeps pullin a Jesus on me. Why?

[Deathbreak]

Ok, so I am working with the Tiberean scripts, the Fishing II one, and the "default font size = " bla bla line of code interfers with my ABS. Well, instead of do the sensible thing and spam you with questions that will NEVER get answered, I did what any noob would do and deleted the code out. Click apply, open the script to make sure the sucker is gone, click "save", then test play. Same problem.
But wait, the error is on the same line!
I went back to the script I had just deleted and the line of code is back. If I modify, click apply, save, and then reboot RMXP I don't have this problem, but that is time consuming.

Anyone know why my code is comming back to life after I delete it?

 

[SephirothSpawn]

Post your code, or more preferably a demo. I can't say anything based off ramble. ^_^

 

[Deathbreak]

The problem isn't code specific, I don't think. It's when I save a change to a script and run the demo, the script reverts back to how it was. Why could this be?

 

[SephirothSpawn]

Without seeing any code or anything, I can't help you. My only guess without the code is that you aren't using it right.

 

[xRythx]

how about buy a copy of rmxp ^__^
illegal version is like 1.01 so if you use 1.01 your obsolete.

 

[Deathbreak]

I do have the legal copy -.-

 

[khmp]

In defense of Deathbreak: Not every script that is found here or other places was created with the legal version. Thus everyone that has the legal version that uses these scripts with the two globals $defaultfontsize and $defaultfontname in it will get an undefined RGSS error. It is only defined in the illegal version, so it's good that the script gave him trouble, it means he has the legal version. So no pointing fingers.

Back to the problem. The way you should have resolved the problem is by defining these globals at the top of the script giving you trouble. Unfortunately now you will have to provide the script in its current state to get the help you need if you still want it.

 

[Deathbreak]

Thank you, I have solved the problem of the code, but I'm still curious as to what I need to do so my code dosen't "come back". I'll make a change, save the program, and then when I come back the change will act like it hasn't occurred, and the modified lines will be back to normal. Is that usual?

 

[khmp]

No I'd say that isn't usual. The only reason I think it wouldn't save is because either you told it not to, or it crashed and didn't have time.

 

[Deathbreak]

I guess I should just be more careful then...
Ty