Getting Started With Phun Forum Celebs
If you are looking at Phun Forum Celebs The Rise Of Mysterious Online Personalities for the first time, the setup is more involved than the packaging makes it look. The forum tool itself handles image rendering and threaded discussions fine, but the Celebs module layers a lot of custom templates and asset handling on top of that, and it will break your board if you skip a few steps. I installed it on three different phpBB installations before I stopped having issues, so here is how it actually works. The core idea is that you create fictional celebrity profiles with photos, bios, and interaction mechanics that users can engage with through forum posts and private messages. It is essentially a roleplay and engagement layer built over standard forum software. You will find the download on the Phun Forum marketplace, usually labeled as a plugin or extension depending on your forum version. Grab the latest release and make sure it matches your phpBB version. I wasted an afternoon on a mismatch once because the changelog was vague about which branch the patch applied to. The installation process starts with uploading the files to your forum root. Do not skip the backup step, because the Celebs module overwrites a handful of template files and adds new database tables. If anything goes wrong during activation, you need a clean fallback. After uploading, run the database migration script from the admin control panel. This creates the necessary tables for profiles, followers, and the reputation scoring system. The migration usually takes under a minute on a standard forum size, but it will timeout if your board has over a million posts and you are running an older PHP version. Use the CLI install script in those cases. I keep a copy of the migration SQL in a text file now just to avoid waiting around.
Once the tables are created, go into the admin extension manager and enable the Celebs module. The configuration screen will ask for a few critical settings. Set the default profile visibility to private first. Leaving it public by default is a common mistake that floods your forum with low-effort bot-generated profiles. The module includes a spam filter, but it is not perfect. It catches obvious automated signups, but it misses carefully scripted ones that register with a real email and post a few normal messages before creating a celebrity profile. I learned this when a coordinated group cycled through twelve fake profiles in one week on my test board. The workaround was setting up a manual approval queue for any profile claiming "public figure" status, which I enabled under the moderation settings. It adds a step but it saves you from cleaning up spam manually later. The profile creation wizard is where most new users get confused. The module asks for a type designation first. There are four categories: Real Celebrities, Fictional Characters, Invented Public Figures, and Anonymous Personas. Each category unlocks different template options and moderation rules. Invented Public Figures is the most flexible but also the most likely to be flagged by the anti-spam system. The system cross-references profile names and biographical details against public databases, and if it finds a real match, it auto-restricts the profile. This is actually useful because it prevents accidental impersonation issues, but it also means you cannot create a profile for someone named "Jordan Smith" if there is already a public figure by that name. I ran into that exact problem when trying to set up a minor local celebrity character. The fix was adding a middle initial and a location qualifier to the profile slug, which the database comparison treats as a distinct entity. The follower and interaction system runs on a lightweight reputation engine. When users interact with a celebrity profile through comments, messages, or reactions, the profile gains engagement points. Higher engagement unlocks tiered content and special post features. The engine is configurable, and I recommend turning down the point multiplier if your forum is small. The default settings assume a board with active daily traffic. On a quiet forum, profiles hit the engagement cap within hours and then sit stagnant because there is no mechanism to decay old points. I wrote a simple cron job that reduces engagement by five percent per week for inactive profiles. It keeps the ranking system feeling alive without requiring constant new content. The module does not include this natively, so you need to add it yourself through a custom event listener.
One thing the documentation does not cover well is how the private messaging system integrates with the Celebs profiles. Each celebrity account can have its own inbox settings, auto-reply templates, and response time expectations. Setting these up correctly matters a lot because bad auto-reply configurations will annoy users faster than any other issue. I configured auto-replies to trigger only after a two-hour delay and limited responses to once per day per user. This prevents the module from flooding the board with generated content that looks robotic. The delay also gives moderators time to review flagged messages before they go out. Without that review step, the auto-reply system becomes a liability. Performance is another area that needs attention. The Celebs module adds several database queries per page load, particularly on boards with active celebrity threads. I tracked this on a forum with about fifteen thousand active users and saw page load time increase from 0.8 seconds to roughly 1.4 seconds after installation. Caching helps, but not completely. The engagement calculations run in real time, which means they cannot be fully cached. The best fix I found was enabling query caching on the database side and setting a cache TTL of sixty seconds for the profile lookup queries. This cuts the overhead down significantly without making the rankings feel stale. The module provides a setting for cache duration in the admin panel, but the default is three hundred seconds, which is too long for active boards. Lower it to sixty or even thirty if your forum sees heavy daily traffic. The biggest limitation of this system is its dependency on consistent moderation. Celebrity roleplay forums attract a specific type of content that ranges from harmless fan fiction to copyright disputes and doxxing attempts. The module includes some built-in protections, but they are not enough on their own. You need an active moderation strategy that includes rate limiting on profile creation, keyword filters on biographical content, and a clear reporting workflow for users who want to flag problematic accounts. I set up a Discord webhook that notifies moderators whenever a profile reaches a certain engagement threshold or receives multiple reports in a short window. This is outside the module's native features, but it is easy to implement with a small script and the Phun Forum API.
Get the Full Details
Another edge case worth noting is mobile compatibility. The profile pages use a responsive layout, but the interaction buttons and engagement visualizations are not always optimized for smaller screens. I noticed that the follower count display and reaction buttons became cramped on phones under five inches. The fix is a custom CSS override that adjusts the grid layout for mobile viewports. The module ships with a basic mobile stylesheet, but it is minimal. Adding a few lines of CSS to your custom stylesheet resolves most of the spacing issues. If you are considering alternatives, the main options are building a custom engagement system from scratch or using a simpler forum modification that only handles profiles without the celebrity-specific features. The custom build route is only worthwhile if you need deep integration with existing site features like e-commerce or membership tiers. For most forums, the Celebs module does enough that the development cost is not justified. The module is not a complete solution either. It has gaps in its reporting system, the API documentation is incomplete, and there is no official support channel beyond the Phun Forum community forums. If those limitations are dealbreakers for you, you might be better off waiting for a future update or contributing to the project directly if you have the technical capacity.
