palette.ini

[aubergine]

For some unknown reason I started editing palette.txt in to an .ini file, grouping the various bits in to sections and also adding a [palette] section at the top to define named references for colour codes.

No idea if it's of any use, the way palette.txt is read in to an array of constants seems pretty clean in WZ code so I assume there's not much desire to replace it with a .ini?

Anyway, here's the file for anyone who's curious...

palette.ini

[aubergine]

Per just added moddable construction/demolish beam colours to palette.txt (not in my ini above).

[Originway]

sorry for OT but I have no idea where to put this question and since you are talking about the beam here, can you control how transparent the beam is with JS?
I was thinking that it would look cooler if you show particles in the beam going one way to build and the other way to demolish but I don't see the texture for this and then make it from very transparent to solid color when done.

[aubergine]

Yes, Per recently updated the palette.txt file in Warzone 3.2 to add to new entries to the end (see my link above).

The colour format is R,G,B,A where A is the alpha value: 0 = transparent, ff = opaque.

As for putting particles in the beam, I imagine there's a texture somewhere that could be edited but have so far not encountered it.

[Per]

It is not texture based. Just a coloured triangle with some blending.

I think a conversion to .ini format would be quite natural, especially since it is hard to reorganize as it is, but the right time to do that would probably be when we start changing the GUI, as that would give a lot more info on how/what info should be in that file. So I am not very keen on changing it right now.

[aubergine]

Yup, totally agree about waiting until GUI rework is done before moving to palette.ini -- I guess by that time the GUI will be done in very different way anyway and the concept of a palette file might be outmoded.