TechAngel85

Live. There was very little to do in terms of actual Dev. Just to this template. I don't think there is any cleanup to do on this one...or it was never cleaned up because the majority of the inline CSS that was there is still there.

From the Dev Guide: You'll have to ask @z929669 where that bit of info came from.

The files should be in a "grass" folder from doing the precache. That folder goes inside the root of the SKSE folder.

I don't normally recommend users follow our Dev Guides, but in this case you might want to check it out. You'll find our mod instructions in Extenders. The rest of our instructions for generation are in the DynDOLOD section (note that DynDOLOD v3 is required). Before all that, make sure you copied your cache files into the SKSE folder.

Discussion topic: PSArcTool by periander Wiki Link

Discussion topic: MBINCompiler by monkeyman192 Wiki Link

Mjjstral (author of AMUMSS) has already mention the changes look great. "Phantastic job!" was his direct words. Haha! Wbertro (another AMUMSS author) said, "Very nice Guide!" about the NoMansSky v2.0 Guide.

The grid system is meant to be used for overall page layout, not smaller things like this, which are inserted into content. That what Flexboxes are for. Either way, the grid system is still flexboxes, just a different implementation of them. The result would like be the same either way. Play with you'd like. Just be sure you can convert it back, if it doesn't go well. Current implementation is pretty simple, of which I think the grid system would add more to the template (and its transclude size).

Discussion topic: AMUMSS by Mjjstral & Wbertro Wiki Link

This template has been updated I have redesigned this template to be responsive using Flexboxes via Bootstrap. It once also displayed the page title, however, that feature has been deprecated for the PageTitle template. Until all pages are converted to the new style, it retains backwards compatibility to display page titles; however, this feature will be removed in a future update. It still needs some work to display nicer on smaller displays, however, it no longer runs off the screen.

Discussion topic: Template:NMSPage

Can you walk up to a road tile and click on it with More Informative Console installed? That you tell us and you some more useful information. Blended Roads should not be be overwritten, so make sure that's not happening and ensure you have a snow texture installed that has a projectedDiffuse textures in Textures\effects:

This Guide has been updated: Beyond the usual cleanup, the folder structure has been updated throughout the Guide. The following changes are all due to us supporting more than Bethesda games, and to mainly incorporate No Man's Sky into into the Guide: Converted all forward slashes in paths back to backslashes: This was done due to discussions and the fact that some programs require backslashes for paths either due to their programming or root programming language limitations. Added new root folder, "Games", to our folder structure to support the following: Step lacked recommendations for Steam install path. For the sake of consistency across all our guides, Steam is now instructed to be installed within the "Games" folder. Likewise for consistency and organization, the "Modding" folder have been moved inside of the "Games" folder. "Tools" renamed to "Bethesda Tools" This was done due to the fact we are installing tools for more than just Bethesda games and piling all these tools for various games in a single folder can get confusing. Therefore, we're structuring the tools out between the various games. Since most of the Bethesda games use the same tools, we put them all together. MO installation has been moved inside the root "Modding" folder MO is not solely a manager for Bethesda game anymore; it supports many more games now. As such, MO has been moved out of the Bethesda Tool grouping and placed within the Modding folder, as it will be a core program used for all of Step's modding. New folder structure added to support NMS As always, our installation paths are optional, however, keep in mind they are referenced through this and other guides. User who deviate will have to remember to correct the paths for their setups.

You might want to update your links in the opening post.

Is this for Beyond Skyrim? Awe! Nevermind:

This Guide has been updated: Added missing download and installation information for MO2. Added relevant Alerts were added at breakpoints for NMS users.

That one needs to be updated too as the width should be in % for the responsive design. It should only accept a percent too, so that the responsiveness isn't broken. I agree it should use a least one named parameter for the main text (possibly for the header too). I really don't use sideboxes much.

That does work, it's just "text" is sticking with the standard we have from the other templates in use. So text= and 2= would work to fix. Btw, I'm just going off the standards that have been there for years (most likely S4N's original work). If we want to change that, then we just need to come to a consensus.

It'll be a lot to replace up front, but once complete it'll be much more optimized and easier to maintain in the future...assuming we don't let bloat creep back in. Considering this template's high use, I thought it was important to optimize it as much as made sense to reduce its load. Thanks for taking the time!

Yeah, we'll just need to update the keywords on the Site Color Pallet. I, or anyone, can do that, if the keywords are final. I did update them from what I posted here, so look them over. I liked the idea of less maintenance so I removed the add, drop, and update keywords and provided usage scenarios instead for guidance. Removed "important" and opted for "brighter" stead. Did the same for dimmer, which is now "dim" and "darker".

Okay it's on up on Dev. The only things that are broken on those using keywords no longer supported, which is what Replace Text will be used for. I made a few additional changes to the color table and included the edits from the live page. Definitely need to refine Usage in the table as I just quickly put those in. All advanced editing beyond this template is pointed to the Site Color Pallet, so this one is focused down. @Citizens Those that may be reading and keeping up, we apologize that you don't get to see the products "in-the-making" due to us using our development environment. However, we felt we could be more open with our development processes. Therefore, you are all getting a glimpse into our development process in action (our back-and-forth, debating and comprising, testing of several integrations before release, teamwork, etc.) As such, please free to jump in with any comments, feedback, questions, and/or suggestions!

LOL. Updated. Works without needing to use Replace Text. However, anywhere the "fix" is used so that "=" character will display would include "text=". Other than that, there would be only the default, anonymous parameters in use. So DY's solutions works for both, but would require two Replace Text runs for future changes.

Well, I guess we don't need really dropped, add or update.

See update to previous post and reply. RE: Inline Heading Honestly, I rarely do this so you guys can do what makes most sense to you. I exclusively used the wiki markup for headings. I agree the hltx should be used only for emphasis, when needed. The only other one that would need 3 is red. Others I'm fine with 2.

Since "{{{text|{{{2}}}}}}" works, this gives the fix (if needed) while will allowing users to skip the "text=" in most cases, I agree this is the best of both worlds. So if we can agree on that and the keyword reduction is a go, I will go ahead and post my changes to Dev for review. I have everyone ready in Notepad. Just been waiting to nail down the final draft.