Difference between older versions

So I recently got back into toying around with Graal for the fourth (fifth?) time. Mostly to waste time I’ve been working on sort of remaking the Graal Classic single player portion, with a connected quest to find the four graals to open Midas’ realm, yada yada.

This leaves me at a bit of an impasse. I’m not sure which version of Graal to use. I’m currently working with 1.39, as I recall there being a lot of people who say it’s the best as far as offline play goes. However I’m also aware that there was a 1.41 released as well, which I have available to me.

The question is, which IS better? What’s the real difference between them? I know 1.41 has setbody implemented, as well as some other nice things, but I vaguely remember showcharacter NPCs losing the ability to walk in this version or something. I’ve also noticed a few annoying things with the glove sprite not showing up in the GUI or over chests in 1.39, which is bugging the hell out of me, since I can SEE the graphic on sprites.png.

Can anyone who’s familiar with them give me a few pointers? Better yet, can someone recode 2.17 to support offline multiplayer and saving/loading again :D?

someone has already requested a recode of 2.17, sadly we do not have access to the source code…

I would go with 1.41 for custom bodies. (and it supports more complex scripts than 1.39)

The season’s will change, and the sun will rise and fall. There’s nothing you can do about it.

Well, the point wasn’t to host it online. Offer it for download if it’s any good, perhaps, but not actually host it on a server.

So to clarify, there are no scathing game-breaking bugs in 1.41 like I’ve been told?

I miss 1.41, I think layering in showimgs was ‘just’ introduced back, no layer 4 and up though (so no GUIs). No Ganis as well. If you’re just doing offline play, just use the 2.1.7.1 client in offline mode. Online Mode buggers up for everyone the first time they use it.

The reason is, its a different logic.
Colors/Images/Visibility/X/Y/Chat/Params, once an NPC script is run on a player, it will send out changes to these properties out to other players, making it seem as if they’re running the script too.

Scripts will run on every player with one exception, anything requiring a “loop” (while/for/timeout), will cease to function if the player is not considered the “leader” (oldest one in the level) of the level.

timereverywhere; Is a command to allow other players to run their own loops, this is generally fine for most NPCs, but remember, if the NPC contains any of the above “global properties”, other players will be overwriting each other’s properties, causing a “Spazzing NPC”

Showimgs do not carry across to other players via an NPC, they will send to other players if it is a weapon, and the index is over 300.

All non-local positioning is in increments of 0.5, no exceptions.
(And if you think you have an exception [like a gani], I will quickly teach you at what you’re seeing is completely local.)

So, all in all. If you did use 1.41 with out GServers, and if it did happen to use the same protocols. if(created){} will still be bugged. Haha.

beholder…that made my head hurt worse than it already does…

Yeah, but unless I’m missing something, you can’t save in offline mode in 2.171, nor can you have offline multiplayer, which is good for testing things.

Offline multiplayer probably will not help you test things, but yes, its true “saveing/loading” your state is not possible in 2.+

[QUOTE=Nalin;10848]I thought it just prevented timeout from working. I don’t think it interferes with normal loops…[/QUOTE]
All loops cease, if it requires the NPC to loop back into it’s scripting, it stops.

[QUOTE=Nalin;10848]You have that backwards. showimg indexes 0-200 show for everybody. Anything over that only shows locally.[/QUOTE]
And yeah, I had that backwards D:

<<

I think y’all are seriously overestimating my scripting ability.
I’ve played around with 1.41 a bunch, though, and it feels slower to me… Iunno. I might just go back to using 1.39, since there’s really only body support and the red glove icon that I’d miss.