Provide a mini papyrus code base sample.

[Scrivener07]

Describe

This is a feature request for a mini papyrus code base sample to be provided. Im writing this up as a feature request because a couple individuals have asked me about this. I already have a sort of testing routine Ive been using with a mini-codebase sample for exactly that. I use it to have a common and consistent code base between version smoke tests. I can polish this code up and figure out the best distribution method later.

Ideas

• Add a VSCodeTestCell for a controlled testing environment in game.
• Add samples for static context scripts (globals).
• Add samples for ObjectReferences and Actors.
• Add samples for Quests.
• Add samples which verify language features are working correctly.

Details

The code base looks something like this at the moment and still needs some polish.

E:\Games\Steam\steamapps\common\Fallout 4\Data
|   VSCode.esp

E:\Games\Steam\steamapps\common\Fallout 4\Data\Scripts\Source\VSCode
|   Build.ppj
|   VSCodeActor.psc
|   VSCodeQuest.psc
|   
\---VSCode
    |   Data.psc
    |   Globals.psc
    |   
    +---Actors
    |       Sample.psc
    |       SampleComplex.psc
    |       
    \---Quests
            Sample.psc
            SampleComplex.psc

[Scrivener07]

VS Code - Papyrus Sample v1.0.0.zip

[Scrivener07]

Version controlling this on its own repository may be a good idea. Id like to get it version controlled in one way or another. Any thoughts on that before I proceed with making a repository for "VS Code - Papyrus Sample"? Even thoughts on minor stuff like the exact naming of the repository.

• papyrus-lang
• papyrus-lang.wiki
• papyrus-debug-server
• papyrus-scripts (?)

[Scrivener07]

https://github.com/Scrivener07/papyrus-script/releases/tag/v1.0.0 Its version controlled starting now. That readme is just so it gets baked into the commit for that release.