User blog comment:Liquoritz/Please help me!/@comment-23204006-20131103002314/@comment-4189499-20131224000951

It is actually all in a horizontal list. All the styling is in place for it to be a horizontal list. It's just that the stupid cache is taking forever to clear so that it recognises the new styling as existing so it can be put on the lists, making them appear horizontal on your screen. This is why I hate using style sheets while still in the middle of working on something. If you want to see what it will look like when the cache clears, copy/paste this: .inline-list { list-style: none !important; margin: 0 !important; } .inline-list li { display: inline; } .inline-list li + li:before { content: '\00a0•\00a0'; } into User:Liquoritz/common.css and then just clear your browser's cache, which can be done by hitting Ctrl+F5 a few times on most browsers until you see the change take effect on the navbox page. That's exactly what's in this wiki's main style sheet and it should be applied by now, but at least this way you can see what it looks like until the main cache clears, at which point you can just delete everything from your common CSS because it will be redundant.

Next point: OK, I think I see where you're getting at now with the expanding and collapsing of the table. (PS, if it's any easier, we can just call it open and closed from now on.) I think I know one way to make the navbox be open on the world which the page is in, but that's a rather long method which will keep having to be updated whenever a new level comes out (if anyone else is reading, I'm thinking of using a #switch based off of the page name, like with Difficulty level). I think I'll go check with the CC forums to see if there's an easier way, or at least if anyone there can give me the JavaScript command and base it off of categories.

It's not to hard to add the show/hide when you are doing it for one whole table. That just requires changing the classes assigned to the table (like in the tutorial I posted earlier). The difficulty comes in trying to change what the show/hide looks like, or when doing it for more than one table (currently your navbox is a whole series of tables, each collapsed separately). What I'm currently using for the show/hide is imported from a script stored on Dev Wiki, or in other words, the code which controls how the show/hide works is actually sitting on another wiki but designed to be used elsewhere such as here (that's the whole point of that wiki), however that means I can't change much about how it works or what the things it puts on the tables such as the show/hide look like. I could kinda do a little bit when using the MediaWiki form of the show/hide (though not much), but that one had delays in opening and closing which you didn't want. So, basically, all that was to say I can't change the font and size of the show/hide buttons. Also, it has nothing to do with parameters because I'm making this thing from scratch instead of trying to make one based on somebody else's template, which is fine for something like Wikipedia where all the styling is already defined, but just completely annoying if you need to modify it outside of the limited parameters they give you, especially if you already know what you're doing with wikitext and CSS.

Header centring: The main problem with centring the headings in the VTE. I can make all the world heading centred easily by merging the cells horizontally, but the levels header would then not align with the rest of them because the center command will make it centre in the available space between the VTE and the right side of the table, rather than the centre of the whole table.

Actually, hold that thought for a moment. I can't believe I didn't think of this earlier. One minute.

Arg, Imamadmad, you idiot! Why didn't you think of that before?! It's so simple! The levels header is completely separate from everything else meaning the three column fix will work for that one, and the rest can just have their cells merged! Ok, Header centring is fixed.

Don't worry if this is all looking terribly complicated now. I was in the exact same place about a year ago. If you want to learn more about coding, go check out the help pages on Community Central for wikitext help and I've found w3schools.com to be a brilliant resource for learning CSS. Just keep trying, or it will just look like a jumbled mass of letters forever!