SMBX2 (2.0 Beta 3)

[Hoeloe]

I can still ask for the ask for the source code in lunalua

No you can't. 38A has NOTHING to do with LunaLua. LunaLua is 2.0 exclusive. 38A's scripting language is teascript-vb, which is totally unrelated and objectively less powerful than LunaLua. Which itself doesn't even matter much as the 38A features are hardcoded into the engine, rather than being scripted extensions like the ones in 2.0.

38A and 2.0 are NOT the same engine. You can't just splice them together. It doesn't work that way.

[timocomsmbx2345]

I can still ask for the ask for the source code in lunalua

No you can't. 38A has NOTHING to do with LunaLua. LunaLua is 2.0 exclusive. 38A's scripting language is teascript-vb, which is totally unrelated and objectively less powerful than LunaLua. Which itself doesn't even matter much as the 38A features are hardcoded into the engine, rather than being scripted extensions like the ones in 2.0.

38A and 2.0 are NOT the same engine. You can't just splice them together. It doesn't work that way.

Oh. . . . . . . . . . . . . . . .
I wonder why he chose Teascript.

[Hoeloe]

Oh. . . . . . . . . . . . . . . .
I wonder why he chose Teascript.

He didnt. Teascript-vb was created by 38A. It's not a well designed or well constructed language, and there are far fewer learning resources available than Lua, which is a commonly used scripting language. The fact of the matter is that 38A and 2.0 are as related as Skyrim and Mass Effect. Two totally different applications. End of. They HAPPEN to look superficially similar, but 2.0 is based over SMBX 1.3, while 38A is a completely separate program.

[Yoshi021]

I can still ask for the ask for the source code in lunalua

No you can't. 38A has NOTHING to do with LunaLua. LunaLua is 2.0 exclusive. 38A's scripting language is teascript-vb, which is totally unrelated and objectively less powerful than LunaLua. Which itself doesn't even matter much as the 38A features are hardcoded into the engine, rather than being scripted extensions like the ones in 2.0.

38A and 2.0 are NOT the same engine. You can't just splice them together. It doesn't work that way.

Oh. . . . . . . . . . . . . . . .
I wonder why he chose Teascript.

BTW, 1.4 is not made in TeaScript, 1.4 is made using VB. TeaScript is a language he made specifically for 1.4 scripts.

[Hoeloe]

No you can't. 38A has NOTHING to do with LunaLua. LunaLua is 2.0 exclusive. 38A's scripting language is teascript-vb, which is totally unrelated and objectively less powerful than LunaLua. Which itself doesn't even matter much as the 38A features are hardcoded into the engine, rather than being scripted extensions like the ones in 2.0.

38A and 2.0 are NOT the same engine. You can't just splice them together. It doesn't work that way.

Oh. . . . . . . . . . . . . . . .
I wonder why he chose Teascript.

BTW, 1.4 is not made in TeaScript, 1.4 is made using VB. TeaScript is a language he made specifically for 1.4 scripts.

It's also accurate to say that 2.0 is not made in Lua either. 2.0 is based over 1.3, which was made using VB (I don't know why 38A chose such an outmoded language to make his engine in, but oh well). The LunaLua extension was written using C++ and ASM, which hooks in a Lua scripting environment, where most of the new features were added.

[timocomsmbx2345]

No you can't. 38A has NOTHING to do with LunaLua. LunaLua is 2.0 exclusive. 38A's scripting language is teascript-vb, which is totally unrelated and objectively less powerful than LunaLua. Which itself doesn't even matter much as the 38A features are hardcoded into the engine, rather than being scripted extensions like the ones in 2.0.

38A and 2.0 are NOT the same engine. You can't just splice them together. It doesn't work that way.

Oh. . . . . . . . . . . . . . . .
I wonder why he chose Teascript.

BTW, 1.4 is not made in TeaScript, 1.4 is made using VB. TeaScript is a language he made specifically for 1.4 scripts.

let's just move on. . . . Signing up to the 38A forums to convinve mr 38a was a dumb idea.

[Snessy the duck]

Oh. . . . . . . . . . . . . . . .
I wonder why he chose Teascript.

BTW, 1.4 is not made in TeaScript, 1.4 is made using VB. TeaScript is a language he made specifically for 1.4 scripts.

let's just move on. . . . Signing up to the 38A forums to convinve mr 38a was a dumb idea.

I don't think 38A is actully on the forums.

[MarioKirby101]

BTW, 1.4 is not made in TeaScript, 1.4 is made using VB. TeaScript is a language he made specifically for 1.4 scripts.

let's just move on. . . . Signing up to the 38A forums to convinve mr 38a was a dumb idea.

I don't think 38A is actully on the forums.

He is, he just doesn't show up much. He is more active, than, say Redigit (although that's kind of given at this point). He is the one who posts the updates and patches, so that proves that he's there.

Also, I do think that SMBX 1.4.3 has some smart ideas (built in script and npc editing, for example) but it's not in any way perfect, not that I think 2.0 is either.
Each version has it's advantages, I'm just going to leave it at that.

[Hoeloe]

built in script

Built-in script has major disadvantages actually. It's far easier to work with a scripting interface that allows you to move scripts around, and it enables the inclusion of APIs, which is one of LunaLua's biggest strengths as a script interface.

[MarioKirby101]

built in script

Built-in script has major disadvantages actually. It's far easier to work with a scripting interface that allows you to move scripts around, and it enables the inclusion of APIs, which is one of LunaLua's biggest strengths as a script interface.

Sure, each naturally has it's advantages, and you are right that 2.0 does do this. I just find it easier to be able to do this stuff entirely within the program (makes testing them easier, I might add), and if I need a script for more than one level I can always copy-paste it. It's not perfect, but it's not like it is completely terrible. Oh, and some of the things you'd need LunaLua to do in 2.0 are built in to 1.4.3. Just saying.

[Emral]

I just find it easier to be able to do this stuff entirely within the program (makes testing them easier, I might add),

You save your lua script in notepad++, switch over in the smbx tab and hit test. It's as many steps as in 38A except the scripting interface is better.

and if I need a script for more than one level I can always copy-paste it.

Easily done for small stuff but when you need, say, a vector library for several levels you'll have to copy hundreds of lines between every level, cluttering your code and being just a general unnecessary step. (note that vectr is one of the smaller APIs in 2.0 yet would still be annoying to copypaste every time)

Oh, and some of the things you'd need LunaLua to do in 2.0 are built in to 1.4.3. Just saying.

Do note that we don't have the 1.3 source code so we have no choice but to add stuff through LunaLua. We're working on making things more user-friendly in the future, but behind the scenes everything uses LunaLua. Not like it's a bad thing. It also makes them easily accessible if you want to look at their source code, compared to the closed source of 38A.

[MarioKirby101]

I just find it easier to be able to do this stuff entirely within the program (makes testing them easier, I might add),

You save your lua script in notepad++, switch over in the smbx tab and hit test. It's as many steps as in 38A except the scripting interface is better.

and if I need a script for more than one level I can always copy-paste it.

Easily done for small stuff but when you need, say, a vector library for several levels you'll have to copy hundreds of lines between every level, cluttering your code and being just a general unnecessary step. (note that vectr is one of the smaller APIs in 2.0 yet would still be annoying to copypaste every time)

Oh, and some of the things you'd need LunaLua to do in 2.0 are built in to 1.4.3. Just saying.

Do note that we don't have the 1.3 source code so we have no choice but to add stuff through LunaLua. We're working on making things more user-friendly in the future, but behind the scenes everything uses LunaLua. Not like it's a bad thing. It also makes them easily accessible if you want to look at their source code, compared to the closed source of 38A.

1. True. To be completely honest, I've never tried LunaLua anyways.
2. Ctrl+A seems to work pretty well for big chunks of code (at least for TeaScipt), and if you have two windows open you can just switch between them to copy multiple scripts. I will say that it is a bit easier to copy stuff in 2.0's system.
3. I'm fully aware of that, but anything custom-scripted in 1.4.3 uses TeaScipt and you can always open it up in the editor and look at the scripts there. Not that 2.0's system is bad, I'm just saying that that 1.4.3 can do the same thing.

[Emral]

2. If you're doing it right you never have to copy anything except API files themselves (for level- or episode-wide mods).
3. "You can always open it up in the editor" to me sounds like you also have to close it occasionally and, correct me if I'm wrong but, aren't the scripts you view in 38A restricted to the currently opened level? Couple that with a requirement to have the editor in focus and I honestly don't see any benefit to the 38A method.

[MarioKirby101]

2. If you're doing it right you never have to copy anything except API files themselves (for level- or episode-wide mods).
3. "You can always open it up in the editor" to me sounds like you also have to close it occasionally and, correct me if I'm wrong but, aren't the scripts you view in 38A restricted to the currently opened level? Couple that with a requirement to have the editor in focus and I honestly don't see any benefit to the 38A method.

2. That's what I meant.
3. I din't say there was an advantage, I just said you could view custom made scripts.

[Emral]

2. That's what I meant.

I meant the files themselves, not the content. You meant the content.

2. Ctrl+A seems to work pretty well for big chunks of code (at least for TeaScipt), and if you have two windows open you can just switch between them to copy multiple scripts.

[MarioKirby101]

2. That's what I meant.

I meant the files themselves, not the content. You meant the content.

2. Ctrl+A seems to work pretty well for big chunks of code (at least for TeaScipt), and if you have two windows open you can just switch between them to copy multiple scripts.

For the record, I meant the files when I said stuff about 2.0. What I said about switch between two windows was you can have SMBX 1.4.3 opened up twice at the same time, I wasn't refering to PGE and 2.0 there.

Look, do we really have to argue about this one? Whether you're copying the files or the content, it gets the same job done.

[Emral]

Smearing butter on your bread can also be done with a toothpick which will "get the job done". Doesn't make it a good method though. 38A has a policy that requires you to use a toothpick.

[Hoeloe]

Whether you're copying the files or the content, it gets the same job done.

There has been a lot of work put into programming language design over the years, ever since "programming" was first invented. Teascript-vb ignores almost all of these design principles to leave you with a very simplistic language, and one important red flag for programming? Code duplication. A well-made programming language should almost never require you to copy and paste chunks of code, and in 99.9999% of cases, it's substantially better not to. Teascript-vb forces you to.

Here's an example of why.

In 2.0, I made a collision detection library. This is a fairly complex set of mathematical functions that people can make use of without having to understand exactly how they work (one of the main benefits of a library, or API). People could make use of complex collision detection without having to implement it. Now, about 2 months after this was being used in a number of places, I discovered a bug in one of the collision detection algorithms, that would cause it to give the wrong result. The fix was simple, just had to tweak one line of code.

See, the important thing here is that, because that code was never copied anywhere, I could just apply the fix and push out an update. Problem solved.

However, if, every time that code needed to be used, the whole 2000-odd lines were copied directly into the script file, that fix would need to be applied individually for each use of the library, which is just an unreasonable task, especially when the library is shoved together with the rest of your code. Finding the line of code to apply the fix to would be a task in and of itself.

So, in actual fact, no, it does NOT do the same job. It does a superficially similar job, badly.


It's well established that LunaLua is by far the superior scripting interface to Teascript-vb. Yes, 38A has other benefits like more NPCS, but before too long, 2.0 should have that too. There is simply no contest on the scripting interfaces.

[loop]

I think that is enough reasoning to get the point straight. Anyway, progress looks very cool. Especially the Torpedo Teds. I like everything on the table, and I would like to see more. Good luck.

[liamsjunk]

I found a bug:if the tiny girl (sorry idk the characters name) ducks in the kuribo shoe, she gets lodged in the floor XD
seeing all these characters In 2.0 makes me want to make one myself(even though I suck at programming) in fact, I might just do it for fun!
I have made a concept thingy for mayro in smbx 2.0. download here:
http://www.mediafire.com/file/ui4zicdn5 ... _-_Copy.7z