SpringBoard-ZK replacement candidate

[Dave-tB]

This is just SpringBoard-Core, souped up a bit for ZK. Putting it as a draft pull-request here, because I think that is more meaningful than trying to create something at SpringBoard-ZK, as I have made additions to some files.

Summary:
Metal Spot and Startbox add, edit, importing, exporting, save, load etc.
-Additional states, classes and commands to make this possible as well as some edits to existing scripts.
Also a custom infoPath for ZK, and exporting of heightmaps only.

[gajop]

I haven't had the time to take a detailed look at this yet, need a bit of time due to the size of the PR.

I did notice that the indent/formatting was quite a bit off in some places. Can you run luacheck on this?
luacheck scen_edit triggers libs_sb/utils libs_sb/savetable.lua --enable 1

I also did a quick CI fix yesterday, removing Travis in favor of GitHub actions. Can you merge those changes in to ensure your PR runs on the CI as well?

I'll take a proper look as soon as I have some time!

[Dave-tB]

roger that, will fix in the next few days

[gajop]

A look at some of the features:

Metal spot editing

• Adding a metal spot removes the Add state. It should keep it for consistency with other operations.
• Clicking on a metal spot shouldn't make it draggable, it should just select it.
• Dragging should display it being dragged. (this is something I never did!)
• A selected metal spot should be editable like other objects within the Properties tab
• Mirror X and Z are mutually exclusive but you can check them both in the UI
• Pressing escape closes/hides all the metal spots which feels odd

Btw, here's what I made some time ago: https://www.youtube.com/watch?v=Afav3o8Z5oY&ab_channel=GajoPetrovi%C4%87

• You could select, move, copy, rotate, undo etc. You get all this for free once you implement the object bridge:
• https://github.com/Spring-SpringBoard/SpringBoard-ZK/blob/master/springboard/exts/metal_spots/cmd/mex_bridge.lua
• It also fixes some of the weird behavior you get when you click and drag an object (this should not display the rect select like it's currently doing for metal & startbox)
• (I did rely on ZK to render them, so that's a part that you could use from your implementation)

Start box editing

• Much of the issues are similar to metal spots
• Doesn't seem to integrate with the Teams panel that well. Would like to be able to specify the start position as one of the areas there.

Other

• Not sure what glVolumes or infoPath is doing?

After this my next step will be to take a look a detailed look at the code, but from what I can suggest now is a refactor of managers (mex_manager, startbox_manager) to s11n object bridge.
I'd also display these things all the time, not only when in the specific states (states -> views)

PS: This PR feels a bit large and might take a while to merge. Maybe it would be better to split it into smaller ones?
I definitely think this could be merged in SB-C, simply because most other games do indeed use metal spots. I wonder if it would be compatible with BAR too.
But I definitely want both of these two major features in SB or its family of repos. Quite useful additions.

[Dave-tB]

--Mex and Startbox
I had tried to implement both as s11n, but got some errors I couldn't crack -- I'll give it another go using some of the manager stuff I've already defined. I think that replacing ZK dependencies now should be quite easy, now that I have more of a handle on the code.

X-Mirror and Z-Mirror aren't be mutually exclusive -- although if you click both I suppose it becomes a 180 degree rotation instead. I could add something separately where you can define what kind of symmetry you want, as you would almost always want the same type of symmetry for all the metal spots. The other issues make sense.

--Other
glVolumes just adds drawGroundTriangle in order to display the startbox polygons, and ground lines when making the polygons. infoPath is a replacement for path traversability (unique to ZK) that shows vehicle(green) bots(yellow) and all terrain(red), for me this just makes it a really nice way to view the heightmap and fix any pathing inconsistencies there might be.

Thank you for the detailed reply. I'm sorry I didn't get to the code yet -- I have installed luacheck now and it should work hopefully, and should have time on wednesday/thursday to fix those issues at least. If I can get the s11n stuff working I will split it into multiple PRs as I do so.