Recent Posts

Not by default since the mini-profile HTML option in the settings only affects the inner HTML of the mini-profile, but I can offer a workaround achieved by editing the plugin.

In Plugins > Build > NPC Profiles click on the Components tab and find the JavaScript section.

Scroll to line 279 which should look like this:
$mini_parent.append('<div class="mini-profile is-npc-element o-npc-mini">'+plugin.mini(post_id,npc)+'</div>');
And change it to this:
$mini_parent.append('<div class="mini-profile is-npc-element o-npc-mini o-npc-mini--'+npc+'">'+plugin.mini(post_id,npc)+'</div>');
Then save the changes to the plugin via the Save Changes button in either the right sidebar or the bottom of the page.

This should let you target the NPC mini-profile with CSS based on the username you've given the NPC. So if your NPC's username in the plugin settings is npc1 you can use this CSS rule to target it:
.o-npc-mini--npc1 {
    background-image: url(IMAGE URL HERE);
}

The height of each box is determined by its contents. If you want to change their heights individually you'll have to assign each of them an ID and change their heights using CSS.

I'll update it eventually, but since this one falls under the fun cosmetic umbrella it's lower priority than others. Like I don't think anyone absolutely needs this plugin to keep their forum running the same as it has been when using v6, so I'm not in a hurry to update it compared to something like the NPC Profiles plugin which some forums might lean heavily on.

A few inherent problems with Discord being used for this purpose:

- I can't Google a Discord thread
- I have to be part of the server to begin with in order to search it
- Likewise, even if I'm part of the server the responses to the thread don't currently get indexed

Reddit is thankfully both searchable and indexed by Google, but the branching comment structure adds an extra level of complexity I personally feel I could do without when looking for solutions.

The main complaint I've seen regarding Discord is long-term message storage and searchability, especially when it comes to hobbies or media that only have important information and documentation stored on Discord.

I've personally had an aversion to joining servers for this reason since there's no particularly easy way for it to be organized beyond single-level channels and pinned messages. Usually a forum, wiki, or documentation website gets the job done much better and has much more precise thread or article searches.

Information like that should prioritize accessibility over interaction. I'll gladly join a server if I have further questions, but I don't believe I should have to for the bare minimum.

If you want it to look exactly like that it's going to take a bit more doing, but as far as the contents of each step are concerned it should readily accept HTML without issue. I'm probably not going to revisit any of my plugins to add more customization to them until it's time to update them for v6 since I'd like to rewrite them completely to be up to par with how I prefer to code JS now. But I can at least point you in the right direction.

In Plugins > Build > Virtual Forum Tour this is the line in the JS component that produces the inner HTML of the landmark:

content: '<div class="tour_container">' + x.content + '</div>' + pbp['v_forum_tour'].addNav(),

The HTML for the content is plainly output there by x.content, while after the div element the navigation is output by the value returned by the addNav function which is declared on this line:

addNav: function(){

You can pretty much customize that line and the contents of that function however you please and the plugin should still work as long as any interactive elements retain their classes. Feel free to customize the CSS rules for those classes to your heart's content.