Prismata Wiki

About your userpage[]

Hey. For some reason, the way your userpage is set up causes a "Template:Gphelp::User:OOeyes" page to show up in Special:WantedPages. Is there a way to fix that? Pjoelj 05:52, 28 February 2015 (UTC)

It looks like it was enough to simply resave the user pages that are transcluding from the help wiki. Probably means the pages were imported before the interwiki link was set up, and the wiki never updated it on its own for some reason and needed a kick to do so. OOeyes (talk) 08:07, 28 February 2015 (UTC)

I believe you can run the update bots? It seems like we're missing several of the new / rebalanced units. If you have a moment to update things we'd appreciate it. Cheers. --NNUMskull (talk) 10:04, 2 April 2015 (UTC)

Oh, for a moment I thought you just mean resave, and I got that started. It's been that kind of week. x_x
I can't run it myself, no, but I'll request a fresh import be done as soon as possible. OOeyes (talk) 21:46, 2 April 2015 (UTC)

Xaetron Card[]

The xaetron card, when viewed on mobile, doesn't seem to have enough information. The card states that xaetron is a 4-health fragile, and that its click makes it lose 7 to produce 5 gauss charges.There is no real mention of healing 4 every turn, or what the xaetron's health starts at. Could you take a look at this? -- pokemonsta433(talk)

The data page was missing the extra information. Maybe it was just out of date. I think the automated imports aren't being run anymore, so it really doesn't hurt to just fix the data pages for missing information like that. (The infoboxes should link the page they're drawing data from.) OOeyes (talk) 19:19, 18 March 2018 (UTC)

Data page script[]

Hi, I'm trying to get some info on the old unit data importer script to maybe try and make a new one.
A developer said: So Gamepedia told us that they can no longer run their script to automatically import our data for the Prismata wiki, which means edits for the new units and changes to existing units have to be done manually
Was the old script created by Gamepedia? Where is the code located at now? Which API endpoints did it use to get its info? Thanks! --Wiwiweb (talk) 21:42, 25 April 2018 (UTC)

Yes, the importer was created internally, and IIRC was built in .Net. Unfortunately, I don't have access to it, and I think the data source was supplied to us by the developers, though I'm not sure if it was any different than the game files. I'll try to get more information, but it's been a while and I'm not entirely sure who to follow up with on this these days, so I can't promise a quick response. OOeyes (talk) 05:50, 26 April 2018 (UTC)
I decided on a whim to skim through the game files, but I didn't see anything there that looked like the kind of unit data we were getting from the developers, so I'd assume it's kept on the servers. So our importer would be useless without the developers supplying the data files. OOeyes (talk) 06:48, 26 April 2018 (UTC)
The developer Elyot said that the Gamepedia wiki script used to use this API endpoint however I can see it's missing half the information, such as the tooltip. So either there used to be a more complete API endpoint, or the Gamepedia script was complex enough that it could generate everything missing. --Wiwiweb (talk) 17:03, 26 April 2018 (UTC)
I don't believe it started out that way, because I remember seeing data sent to us as email attachments after updates. The script may have been adapted later to use the endpoint, but it also uploaded the unit portraits and panels as well, which don't seem to be provided here. I know the importer wasn't sophisticated enough to generate those. OOeyes (talk) 18:59, 26 April 2018 (UTC)

New pages[]

Hi there, as you'll see ex. Scrap and Scrutiny (Expert Challenge) here, I'm adding a few new pages for the tricky campaign challenges, hints, and solutions.

Can you give me your opinion if that's ok like it's there? For the show+ I used wiki markup that's not necessarily typical for Gamepedia

Any other feedback, ideas or heads-up(s) would be appreciated before I go on adding a few more of these potentially frustrating things! Dtean (talk) 17:49, 25 May 2018 (UTC)

The biggest thing I did was to combine the episode lists and the episode pages together. I'm guessing you might have used Wikipedia as an example, but Wikipedia is kinda of a bad example for this due to the difference in scope. With Wikipedia being a general encyclopedia, its pages for the games/movies/shows and so on tend to get crowded, and it makes sense to split off some content (especially since their episode tables can be big on their own). This wiki is entirely about Prismata, and the episode pages aren't likely to get cluttered enough to have any value in moving such short tables to another pages; what it does here is mostly just make navigation more complicated.
I also made some changes to the linked mission page as suggestions. This is a bit nitpicky, but the changes I made are because:
  • Tables shouldn't be used purely for visual layout, but for actual table content. If you have one cell per row, it's usually list content, not table content. (Misuse of tables is sadly very common on wikis, though.)
  • I removed the role="spoiler" because I can't find any sign anything actually supports that ARIA role. It's not documented as standard, and a search didn't turn up any evidence that anything has nonstandard support for it either. So probably best to take it out rather than leave future editors with the impression it actually does something.
  • Leaving more than one blank line between things cause the wiki to insert empty paragraphs. Please don't use <br> just for spacing either.
Otherwise, I think what you're doing is fine. OOeyes (talk) 00:43, 27 May 2018 (UTC)
Thanks a bunch&taking the time! Damn I saw this too late and had uniformly adapted all the mission pages that exist so far the same way. Point by point
  • I tried your <div class="contentbox mw-contentbox ">, but it was slower to load the 'pop-ups', extend the collapsed info that is, than the tables. Tried on 2 deviced on 3 browsers. If there is an alternative for collapsible info that can be adjusted to look neutral or contrasts with the dark background, I'd be all ears (and would grudgingly update all the pages once more).
  • removing spoiler tags everywhere now. ty, had just copycat-ed it from some other wiki project.
  • Yeah, I fought the breaks a lot. Better way to do
    (because with it I don't have to hit return 4 times for a single larger breaks after a section)? --Dtean (talk) 21:06, 30 May 2018 (UTC)
I personally don't recommend leaving big empty spaces between sections at all, with the exception of having something to left or right you need a heading to end up below. In those cases, there's the {{clear}} template. If you really have to space it out for some reason, I'd recommend putting the section between something like <div style="margin-bottom: 5em;"> and </div>, but any way you'd do it, it's pretty inconsistent with usual wiki style. OOeyes (talk) 05:04, 1 June 2018 (UTC)

Broken image from template[]

I don't understand why the Valkyrion page has a broken Barrier panel. If you click Edit Source, then Preview without making any changes, it appears correctly. Any clue? --Wiwiweb (talk) 19:32, 30 May 2018 (UTC)

Weird, I tried sandboxing here . Same behaviour, looks fine in the preview. Why are the data things linked to something? I thought they're taken from the Lunarch blog and/or an Amazon webhosting location (edit: I'm wrong)?!? Don't have a lot of experience, but likely a problem in the data page for the unit(s) Dtean (talk) 20:28, 30 May 2018 (UTC)
The cloudfront thing is just how wiki images are uploaded. See --Wiwiweb (talk) 20:41, 30 May 2018 (UTC)
True, must've mistaken it with another site. Verified others also and they don't work (see the sandbox page, Tarsier instead of barrier doesn't work either. Copied and fiddled the html code to no avail. hmm --Dtean (talk) 20:56, 30 May 2018 (UTC)
It's a bizarre intermittent bug with Cargo, the extension running those templates. We don't know yet what triggers it, but using "Purge" or "Purge cache" in the dropdown menu resolves it when it happens. OOeyes (talk) 21:41, 30 May 2018 (UTC)