Systems 2.0 Wiki Pages

    Joined
    Jul 30, 2013
    Messages
    195
    Reaction score
    84
    • Legacy Citizen 4
    petlahk when you add the block images for pages you don't have to add the file name of the block image into infobox. That template will automatically use an image that has the same name as the page.

    This is why I try to keep the block names as close to their in-game names as possible.
    Ah. I didn't know that. In any case though, I was having trouble with the templates not having the images showing up in the infoboxes, and going through and adding the image to all the default infoboxes seemed to fix it. It can't hurt, right? *shrugs*.
     

    Crimson-Artist

    Wiki Administrator
    Joined
    Sep 10, 2013
    Messages
    1,667
    Reaction score
    1,641
    • Video Genius
    • Competition Winner - Stations
    • Wiki Contributor Gold
    Ah. I didn't know that. In any case though, I was having trouble with the templates not having the images showing up in the infoboxes, and going through and adding the image to all the default infoboxes seemed to fix it. It can't hurt, right? *shrugs*.
    I dont think it would hurt but its unnecessary to add it when the templates automatically use images with the same name. The template pages themselves will never show the image anyways. The only thing that matters is the actual block page.
     
    Joined
    Jul 30, 2013
    Messages
    195
    Reaction score
    84
    • Legacy Citizen 4
    The template pages themselves will never show the image anyways.
    They do though. In anycase I feel like if it solves a future wiki-editor the bother of adding an image then it can't hurt. If the template page has the image then it's basically impossible for the future templates not to have it so long as you reference the template page.

    Also, I think we need to add a "Feature Is Depricated" or "Feature No Longer Supported" thing. I don't know whether it would be a template or a category though. And I want it to show a big warning at the top of the page. "This feature is depricated. Please see [article] for up to date information."
     

    Crimson-Artist

    Wiki Administrator
    Joined
    Sep 10, 2013
    Messages
    1,667
    Reaction score
    1,641
    • Video Genius
    • Competition Winner - Stations
    • Wiki Contributor Gold
    They do though. In anycase I feel like if it solves a future wiki-editor the bother of adding an image then it can't hurt. If the template page has the image then it's basically impossible for the future templates not to have it so long as you reference the template page.

    Also, I think we need to add a "Feature Is Depricated" or "Feature No Longer Supported" thing. I don't know whether it would be a template or a category though. And I want it to show a big warning at the top of the page. "This feature is depricated. Please see [article] for up to date information."
    there is a template for tagging pages as deprecated. Template:Notig - StarMade Wiki

    Just type "{{notig}}
     
    • Like
    Reactions: MacThule

    Crimson-Artist

    Wiki Administrator
    Joined
    Sep 10, 2013
    Messages
    1,667
    Reaction score
    1,641
    • Video Genius
    • Competition Winner - Stations
    • Wiki Contributor Gold
    See. I'm not quite happy with the default message there. "Power Systems is not in the game." might confuse people. :P

    I'm gonna stick it there for now, and we'll think about a better system when we're not so tired.
    Also I see that you've created a template that indicates if a page is up to date. I would advise against using templates this way. Templates r intended to be used to speed up the process of making pages by automatically adding text in.

    Because they are so cumbersome to edit they are suppose to be used to list data that rarely gets changed but is frequently needed. For instance I made navigators for related blocks in a grouping that goes at the bottom of pages. when I edit the template every pages featuring these navigators will change as well.

    Unless you're planning on making a new template every time a page gets updated I would highly suggest that you simply add the data of the template to each individual page. That way pages can be worked on and updated one at a time without causing so much confusion.
     
    • Like
    Reactions: MacThule
    Joined
    Jul 30, 2013
    Messages
    195
    Reaction score
    84
    • Legacy Citizen 4
    Also I see that you've created a template that indicates if a page is up to date
    Oh shoot, did I? That was accident. I'd delete it if I knew how. I was futzing around trying to figure out how to do what I want to do and not knowing how to do it.

    What I actually want is effectively a warning message with a text box that we can change. I wanted to use the wikipedia warning box, but apparent that isn't a standard function. Like just something like "Legacy Page - You are viewing a Legacy Page. Up to date information can be found here: [Custom text]"

    But again, I don't know whether that's a template, or a category, or what.
     
    • Like
    Reactions: MacThule

    Crimson-Artist

    Wiki Administrator
    Joined
    Sep 10, 2013
    Messages
    1,667
    Reaction score
    1,641
    • Video Genius
    • Competition Winner - Stations
    • Wiki Contributor Gold
    Oh shoot, did I? That was accident. I'd delete it if I knew how. I was futzing around trying to figure out how to do what I want to do and not knowing how to do it.

    What I actually want is effectively a warning message with a text box that we can change. I wanted to use the wikipedia warning box, but apparent that isn't a standard function. Like just something like "Legacy Page - You are viewing a Legacy Page. Up to date information can be found here: [Custom text]"

    But again, I don't know whether that's a template, or a category, or what.
    The rule is if you're gonna have the same text/data pasted on multiple pages and that text/data does not need to be changed frequently then you use a template.

    Sorry but I have to clarify this cuz duke was getting a little mad that ppl were misusing templates just to add text that was only going to be used on one page or were filling them with data that would very likely need to be changed soon.

    You could probably create a better deprecated template but if you intend on adding a link to the updated information I would say you're best bet is to just type out the message on a individual page basis. Or at least thats how I would do it, there might be a way but I cant code.
     
    Joined
    Jul 30, 2013
    Messages
    195
    Reaction score
    84
    • Legacy Citizen 4
    You could probably create a better deprecated template but if you intend on adding a link to the updated information I would say you're best bet is to just type out the message on a individual page basis. Or at least thats how I would do it, there might be a way but I cant code.
    Yeah. I getcha. Templates should mostly be used as static variables that are used in a bunch of different articles. They shouldn't be used for things that change drastically from article to article.

    My issue with the notig template is that it's a little bit *too* static. It's not descrptive enough, and the title doesn't match it's purpose quite well enough. I think a better title would be Legacy System. And, also, I have no Fing clue how to get one to display a tag at the top, which is why I'm digging through wiki articles on markdown text trying to figure out how to make one with basically just *one* variable. It would save the trouble of needing everyone to dig up how to make an info box, but also not be so weirdly static as everything else.
    [doublepost=1525410379,1525409694][/doublepost]Piffle. This is why our personal how to wiki on our wiki page needs to be wiki-edited. Yeah. NOTIG prolly shouldn't exist. Instead there should be a section on ambox...
     
    Joined
    Jul 30, 2013
    Messages
    195
    Reaction score
    84
    • Legacy Citizen 4
    Crimson-Artist So. I woke up this morning and read the changelogs and I don't think it was me that has been creating templates willy-nilly all over the place. 'Cus I see like, 5 new template creations for somewhat questionable things - including version - and they're all under Arkahys.
    [doublepost=1525444871,1525444160][/doublepost]I gotta go to class for the day. I'll get back to editing later. I just added names to a few more infobox templates again.
     
    Joined
    Apr 14, 2018
    Messages
    49
    Reaction score
    57
    I talk about this 2 tags with Crimson before adding them yesterday : {{200.335}} and {{201.x}} .
    I read posts yesterday and wasn't sure you was discussing of these tags, as I ask to crimson before add and use them. Wainting crimson to know What he talk about.
    And others (previewbox,etc...) was just current testing to get "mini infobox" (as you seems to do) that I don't display in public pages.
     
    Last edited:
    • Like
    Reactions: petlahk

    Crimson-Artist

    Wiki Administrator
    Joined
    Sep 10, 2013
    Messages
    1,667
    Reaction score
    1,641
    • Video Genius
    • Competition Winner - Stations
    • Wiki Contributor Gold
    I talk about this 2 tags with Crimson before adding them yesterday : {{200.335}} and {{201.x}} .
    I read posts yesterday and wasn't sure you was discussing of these tags, as I ask to crimson before add and use them. Wainting crimson to know What he talk about.
    And others (previewbox,etc...) was just current testing to get "mini infobox" (as you seems to do) that I don't display in public pages.
    We decided to just add a ambox message at the top of every page to indicate what version the page is up to date to rather than using a template. A template would effect every page that it is on meaning that unless you update every page that has the version template on it at the same time it would cause a lot of confusion.
     
    Joined
    Jul 30, 2013
    Messages
    195
    Reaction score
    84
    • Legacy Citizen 4
    Crimson-Artist MacThule

    I'm finished with:
    System Integrity - StarMade Wiki
    and
    Shield System - StarMade Wiki

    I'm wondering if you could go through them, see if anything needs to be changed, and then add your related section.
    Also, I was sorta wondering if we should stick Category:Tutorials on the reactor page as well. I'm inclined to think so, but I wanted to ask you considering you made the Category:Mechanics.
    [doublepost=1525548047,1525546923][/doublepost]I'm actually doing some edits to the reactors page again. Adding a section on more complex stabilizer placement.
     
    • Like
    Reactions: MacThule
    Joined
    Jan 31, 2015
    Messages
    1,700
    Reaction score
    1,203
    • Thinking Positive
    • Likeable
    I'm in between a dressing my kid up for a parade, then a taekwando tournament, and a 5th of May party later (all today), so it may have to wait a bit! ^^
     
    • Like
    Reactions: petlahk
    Joined
    Jul 30, 2013
    Messages
    195
    Reaction score
    84
    • Legacy Citizen 4
    Alright. I added another section to the Reactors page. It's a bit incomplete because I don't entirely understand how the bonus efficiency numbers work. But I think it's better that it be there as is than not there at all.
    [doublepost=1525555255,1525553477][/doublepost]Crimson-Artist

    So. I was thinking about how this wiki-editing is gonna go in the future. We've done a great job so far getting the power stuff up to date. And soonish I should get working on the Basic Shipbuilding and Advanced Shipbuilding pages. However, once the weapons update hits officially there are gonna be a lot more pages that need a lot of work to be done.

    The issue I see is that I don't know that it makes sense to keep using our system of tagging things legacy pages, ect... There's two issues with it. The first is that it causes bloat, and the second is that they'll still be visible on a google search. New players might perform a google search first, and they shouldn't be getting confused by "Wait, this article is on power systems, and this is on reactors, which do I click?" or more like "Wait, why are there two top results for weapons systems?"

    So. I was talking with JinM and DukeOfRealms on the discord. and the consensus is to pitch it to you.

    However, What I think *might* be useful would be to go with a Dwarf Fortress Wiki style system of having older version articles under a different tab-type-thing at the top.

    DF2014:Whip - Dwarf Fortress Wiki
    Template:ArticleVersion - Dwarf Fortress Wiki

    This would solve the issue of taking up article names and the issue of article names that are too similar.

    But, as JinM pointed out, this would make for a rather tricky systems thing, and the template would be... difficult at best.

    Simpler options would be to merge legacy articles directly under new titles so that the current "Weapons System" page becomes "Legacy Weapons Systems" so we can at least free up the name again. Same for Power Systems, ect...

    The Ambox notice and the bolded "This is outmoded, go here for the up-to-date one" does help. But I like trying to dig into niche issues before they become large problems.

    Edit/Addendum: *Simplest* Would be to delete/overwrite all the legacy pages. But I think that'd be very disrespectful to all the hard work. And some people still stubbornly use the old systems.
     

    Crimson-Artist

    Wiki Administrator
    Joined
    Sep 10, 2013
    Messages
    1,667
    Reaction score
    1,641
    • Video Genius
    • Competition Winner - Stations
    • Wiki Contributor Gold
    Alright. I added another section to the Reactors page. It's a bit incomplete because I don't entirely understand how the bonus efficiency numbers work. But I think it's better that it be there as is than not there at all.
    [doublepost=1525555255,1525553477][/doublepost]Crimson-Artist

    So. I was thinking about how this wiki-editing is gonna go in the future. We've done a great job so far getting the power stuff up to date. And soonish I should get working on the Basic Shipbuilding and Advanced Shipbuilding pages. However, once the weapons update hits officially there are gonna be a lot more pages that need a lot of work to be done.

    The issue I see is that I don't know that it makes sense to keep using our system of tagging things legacy pages, ect... There's two issues with it. The first is that it causes bloat, and the second is that they'll still be visible on a google search. New players might perform a google search first, and they shouldn't be getting confused by "Wait, this article is on power systems, and this is on reactors, which do I click?" or more like "Wait, why are there two top results for weapons systems?"

    So. I was talking with JinM and DukeOfRealms on the discord. and the consensus is to pitch it to you.

    However, What I think *might* be useful would be to go with a Dwarf Fortress Wiki style system of having older version articles under a different tab-type-thing at the top.

    DF2014:Whip - Dwarf Fortress Wiki
    Template:ArticleVersion - Dwarf Fortress Wiki

    This would solve the issue of taking up article names and the issue of article names that are too similar.

    But, as JinM pointed out, this would make for a rather tricky systems thing, and the template would be... difficult at best.

    Simpler options would be to merge legacy articles directly under new titles so that the current "Weapons System" page becomes "Legacy Weapons Systems" so we can at least free up the name again. Same for Power Systems, ect...

    The Ambox notice and the bolded "This is outmoded, go here for the up-to-date one" does help. But I like trying to dig into niche issues before they become large problems.

    Edit/Addendum: *Simplest* Would be to delete/overwrite all the legacy pages. But I think that'd be very disrespectful to all the hard work. And some people still stubbornly use the old systems.
    I would definitely go with the renaming of older pages to add "Legacy" or "Old" as a start. When rails originally came out the old docking page was renamed to add "old" in the title and had a link to the current rail docking page.

    For the time being we can use a normal ambox for outdated pages until we can develop a more dynamic template later. I would rather we have something basic there initially and come back later with something better.
     
    Joined
    Jul 30, 2013
    Messages
    195
    Reaction score
    84
    • Legacy Citizen 4
    Ignore us. We are casually making a collective mess of the reactors page right now.
     
    • Like
    Reactions: MacThule
    Joined
    Apr 14, 2018
    Messages
    49
    Reaction score
    57
    petlahk MacThule
    Actually, as you know, when you query infos from blocks, your get a table, no less, no more. As i explain to Crimson-Artist , it is very restrictive and a new system can allow many implementation by using a database without format (table) and create template on it .
    So, I'am working on a totally new database system today, purpose :
    • replace old {{infobox block}} tag, complex as to use it correcty (if {{infobox block/Reactor Main}} work) you should make something like that :
      {{infobox block
      |type=Reactor Main
      |hp=100
      |Armor=30%
      |etc...}}
    • add a {{tiny table}} to display only block and id. always in a quick simple action
    • allow to make page very dynanic by use {{tag|block|info}} instead of write a value in a page, then if value of block change, all data in pages are update. (armor points, name, HP, etc...)
    So I make some quick templates for the 3 last points (and i will make doc to explain all function i make on it to use it) (todo):
    I.E with "reactor main" and value for "HP"
    {{blockbox|Reactor Main}} to replace {{infobox block|type=Reactor Main|hp=100|Armor=30%|etc...}}
    {{tinyblockbox|Reator Main}} display a little table with only name, icon, ID.
    I have to fine tune to prevent blocks to be displayed more than 50% of page (then making 2 lines, 50% or x%, i will see by results)
    {{ib|Reactor Main|hp}} return hp of block (or type choosed),
    without parameters (type) return name.
    if type is image, can add a number parameters for the size of image. {{ib|Reactor Main|image|150}}
    To be used very often in pages, have to be really short string, then i'm reflect how to make compressed named block call . By id, or a list to choose (very complex this one), or just shortcut names
    {{blocklink|Reactor Main}} (Work in progress) a link of the block page with an icon at size of texte (normal format).
    on this one, i will reduce name of template such as {{bl|block}} as it could/should be used very often as {{ib}}...
    The really goal : I trying to get an info window onmouseover who display the table of block.. :love: that is a good trick !!
    Will have more data for blocks in new database to sorts them and allow to handle more precise:

    • category and subcategory (make an ID list page dynaamic)
    • specific blocks type such as rate of fire, damages, etc.. for weapons. to make table of weapons and sorts them by their power, rate , or what you seek. could be done for light, and sure others...
    • one other powerfull idea I can't still make word on it ... lol.

    and that is the result:
    ADVERTISE : it is a test with 5 blocks in a new database, so you can't actually use tags for others blocks !
    Dbtest - StarMade Wiki

    With this kind on new code, could come many other interesting templates:
    tables of blocks with sortings option by id, armor, hp, etc...
    slideshow of same category blocks (I.E on a chambers page : a slide show of all chambers, instead of display each one)
    etc...
    And more interesting, people can easily make new tempalte by modify mine !!! (as i already comment all to be explicit) and i will make doc files to explain how to.

    But now, have to modify a part of all actual pages of "actual table data block" to "move them" to the new system.
    Even if i make all to make this less painfull, and compatible, that's a work....
    I'am talking with admin (server-side admins) to get scripts on wiki to get it easier (make it in 5 processor work minutes).
    if they can't do anything, i will need help to convert database... hoping not !

    If you have request or ideas of template...
     
    Last edited:
    • Like
    Reactions: MacThule