CSEE Lua Assistant (Copilot GPT)

[Crossroads]

Here's something I am experimenting with at the moment. With the large number of CSEE (CS Event Engine) Lua apis available, wouldn't it benice to have a GPT helping to use them?

This GPT was created on my personal Microsoft Copilot Pro plan. See if you find it helpful. What I have found out so far, is that prompting (asking questions) really matters!

In particular, if you see it answering without first listing V Using: search knowledge uploaded by user for question answering then it is likely slacking off and making stuff up. Ask, ask again, with more detail.

• [CSEE Lua Assistant (Copilot GPT) <= LINK REMOVED FOR NOW; TO BE CONTINUED AT A LATER STAGE

Your feedback appreciated!

[Crossroads]

For instance:

csee1.jpg (109.07 KiB) Viewed 896 times

[Crossroads]

...then

csee2.jpg (112.69 KiB) Viewed 895 times

[Crossroads]

One more...

csee3.jpg (116.19 KiB) Viewed 900 times

[Crossroads]

Next, I need a pair of fresh eyes to read those in detail, wheter true, or whether GPT making things up. At first look it makes sense.

[Jason Petho]

All good until the last question you posed, it was misidentifying the variables.

[Crossroads]

All good until the last question you posed, it was misidentifying the variables.

What I have tried this so far it is better analysing code I have written than making its own code. What I am wondering is that as I and maybe others use this does it get better with its answers?

Init.lua and user.lua together are some 20 000 lines of code, something to chew on for a while maybe. I will try tomorrow with some help analysing lua I am writing.

[Crossroads]

Copilot GPT Builder allows for one and only one document (file) to be uploaded. Previously, I had only uploaded the init.lua file with all the CSEE functions there. This was clearly not working optimally.

I uploaded a file again, this time combining the REFERENCE documentation Berto had put together, and the implementation files as well. Further on, I tagged each section as:

• [CSEE LUA FUNCTIONS - DEFINITIONS] - [/CSEE LUA FUNCTIONS - DEFINITIONS]

• [CSEE LUA FUNCTIONS - EXAMPLES] - [/CSEE LUA FUNCTIONS - EXAMPLES]

• [CSEE LUA FUNCTIONS - IMPLEMENTATIONS] - [/CSEE LUA FUNCTIONS - IMPLEMENTATIONS]

Hopefully this provides for a better user experience. And maybe I and we need to use this GPT for a while to have it up to speed. It certainly needs a nudge or three to spit out the expected answer.

Yet, quite neat to have a chat GPT for CSEE Lua library.

[Jason Petho]

This will be crazy awesome if you can get it to work.

Really!

I'll be all over this if it works!

[Crossroads]

This will be crazy awesome if you can get it to work.

Really!

I'll be all over this if it works!

Well it better work! I am not paying Copilot twenty bucks a month to be a total slacker lol

[Crossroads]

This was all rather interesting, but not worth USD20 per month quite yet, perhaps. I canceled my Copilot Pro test trial. To be continued some other day?

[Jason Petho]

Thank you for trying!

That was most interesting!

[Crossroads]

Not quite ready to give up on a CSEE Lua assistant, so trying this with GitHub Copilot instead. Created a project to contain all the Middle East scenario lua files, then included init.lua and user.lua as well.

GH Copilot should be very familiar with referencing project specific source material, so interested to find out how this will work over the coming days and weeks working with CS Middle East lua files. There're all the CS Vietnam "beyond 1968" scenarios needing CSEE Lua files as well, so make that "over the coming months" instead. Ha.

This is a Middle East sample, sorry about that, but shows the idea.

ghcopilot.jpg (470.59 KiB) Viewed 698 times

[Crossroads]

Meanwhile, MS Copilot Pro and all the support it provides for creating user content specific GPTs, I am not done with you yet.

Maybe, once the coming 1.31 is out, and we are working towards the autumn 1.40 update, there could be a CS Vietnam User Manual GPT available?

"I am about to attack a village hex with a bunker on it. Explain the combat modifiers."

Now that would be neat, too! To be continued.