• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Showing developer posts only. Show all posts in this thread.
I'll look into whether I can somehow get a dump of all the portraits. Please don't upload more portraits until I've gotten an answer, since if the answer is "yes", that'll make it more tedious for me to get that set up on the wiki.
 
Think all traits are added and done.
I'll be uploading the proper game-file versions eventually.
Would do it tomorrow, but I'll be busy with a trip to Stockholm. So sometime next week probably.
 
  • 2
Reactions:
Once upon a time I used to pop in the CD, kick off the install and wander to my throne and flip through the manual. I suspect this will be the first major release to not even have a digital one. Any chance they gave some of you major wiki contributors (non-staff) a head start to play the game and the wiki updates are hidden? Off topic cheers to you wiki folk for the work you do.
There will be quite a bit of info carried over from a private wiki on release, yes.
 
  • 6
  • 2
Reactions:
Does pre-ordering from Paradox through the Wiki page rather than Steam help support the WIki?
The source of visitors and purchasers does get tracked, but it doesn't directly impact the wiki, no.

From what I hear, Paradox does get a bigger cut on their own site than on Steam though.
 
Eh, guys I have a problem; my race is both Xenophile AND Militarist. Does this mean I'm hit with a permanent -2.5% Happiness?
According to the Wiki, it says exactly that. I'm just asking here to be sure...
The wiki should be correct. The balance implications of that is a discussion that should be taken elsewhere though.
 
Is someone poking the wiki with a backhoe? Can't get to anything other than the front page as of the t/ds of this post.
As far as I can tell, a cache filled up, causing issues. The size limit has since been increased.
 
  • 2
Reactions:
At the present time, I still get heavy difficulties to browse and edit the wiki.
Still? Load should be normal currently. The CPU load isn't maxxed.

Do note that some pages (E.G., technology) are so long that they lag on the client side while being edited.
It's also relying too much on templates, which can cause similar issues.
 
Also, note that the http://wikis.paradoxplaza.com/ link fails (ERR_TOO_MANY_REDIRECTS).
Known issue. It'll disappear the next time the Apache web server restarts (tomorrow morning).
Already fixed, but restarting the Apache server causes the whole server to be slow for a while, so that's not considered pressing enough to fix immediately.
 
  • 1
Reactions:
@Meneth
I note that the second person is frequently used in this and other wikis although it is not supposed to be in the style guide. Is this based on tutorials often often using the second person to be friendlier, or should that be cleaned up?

Also, should defined technical terms be written in italics, or with initial capitalization? Since a wiki is not linear, a technical term is first defined for the reader wherever the reader happens to first encounter it, so it seems logical to either distinguish such terms that way or simply write them in normal text lower case.

Sometimes the usage is inconsistent on a page or portion, and I think inconsistencies distract from the reading so would like to fix what should indeed be fixed as I come upon them.

Thanks.
The third person is highly preferred, especially outside guide articles.

Technical terms should simply be written as normal text.
 
  • 1
Reactions:
In other performance news, I've been trying out HHVM on another server of mine due to the performance issues users have experienced lately. What it does is compiles PHP to a faster language, which according to WikiMedia (the company behind Wikipedia and MediaWiki, the software my wikis run on) can speed up wikis by a factor of two or so.

The results so far seem pretty clear:
UQDMSHq.png
09Suno4.png


While the other server handles 1500 clients in a minute reasonably well while using HHVM, it can't even handle 600 using PHP (it handled 500 fine in an earlier test, so the barrier seems to be right around that level).
Instead, a queue of requests quickly built up, and the server ran out of memory, promptly crashing the database. The memory issue isn't especially relevant to the Paradox Wikis, as they have far more memory, but the CPU load certainly is.

I also ran a test to see how long it took to render a preview of a large page. That yielded the following results across five tests of each config:
PHP: 2.806s, 2.591s, 2.411s, 3.243s, 2.300s
Average: 2.670s

HHVM: 0.691s, 0.813s, 0.419s, 0.722s, 0.791s
Average: 0.687s

That's a near 4-fold reduction in time on HHVM.

As these results are highly promising, I'll be trying out HHVM in practice on the Paradox Wikis tomorrow morning. If all goes well, this should do a lot to stop the performance issues people have experienced.
 
Last edited:
  • 2
Reactions: