Release candidate question???
raze_struck
Member, PRO Posts: 141
If you use a release candidate now, will I be able to transfer my file to a stable build release afterwards? I am a pro member, and in the early stages of developing a long term title, and I want to take advantage of referencing table attributes from either side of a conditional, and all the other goodies of course. Anyway if I open my project in the nightly, and continue it there, can I then re-open it under the new stable that comes out thereafter. Shouldn't be an issue right?
Kind of a dumb question, but I just need to make sure :P
Well I guess by the same logic of being able to open up my project (built on a stable) on a release candidate, it should apply that I could open up a release candidate on a future stable correct?
Comments
I'm going to go ahead and say yes. You'll be fine.
I don't see why they would release a nightly version that does not allow you to continue production of your game in a final release later on. That would be the stupidest thing I've ever heard. So with that being said, I'm going to go with yes.
Yes, you will be able to transfer your Release Candidate project file to the stable 0.11 Creator version when it is released.
My GameSalad Academy Courses! ◦ Check out my quality templates! ◦ Add me on Skype: braydon_sfx
Hey, you again! lol thanks, figured as much :P
Since you want to answer all my questions lol jkin, is it true that you can't save multiple tables at once?
I only started using GameSalad 7 days ago! lol... But, as far as I know, you can make up to 100 tables per project. Not sure about saving multiple tables at once, but if you cannot, just save them one by one!
@razmigma89@gmail.com said:
You'll have to have separate Save Table behaviors for each table in your game that you would wish to save.
My GameSalad Academy Courses! ◦ Check out my quality templates! ◦ Add me on Skype: braydon_sfx
Nice, that's what I figured. Weird I read somewhere you can only save one table at a time? :S
But im assuming;
Save table: game.table1 to key a
and
Save table: game.table2 to key f
Would be cool
Yeah, that's fine...