|
The play and reset button are godawful.
There are a certain amount of things that get reset, and some that don't.
To recreate this bug, do the following.
Place a brick in workspace.
Place a script in workspace.
CODE:
game.Workspace.Part:Destroy()
Press Play
Wait a second
Press Reset
Zomg the part is totally gone!
Stupid bug. The play button should create a temporary save, that the reset button reverts to. I don't know what you were smoking when you did it any other way, but it is really upsetting.
That was humor at the end, not hate.
Thanks! |
|
Jtmt88Join Date: 2008-06-07
Post Count: 4346 |
It's not a bug. The method Destroy() clears the brick and it cannot be called back into the game unless recreated by the constructor Instance.new() or inserted with the Basic Objects explorer. |
|
Ravenger7Join Date: 2012-09-11
Post Count: 809 |
I'm thinking about making it save when you hit the play button and reload when you stop. However, it's going to take a few seconds to save and load I think. Is that an issue for anyone? Do you stop and start a lot? I'm looking into ways to make it faster to save but I can't promise anything. |
|
|
The play and reset button have never worked. Why wouldn't you just test in solo... |
|
|
@Ravenger
Yeah, that is what Studio 1.0 used to do, but it made the program hang for a few seconds, even on small places. If you could make it the speed of opening a file (which is fairly fast) minus a bit, then you are winning.
Plus, there is something I posted about scripts not getting reset properly. It doesn't reset any changes to scripts (the code in them, not properties). The issue was fixed where deleted scripts didn't come back, but this isn't.
@buddy
Yes, they did a while back in 1.0. However, now the faster one is less reliable. |
|
|
@Prehistoricman
Studio 1.0 had that issue.
The problem is, I make a lot of machines. They destroy stuff and whatnot. Like my regen pad, it destroys the object until someone regens it for the first time.
I'm definitely okay with it saving. However, make it do a TEMPORARY save, not a file save. I use the play button to modify LOADS, and see if a fix works. If not, I scrap it.
So like visits saving, the play button could make temporary saves for sure. Beats losing work! |
|
|
'Studio 1.0 had that issue.'
Only recently. They broke it very close to the release of Studio 2013. |
|
Jtmt88Join Date: 2008-06-07
Post Count: 4346 |
Next time, use Remove() if you are going to press play. I know, I know, "deprecated", blah blah blah, but it allows the part to be called back into the game. Or you can just use nil. |
|
WhosoeverJoin Date: 2012-02-24
Post Count: 7660 |
Yeah. |
|
|
Rikyro, for someone like you, it's pretty sad to see you rage
Seriousy, get over it. The people who make it the farthest are the people who use studio 2013 to it's advantage. And that I do.
Get over all this, it's your computer causing most of these issues, because Studio 2013 is great for me. |
|
|
^
Two things:
What he did is not a fault of his computer.
This is a real bug.
What he did is fully reproducible and if you can't be bothered to test this to insult somebody for being stupid, then you are much more stupid than him. Perhaps his other threads are dim-minded. In that case, flame on those ones. This is a legit bug, not a computer error. |
|
|
My apologies, this one IS a real bug. I clicked the wrong one. The last one he posted, was not a real bug, but just computer issue about crashes.
Number of crashes RS 2013 has had for me: x1
"And know that I am with you always; yes, to the end of time." --Jesus Christ |
|