#Structure of Modding article(s) - RFC
133 messages Β· Page 1 of 1 (latest)
Single page with how to mod, with links to sub pages for having documentation
At least that's my opinion
hmm...
it depends...
i worked with wiki's that had index for modding specific thing
to TL;DR versions https://starsector.wiki.gg/wiki/Intro_to_Modding
The purpose of this tutorial is to create sort of a 'minimum viable product' when it comes to modding -- a simple mod including all of the facets that normally come to mind when one thinks of a Starsector mod. By the end of this tutorial, you will have a mod with a custom ship, weapon, faction, star system, and associated other creations, as wel...
i would say that TL;DR version is good when it comes to basic info (adding few values, changing a picture of something, adding sound to action, or what programs to use [that one is important with links to the sites to get em])
HOWEVER, when it comes to advance stuff, like adding power requirement and uptick or something to do with atmos to brand new items
a kind of index is very valuable to just go and look it up there, what does what
so, yea
Single page with TL;DR and links to get started, with some basic stuff like chaning values or pictures in files.
and then branch off into index with what does what, and more advance examples of coding
Alright, so an overview "[[Help:Modding]]" which serves as an introduction, shows what tools to use, etc; then [[Help:Modding/Tickers]], [[Help:Modding/CondOwners]], [[Help:Modding/Loot]] et cetera, with more detailed info on each topic, examples...
yea, that could work
I dislike having step by step tutorial being focus
Tutorial like that can be added but not as Introduction to modding per say
It would be better to have explained how game reads stuff and how system works
Intro in such way as it is linked is bad for getting knowledge how stuff works, at least for me
This is way better structure in my opinion
@feral frigate @ocean stone
huh
i mean yea, i agree that step by step is not exactly great, but at the same time.
you don't want to discourage lads who usually are going to taste coding for first time.
Just what it requires, what it can have
What else has to be done so it appears in game
What you need to know
Not "follow these steps"
Aigh'. I'll do the layout, you do the rough data, we mash it into palatable reading material together?
You want wiki to be informative
That is goal
Leave step by step tutorials to content creators
those usually leave a lot to be said on forums or random discord questions....
Okay, look at link
Only I guess what is missing is where files for events should be
But other than that? Combine it with https://eu4.paradoxwikis.com/Scripting_Tutorial
And what else you would require?
Ohh right triggers scopes effects
Which all have their own pages
i didn't say to not have its own pages
i said that when someone looks at "into the modding" guide, they usually expect to see what they need to get started
links to programs
links to guides even youtube for sake
or to said indexes
that explains more
It's literally text editor and graphic editor
That's all, you can have that I somewhere put
Oh right it's JSON so validator
But you give that information like that
I think it's better to have mods of better quality due to not most people going doing same steps of same tutorial making OP factions and just slapping them in
If such wiki breeds such mods I would like to avoid that
Even on just probability of this being case
yknow, i start to realize that we probably have different experiences with coding wiki's and help that we manage to get on em
and that might shifted my point of view on it
Most faction mods in starsector are "I made strong faction that have ships soloing multiple bigger ships without issue"
I'm just saying out of being used to eu4 type of wiki when it comes to me doing modding
ay, i usually used SS13 modding coding wiki
I have nothing to complain on that setup
and that was bit more spare on work
but usually in code there were comments left by other coders
explaining what they do and when to use em
gah
yea, looking at EU4 wiki seems a far more cleaner
then most of other wikis i used
It's pretty much done similarly to coding language documentation
Ohh Right caused it's scripting language
In case of ostranauts we just have JSON database structure
Wait, maybe more, I didn't look into game data well enough
I probably shouldn't be here, but can't you do both approaches? Have the main introductory to modding on the main page, and if you are adding links to other pages, have one directed to a step by step example? I have yet to write a mod, have played with a little bit of programming, but am completely enjoying this game and have had thoughts about trying my hand at a mod to see if I can.
Why do ya think you shouldn't be here? The RFCs are for the entire user base to chip in to! π
my point of view on it, was of a guy who wanted to go into modding/coding.
and then was meet with bare wiki, explaining only advance stuff that i didn't know jack shit, jargon that was akin to magic runes, and everyone going with attitude "how do you don't know this, its fucking idiotic easy."
JSON != database.
If I hear you using those words in this combination again, I will smack you.
It's game data
In JSON format
Engine is changing it into objects right?
@ocean stone
"A database is an organized collection of structured information, or data, typically stored electronically in a computer system"
It's about use case
Unless you mean I should in this case write data and base separately
JSON data are... no, is... objects. JavaScript Object Notation. It defines objects in a human- and machine-readable way. With this definition, a book is a form of a database.
Phone book more like would be
And JSON is file format
You can utilize it without JavaScript
Anyhow, I'm sorry, but this is not the place for this discussion. You're welcome to debate the intricacies with me via DM, but this is drifting too off-topic.
Yeah, as I said elsewhere: A brief intro on modding with things like links to VS Code, and the basic quirks of JSONs (The comma versus no comma thing basically), a list of everything believed to be beyond the reach of JSON modding, and then finally the layout of files and what those files do in general, which then links into a detailed page of that filetype with all of the gritty details.
Step by step examples of how to mod specific things is what would get more people into it, its one thing to just read the theory of how, but real examples are far more useful.
Like "this is how you add a ship part", "This is how you get a custom ship to be included in the game" "this is how you make a new piece of equipment" etc.
Step by step is cancer on modding
maybe, but as an example for people to learn by, its very useful.
Doing it in informative style is way better
to you, people learn differently, you shouldnt discount that.
It's Wiki
Not tutorial site
it was a suggestion on how to get people into modding, do whatever you want.
You want to breed modders? Or you want to breed "let's do what this tutorial said"
https://eu4.paradoxwikis.com/Event_modding
(I guess missing from there where events are located, but folder is named events so not big of deal)
Good wiki page about modding
Bad wiki page about modding
@modest pilot
bad to you. I like specific goal oriented learning. It doenst take much to take that information and understand how to change it for other things. but whatever. you clearly arent open for suggestions, so I've made mine, nothing more to say.
How page I linked is bad for goal oriented?
It clearly states what is required in event, and it explains all of those
Effects and triggers and scopes are available on other pages
Scripting language description is also explained on other page
Step by step is useless to person that is already modder, and step by step would probably lead to lower quality of mods, (second one is just assumption based on seeing starsector having step by step introduction, and knowing issues with starsector's mods)
@modest pilot
issues with starsector mods?
there are so many of them ya might as well be trying hard to pin it down at single wiki tutorial
AOTD is one that started small
Nexerelin started small as well
the problem however in starsector modding isn't quality of mods
its how they treat new modders
as they got the same snoppy altitude that shots down anyone trying to understand what means what
but that is no talk for 'ere
And do they have resource on wiki saying what is what and does what?
But hey, they do have step by step tutorial so I guess it's not required right?
(sarcasm, maybe I over did on that)
and you are begin overly ass in this entire converstation
(yea definitely went step too far, I don't know how to rephrase that one)
Okay, I don't know how to rephrase second sentence
But point stands
Goal is to inform what's necessary, what is what, and what does what
So someone knows how to setup item and it's behaviour
According to their idea
yknow, i'm not gonna get onta ya, so i'm done
Okay so you gonna jump on guy that would like to see wiki for modding be done as documentation rather than filled with step by step tutorials being useless for him and plenty of other people
I see stuff like that starsector introduction, I'm not reading that at all
Single page with TL;DR and links to get started, with some basic stuff like chaning values or pictures in files.
and then branch off into index with what does what, and more advance examples of coding
I mean I definitely do see Rells POV there from someone who isn't intimately familiar with the modding. I'm thinking an "Examples" subpage detailing how to do certain small things step-by-step, giving the user the tools to build their own stuff by referring back to the intro page.
But yeah, @spiral raft change your tone, please. I'm already fevery, man. Don't do that.
I literally tried to rephrase that one sentence, i'm unable to do it without having point of argument not changed
Just, going forward, aigh'? β€οΈ
is the community guide in the wiki already? helped me alot, Ive found a few bits but not that much.. there's no good overview page for the modding stuff, had to lookup the Condowners in AllPages π
Not yet. You're welcome to put it there!
We do have [[Getting started]] though
mediawiki tho -.-
Aaaaaaaaaaand?
grabs crowbar
Coordination is already done through Discord, be happy I'm not making y'all use the Talk pages.
Chances are nothing would get looked at anyway lol
haha, suffered many years with that format already... bring back bad memories
Good, then ya know what to do! π
I promise you it ain't too bad. Probably. Also, what'd you work on before?
our customer handbook is a mediawiki so I certainly know it π