Comments (11)
In this format?
name: Gunner v2 slots: core: class: CoreUnit weapon: class: WeaponUnit select: manual radar: class: RadarPVPUnit select: manual handlers: library: start: lua: |
Hi @Snipey, this format you mentioned is the YAML/JSON which is already generated for copy-paste into the object. I guess you meant something similar to ArchHUD's .conf
files stored for easy apply, those are currently not generated but can be worked out! Let me take a look on what is currently used :)
from du-luac.
@Snipey @Serializer I've done some work on getting proper autoconfig .conf
files working, if you want to try it out, install directly from the branch using: npm i -g git://[email protected]:wolfe-labs/DU-LuaC.git#feature/autoconf
The only changes necessary on project files to support it is adding the select
field under slots
, possible values as far I noticed are manual
and all
:
{
"builds": {
"main": {
"name": "main",
"slots": {
"special": {
"name": "special",
"type": "screen",
"select": "manual"
},
"others": {
"name": "others",
"type": "screen",
"select": "all"
}
}
}
}
}
from du-luac.
That's already in there?
from du-luac.
In this format?
name: Gunner v2
slots:
core:
class: CoreUnit
weapon:
class: WeaponUnit
select: manual
radar:
class: RadarPVPUnit
select: manual
handlers:
library:
start:
lua: |
from du-luac.
Not sure about the format it's in, but for the build targets, it's json that can be copy/pasted I haven't tested wolfe's script for weapons nor radars, I can do it for others, and they are in the list, so I am guessing it works :)
from du-luac.
My test project.json for my accountsSystem, it only has a development target, for build I would minify and not handle errors :)
{ "name": "Yggdrasil-Society.tests", "description": "Tests for libraries/databases and systems developed by Yggdrasil Society", "sourcePath": "src", "outputPath": "out", "libs": [ { "id": "Yggdrasil-Society.libraries", "path": "..\\libraries\\" }, { "id": "Yggdrasil-Society.databases", "path": "..\\databases\\" }, { "id": "Yggdrasil-Society.systems", "path": "..\\systems\\" } ], "targets": [ { "name": "development", "minify": false, "handleErrors": true } ], "builds": { "TestAccounts": { "name": "TestAccounts", "slots": { "ygdsScreen": { "name": "screen", "type": "screen" }, "accountsDB": { "name": "accountsDB", "type": "databank" } } } } }
from du-luac.
Not sure about the format it's in, but for the build targets, it's json that can be copy/pasted I haven't tested wolfe's script for weapons nor radars, I can do it for others, and they are in the list, so I am guessing it works :)
So from what I'm seeing this is not technically an auto configure script just generating the slot names for the board. The autoconf is the right click apply that is on Arch HUD. it allows the naming of classes for the script and auto links them to the control unit.
This just generates json to paste to a unit with all the slots predefined. On a ship you don't know how many of every element you have.
Referring to scripts placed here
C:\ProgramData\Dual Universe\Game\data\lua\autoconf\custom
from du-luac.
It is an autoconfigure json as far as I know, except the links have to be either added in the same order as you do with the tool, or rearrange them in the project.json, or you can use code to link them by class, or by name...Don't know how that works, I am not using those features yet
from du-luac.
Yes I was referring to the .conf files as it is easier to keep those around for control units like RC, Gunner chairs, and command seats. It also is great for auto linking things to the chair.
from du-luac.
@MatheusMK3 I would test it, however I currently have no ship nor flightscript to test it on, I say currently I've only ever owned one x-small core ship :D
from du-luac.
Closing the issue as that should be live by now
from du-luac.
Related Issues (20)
- no such file or directory, open 'XYZ\out\development\main.lua HOT 3
- Production minify created error code HOT 1
- --export lua parameters are removed like all other comments during minify HOT 1
- import github library HOT 2
- Test folder addition HOT 1
- Install on Windows fail HOT 1
- Add support to sumneko's Lua extension HOT 3
- Feature: Add more element types to the linking command HOT 1
- Bug: Strings and comments that contain a `require` statement also triggers parent `require` HOT 1
- Chore: Improve codex generation
- Feature: Being able to compile files into "loaders" which require the actual project file from DU's Lua directory HOT 2
- Build target "env variables" and compiler-level conditionals HOT 2
- Allow passing of build target name to build command
- Feature: Support embedding of compiled Lua files HOT 2
- Add config value to strip comments in non-minified builds
- embedFile(): use same file resolving method as require() HOT 1
- Create improved documentation page
- Investigate "files required in a loop" error happening incorrectly
- Investigate issue with Node.js file move (rename) across different Windows drives
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from du-luac.