Difference between revisions of "User talk:HikaruFer"

Revision as of 17:00, 13 May 2020

Menu

Jade-Hikaru My Messages My Contributions My Sandbox My Archives Projects (Active) Projects (Finished)

~Hikaru~

Newlines in templates

Hello! Just wanted to give you a small warning that newline symbols at the end (or beginning) of the template are also carried to the pages that use them. It's probably easiest to illustrate on the <noinclude> tags at the end of the templates. While it's pretty to write <noinclude>{{documentation}}</noinclude> on a new line, you also introduce here a new newline just before the noinclude tag. One way to avoid this is to write the starting <noinclude> on the preceding line with some text right before it. Then the newline will be within the noinclude tag and, due to what the tag does, will be present only on the template page where it will do no harm. Alternatively, you can use HTML comments to comment it out (<!--(newline)-->), but it's not very pretty. And of course, you can also put the "<noinclude>{{documentation}}</noinclude>" thing whole on the preceding line and don't worry about any newlines.

You can also come across this issue when you use the #ifeq or similar function. The newlines they may introduce are far trickier to get rid of. Here's one I was fixing recently: Template:CostumeTable/Start. I don't want to discourage you from using these functions, just to keep in mind some of the more subtle effects they may have.

The newlines are an issue when you transclude a template to another page. It hinders formating a bit. Single newline is ignored by the wiki, 2 newlines divide paragraphs and 3 or more add empty lines between the paragraphs. For example, in the News/2020 page, there is one empty line between each entry (2 newlines) and everything works fine. However, if the {{NewsTable}} template would have a newline at the end, then there could be at most 1 newline between the entries (1+1=2), otherwise all of them would break a little (there would be an empty line in the last column, 1+2=3). So the newlines aren't that big of a deal, sometimes it doesn't even have to be a problem, but it's best to avoid sending them to other pages somehow.

Also, for testing templates I sometimes use the Special:Expandtemplates page. I use it mostly as a second editor window for testing the changes without having to modify the original template to see the results and then reverting it back after the test. The additional info there may also be useful sometimes. --Matusm (talk) 21:24, 19 March 2020 (UTC)

Ohhh yeah, do u think it matters in the "fix" i been doing to the bosses page? (like, take Snarbolax for example). Since i did it like this to avoid a visual mess xd, i got lost looking for an specific word being all cramped. I remembered to dont add a newline at the Template:Boss when adding the auto-categories :D, that ended up fine right?. And in no way i find ur msg discouraging, i like to learn~ and as i said i forgot many of the "rules" for the templates so i only edit them if i want to test a fix or add something i think its needed; im guilty of using the "enter" key too much sometimes, its a mania xd i try to just add one between each }} {{ just so i or any other wikieditor dont get lost between each entry (like the news/2020) but when i edit a template i (most of the time) have to test if everything ended up fine, like, when i shorted the APNG's template and earsed a newline and then the boxes glued each other badly so i was like "oh kk that was there for a reason" *manually revert* xd. Next time im gonna try the special template u mention :D.

Feel free to leave me more msgs like this~ HikaruFer (talk) 21:57, 19 March 2020 (UTC)

Yes, it matters in this case. You've introduced a newline at the end of the Boss template, so now the boss pages have one empty line at the beginning. If you edit the Snarbolax page, remove one newline that follows the Boss template and preview it, the empty line at the beginning should disappear. But of course, this should be fixed in the template, not pages. :P

The 2 newlines between news entries are fine, even newlines inside the templates may be fine. The only issue are newlines near beginning and end of the template. I like when the templates are nicely readable, too, but often it's because of weird rules like these that you can't make the templates look very pretty. This one rule specifically is responsible for the long <includeonly><noinclude> chains at the ends. But it's also thanks to this rule that you can put that many enters between entries. :D --Matusm (talk) 23:27, 19 March 2020 (UTC)

OHHH i saw it xdd i didnt notice it, i mean, not that it was due a newline in the template xd. jajaja its funny how that simple "enter" caused that xd. Now it looks prettier :D~. Thx for telling me this way~ if u edit it i wouldnt have understand where and why that newline caused what it did HikaruFer (talk) 23:34, 19 March 2020 (UTC)

No problem. I'm happy it worked out well. :) --Matusm (talk) 00:04, 20 March 2020 (UTC)

Tile minimaps

Hello! I'd like to know if those minimap images you've uploaded are from the game (stored image files) or if you recreated them from scratch with image manipulation software? Example --Spockler (talk) 04:44, 12 May 2020 (GMT+3)

Hello there~ The ones i have done are all with image manipulation software, i take screens in-game of the map, put them together with the software, then i use a selection tool to create all the shapes, and then i add the icons (from the games files, which are the same as the ones here in the wiki). Sadly, the maps seen in-game are generated by the game itself so there aren't images files of them and those had to be done manually :( --HikaruFER 02:08, 12 May 2020 (UTC)

I must point out that these maps are very well done and no doubt recreating them took a lot of time and effort. You even got the collision right with the pixel precision on these maps that are missing some tiles on the edges! I assume you're also using Tudey scene editor for this job, as most of the map can't be captured by the minimap view distance?

Also, I wonder if scene (level) IDs are welcome in this wikipedia as technical trivia? I've studied game levels for quite a while and I could add their IDs to their respective articles, as there are some interesting things going on behind the scenes (pun intended). However I'm not sure if such data is welcome here as Grey Havens might see it as a possible threat to the game (as they sometimes do) even though they aren't monitoring wikipedia (at all). --Spockler (talk) 15:21, 12 May 2020 (GMT+3)

Thanks! Not only me has done some of theses map btw :), i have done a few. I took screens of the big map, the minimap its extremely tiny to make it work, its posible but too bothersome xd, so with a few images-screen i can complete the guide for the whole map.

And, you mean IDs as game files? like "Starlight Cradle's map is generated with this game file"? if its that, im not gonna lie, that would be interesting to check but doesnt have space in the wiki sadly :(, they (Grey Havens) had said they prefer static maps (like the one in Apocrea's mission or Sanctuary) to not be uploaded in the main space of the wiki since they give the static efect in-game for a reason, theres still these images around but not in the main space. You know now that u mention it, Novaster once mentioned that someone wrote a script to make these map images easier but i never got to ask them about it, do u know something about that? --HikaruFER 17:19, 12 May 2020 (UTC)

> And, you mean IDs as game files?

No, as scene file names (e.g. 1 for Haven: Town Square or 393 for Starlight Cradle: Shrine of Slumber IV). I don't want to upload files themselves or maps of procedural levels, but just IDs.

> Novaster once mentioned that someone wrote a script to make these map images easier, do u know something about that?

Unfortunately no, but there's the Super Zoom mod that allows you to move camera to sky-high to get the top-down view. Minimap is aligned with the 3D tilemap, but it's not 1:1 size. It might still be useful, tho. --Spockler (talk) 19:56, 13 May 2020 (GMT+3)