Ganiscript verses Ganis

Tyhm · #1 08-30-2002, 03:59 AM

In ganis, you can easily define sprites and move stuff around.
In ganiscript, you cannot do that, but you can apply color effects to images without knowing what the image filename is beforehand.

Perhaps there needs to be a gani command, UNBUFFERED? Unbuffered ganis would behave exactly as if they'd been ganiscripted - you can COLOREFFECT a sprite that uses HEAD as its source, you can ZOOMEFFECT on ATTR1, you can even COLOREFFECT 0 PARAM1 PARAM2 PARAM3 PARAM4

Man. If I could do that, I'd be unstoppable....

Kaimetsu · #2 08-30-2002, 06:00 AM

Makes sense, I suppose. For my information, is it possible at the moment to completely recreate ganis through ganiscripting? Can they access #8 and #3 and so on?

Python523 · #3 08-30-2002, 06:14 AM

Quote:

Originally posted by Kaimetsu
Makes sense, I suppose. For my information, is it possible at the moment to completely recreate ganis through ganiscripting? Can they access #8 and #3 and so on?

I think gani script can only do 'eye candy', like light effects, showimg, zoom effects, and sounds

Kaimetsu · #4 08-30-2002, 06:18 AM

Quote:

Originally posted by Python523

I think gani script can only do 'eye candy', like light effects, showimg, zoom effects, and sounds

Oh, and of course they can't change the coloration of the bodies according to the #Cx codes.

Tyhm · #5 08-30-2002, 06:35 AM

Other than that, yes. They can do everything. The downside is, if I switch this whole thing over to ganiscript, I have a bunch of ganis of just shadows - which for one, it's a waste, for another I have to give up testplayer. It's an empty gani with a bunch of showimg's (which will have to use layers 0, 1, 2, and 3 until we get floating point layers - or index sorting, I guess, though that way still seems wasteful), so NPCs would have to be right on the shadow to hit it, it seems...unless testplayer cheats, but still, I don't want to have to do a million showimg and changeimgvis' 10 (or 20) times a second just because the buffer optimization requires the RGB values and image to be known regardless of the player's attributes...I'd much rather get an UNBUFFERED command.

Tyhm · #6 08-30-2002, 11:13 AM

*bump* Of course, this may require a few more additions...such as COLOREFFECT accepting strtofloat(#s(yadda)) instead of literal numbers...evaluating the arguments instead of using them directly, for unbuffered ganis.

Kaimetsu · #7 08-30-2002, 02:55 PM

I'm agreeing with you. This sounds useful.

Com013 · #8 08-30-2002, 06:59 PM

I think in one of the G2002 ganis (bigship2 or whatever) I have seen a ganiscript with showimg using a sprite number.
Like: "showimg 1,1,playerx,playery;"
I'm afraid I didn't really understand what you meant, but maybe this could help.

Tyhm · #9 08-31-2002, 01:33 AM

Hm. I was about to suggest that as well, it does make things somewhat easier - but then I have to assemble a showimg gani over the existing gani just to get it to look right, plus I have to do it all with layers 2 and 3, since there are no floating point layers, meaning the player will BE drawoverplayer...

If I had floating point layers and sprite[spritenum].x, sprite[spritenum].y, sprite[spritenum].index for spritenum 0 to spritescount, I could hypothetically do it that way - but I'd still rather have UNBUFFERED ganis. And that's not me yelling, that's me quoting it within the Gani declaration naming convention, all that stuff's all-caps.

Com013 · #10 08-31-2002, 01:46 AM

I can't really follow you...
what's the unbuffered thing supposed to do?

Tyhm · #11 08-31-2002, 03:44 AM

UNBUFFERED would make all ganis behave like ganiscripted blanks. That way you can do COLOREFFECT 20 #e(0,5,ATTR1) #e(5,10,ATTR1) #e(10,15,ATTR1) #e(15,20,ATTR1) instead of having to do COLOREFFECT 20 1 0.75 0.5 0.99 or a bunch of showimg's over your sprites to have a single gani with fully customizable colors

Com013 · #12 08-31-2002, 11:43 PM

Ok, got it. PARAMx and ATTRx don't help?

Python523 · #13 09-01-2002, 12:04 AM

Quote:

Originally posted by Com013
Ok, got it. PARAMx and ATTRx don't help?

he wants to be able to set color effects, zoom effects, etc etc on Params and attributes

Tyhm · #14 09-01-2002, 01:53 AM

PARAMx and ATTRx aren't considered legal values for COLOREFFECT. strtofloat is likewise disregarded - as it stands, it has to be a constant value, not a pointer to a constant value - it has to be 0.875, not strtofloat(#v(0.875))

If we had an UNBUFFERED command, then strtofloat(#P3) would be legit...