Talk:Magia☆Report

Note: Please always sign your name when editing talk page by putting four tildes (~~~~) at the end of your comment.

If you know the names of various Magia Report comics on this wiki, drop them in the appropriate galleries. PureChaos (talk) 12:14, 5 June 2023 (UTC)

Alternatively, if I already uploaded the select comic and you feel the original is the better version, delete the file I put and replace it. PureChaos (talk) 12:36, 5 June 2023 (UTC)

Wait, the comics were already uploaded? I can't find anything in that user's logs, plus I got a dupe warning only on S1E46... (deleted file)

Anyhoo. I uploaded all of the MagiRepos, as they are on Danbooru (this is how I automated the character categories too, just adapted their tags). Basically I did it cuz MagiReco had two domains: magireco.com, for the public site, and magi-reco.com, basically as the game's servers if I understood correctly. Both hosted MagiRepo, but at different qualities - magireco.com had them at 720x917 up to S2E273 and at 2550x3625 from onwards, and magi-reco.com had them at 1024x1456 the whole time. Meaning that for a good chunk of its run, the "game file" ver was higher res and thus quality than the public ver. But magi-reco.com is now inactive. Danbooru users archived the magi-reco version for a good chunk of the comics, which is good, because I have no idea where else to find them, and I think we should have the highest res possible. But some pages still ended up with magireco.com links instead... EPF (talk) 18:53, 8 November 2025 (UTC)

As for the titles, they're present in the book release, and only in an img format, which means... Non-automatizable. Which means it's a painnnnnnnn to get those for the wiki. The book release is at 1920x1080 iirc btw, but I'm not sure if we just want whole pages of a de-facto paid version on the wiki, sounds potentially troublesome. EPF (talk) 18:53, 8 November 2025 (UTC)

Displaying stories

A lot of stories from Report and Et Cetera are just comics, meaning that they're better displayed with just images than summaries (depending on how much that is allowed here, because I remember the Exedra transcripts getting shut down). Right now they are either extremely long images, a lot of images making a line or a slideshow gallery. I like the slideshow gallery the most, but its also pretty ugly... the width is uncontrolable, its weirdly spaced, I just don't like it. Is there a way to somehow either change the slideshow mode for galleries (with css), or maybe just make a new gallery mode? Or can someone think of a better way to display these stories. - TheresaFrog421 (talk) 22:26, 17 August 2026 (UTC)

Making a new gallery mode isn't really possible. It might be possible to modify the slideshow mode, but it depends what you want to change, and it could be skin-dependent. Could you explain in great detail what you'd like to be different? ~ Celtic Minstrel (talk) 01:17, 18 August 2026 (UTC)

My main problem is Spacing/Padding/Margins: there's a LOT of unnecessary spacing when slideshow is used, there's extra space above the arrows, between the arrows and images and below the images. That might be enough to redeem the slideshow mode imo BUT its still kinda broken? Like the images being blurry for a second, sometimes the whole thing jumping when you switch images, and I doubt that could even be fixed. - TheresaFrog421 (talk) 09:42, 18 August 2026 (UTC)

Yeah, I don't think you can do anything about the image being blurry for a second – that just means it's loading. Everything else sounds like something that could likely be done with CSS. ~ Celtic Minstrel (talk) 12:39, 18 August 2026 (UTC)

Would it be possible to make a similar template (probably with a module)? This is a simple recreation of what I'm thinking:

<		>
1 / 16

I know that maybe there's no point in even making this if its so similar, but my main point for why maybe this would be better is the page number, it would be counted by the template/module and the first number (apart from just changing when the arrows are clicked) could also be changed by user input, so the user can just choose any page when they want, probably by being able to write it in there. I don't know just how much is possible with modules, but if this is I think we should consider this. - TheresaFrog421 (talk) 13:04, 18 August 2026 (UTC)

Modules don't bring much that's new compared to normal templates; they're mostly just more convenient to work with for complex stuff. Anyway, I threw together some CSS that seems to make the slideshow a tiny bit more compact:

.gallerycarousel .mw-gallery-slideshow-buttons {
  height: 0;
  padding: 0;
  margin: 0;
}
.gallerycarousel .mw-gallery-slideshow-buttons > div > :nth-child(1) {
  float: left;
  margin-top: 10em;
}
.gallerycarousel .mw-gallery-slideshow-buttons > div > :nth-child(2) {
  display: none;
}
.gallerycarousel .mw-gallery-slideshow-buttons > div > :nth-child(3) {
  float: right;
  margin-top: 10em;
  margin-right: auto;
}

It might be possible to get it even better, but I'm not sure. The page number might be doable with some custom JavaScript on MediaWiki:Common.js ~ Celtic Minstrel (talk) 03:04, 19 August 2026 (UTC)

Would the css be applied like <gallery mode='slideshow' class='gallerycarousel'>? My thinking was that the module (or whatever) would recreate the slideshow mode but not outright use it, like the page number would control everything (which image is shown), the arrows would change it and the user could also write it in. Though idk if that's a good idea. - TheresaFrog421 (talk) 03:25, 19 August 2026 (UTC)

No. If you were to put that code in a template (assuming the sanitized CSS engine accepts it), you could include that template with the tag and it would affect all slideshow galleries on that page, without adding any special code around the gallery (an element with the "gallerycarousel" class is automatically generated as part of a slideshow gallery). If you want to be able to have slideshow galleries that use the altered CSS and other slideshow galleries that don't, you would need to add another class above them all. I doubt you can put a class on a <gallery> tag (though you're welcome to try), so most likely you'd surround it with a div like <div class="myclass"><gallery>...</gallery></div> and add .myclass> to the front of each of each of the selectors. In the event that the sanitized CSS engine doesn't accept it, it could still be added to MediaWiki:Common.js (but in that case I would need to do it for you).

It would probably be worth fiddling around with styles live on a page before settling on the details. You can right-click the gallery and "Inspect Element", and that'll allow you to poke around and modify style without even editing (the changes will be reverted if you reload the page). It's how I came up with the above CSS. ~ Celtic Minstrel (talk) 01:04, 20 August 2026 (UTC)

We don't really use slideshow galleries like at all, so I don't think we should bother with trying to make sure that not all galleries on a page will be affected (especially if the only changes are just moving the arrows around and spacing). - TheresaFrog421 (talk) 01:33, 20 August 2026 (UTC)

I made my own css page and can test these easier now. I also decided to try a new type that I found on the internet, where its a list of images, one after the other, that can be scrolled through. I actually really like it as it fixes some of my problems with a slideshow gallery, the images are all loaded at the same time (since they're just hidden by being outside of the box) so there's no awkward loading and jumping when switching images, and clicking the scrollbar allows you to move with arrow keys which is really nice. Now it does come with its own problems obviously... First, on my phone the scrolling goes kinda too fast in my opinion, so unless you do it gently it usually skips a page. Second, there's no arrow buttons, which would be really good, but I have looked and a scrollbar CAN have buttons, but I have no idea how to make them work... First of all, the code is just rejected when I try to add it? Maybe its just wrong, because it always says "Invalid selector list at line ##", this is what I try to add (The ###s are something random):

.Story::-webkit-scrollbar-button {
	display: block;
    background-color: ###;
	height: ###;
	width: ###;
}

.Story::-webkit-scrollbar-button:vertical:decrement:end  {
	display:none;
}

.Story::-webkit-scrollbar-button:vertical:increment:start  {
	display:none;
}

These worked on a different page where I was testing it but just don't here, also these buttons would just be added to the scrollbar itself, but they would look better outside of it like slideshow galleries do it, but that didn't work on that page and I'm not sure if it's possible. - TheresaFrog421 (talk) 11:51, 22 August 2026 (UTC)

You're talking about the Sanitized CSS page type, right? It's possible that the CSS feature you want to use is either too old or deemed as "unsafe" by the sanitizer. It could also be that it's a nonstandard feature (that CSS would not be used in Firefox, for example). ~ Celtic Minstrel (talk) 23:02, 22 August 2026 (UTC)

Yeah I'm pretty sure firefox and edge don't support the arrows... Does that mean I should give up the idea or just that it would need to be put on a not-sanitized css page? Also do you think the css display is better than the slideshow gallery? (Without the arrows) Im kinda conflicted. - TheresaFrog421 (talk) 07:33, 23 August 2026 (UTC)