Dated entries from the live ventures, newest first. Each entry links to the venture brief for the full current snapshot — roadmap, stack and stage.
One line per change, tagged with the venture it belongs to.
The unread badge in the message list always showed zero — only messages received while you had the page open were counted. The count is now stored and returned by the server, so when you open your inbox you see the correct number straight away, without having to wait for new messages to arrive.
The button was present but always failed silently — it tried to start a chat that required a full application, which most people hadn’t submitted yet. The enquiry flow now opens a direct conversation with the rescue without needing an application first. The rescue sees all enquiries for their pets in one shared inbox.
A set of interconnected issues has been resolved: application forms now display all their questions (previously the form was blank); adopters can submit separate applications for different pets without being blocked by an unrelated active application; and rescue staff can open applications, read through the answers, and record a decision. Adoption fees also now display in pounds rather than dollars.
A wiring issue meant these three core account flows were broken in the browser — sign-up went nowhere, verification links didn’t complete, and password reset stalled at the confirmation screen. All three work end to end now.
Applicants were previously showing as “Unknown / No email provided” in the rescue dashboard. A fix to how applicant information is looked up now means rescue staff can see each applicant’s name and email address for any application to their rescue.
The brand colour used for primary action buttons failed the accessibility standard for colour contrast — white text on the original rose tone measured below the required ratio. The colour has been darkened to meet the standard, making buttons more readable for everyone, including users with visual impairments.
A bug meant certain actions — including saving a pet as a favourite and marking messages as read — were silently rejected. These actions now complete as expected.
When a player kills a teammate, the bot sends them a private in-game message reminding them that team killing is against the rules and asking them to apologise in team chat. The warning does not fire for helicopter crashes. Each warning is recorded in the player’s history and the moderation log.
The Season 1 landing page now leads with a larger countdown to the 15 October wipe and presents what’s coming as a card grid rather than a bulleted list, making it easier to scan what will be revealed when the season ends.
Each player can now see a personal slideshow of their Season 1 highlights — a slide-by-slide recap of your stats, faction wins, kill streaks and lowest moments. Numbers count up as each slide loads, with animated backgrounds, confetti on the big moments, and optional music. The full Season 1 server-wide roundup page goes live on 15 October when the season ends and the server wipes.
The longest kill distance now only counts shots from hand-held weapons — a missile locked on from a launcher no longer qualifies. The K/D board now shows the 10-match qualifying threshold, matching what the bot now applies.
The K/D board now requires 10 completed matches to appear — replacing the previous hours-played rule introduced on 7 October. The longest kill stat now only counts hand-held weapons. Bot in-game messages also skip any line used recently, so the same message doesn’t repeat too quickly.
Staff logged in to the admin page stay authenticated for 36 hours, removing the need to re-enter credentials the morning after a late session.
File uploads, invitation links and content management requests now go through stricter validation. Security headers on every API response have been strengthened. Four dependency security advisories patched: image processing, HTML sanitisation, and two infrastructure components.
The bot previously recorded level-score endings as draws. They are now logged as “no result” — which is accurate to how the game handles them. Match history pages and Discord roundup posts reflect the corrected result.
When two teams finish a map with the same score, the result is now shown as “no result” on match pages, the leaderboard and the faction win-rate section. The previous label of “draw” did not match how the game itself records these outcomes.
The staff area is now split into two sections: Moderation and Server settings. The Moderation view shows current alerts and player details side by side, with quick-look cards for each player and one-click buttons to warn, kick or ban without opening a separate form. The “Admin” tab has been renamed to “Bans and VIP” to better reflect what it contains.
An update earlier in the week had made the weekly rotation dropdowns unresponsive. They now work correctly and are styled as standard form controls for easier use. Separately, the Weapon rules tab now lets staff type a weapon name in any case when adding or removing weapons from the rules list.
When a staff member looks at a flagged player and finds nothing to act on, they can mark them as “checked”. That player moves out of the “Worth a look” section for all staff, with the checking member’s name shown. The mark clears at the end of the UTC day.
A new Weapon rules tab on the staff page lets staff pick which weapons trigger an action when a player kills with one: nothing, a private warning, repeated warnings then a kick, or an immediate kick. Every warning or kick is recorded in the player’s history and the moderation log.
Staff can mark any player as private. Everywhere the public can see — the stats site, live match, leaderboards, match summaries, and Discord posts — that player is shown as “[private profile]” with no link to a player page. Staff still see full details; the player’s public page returns a not-found to everyone else.
To appear on the kill/death leaderboard, a player now needs at least 10 hours of play in the last 30 days — including seeding time. The previous qualifier (3 matches) could be met in a brief visit without meaningful participation, which allowed short stays to dominate the top of the board.
The /player staff command now includes a team-kill summary for the current day: how many teammates that player has killed, who those teammates were, any griefing flag, and each incident with weapon, distance and map.
Two minutes after joining for the first time that session, each player receives a private in-game message with the server rules, the Discord link and the website address. Players who rejoin after a map change don’t receive it again.
The bot now reads the ban list every 10 minutes instead of every minute, and checks the map rotation only when the map changes. Kill-feed replies now reach the game as soon as they’re ready, reducing the load on the game server during busy matches.
Low-population Discord alerts between 9 pm and 6 am UK time now post without tagging the seeder role — a quiet server at night is everyone going to bed, not a call to action. Live alerts and the /seednow command still tag the role as normal.
The staff page now tracks every player’s arrivals and departures, keeping a session-by-session history for the last 30 days. Staff can see exactly when a player joined, when they left, and how long they stayed — with their current session shown first.
When a bot command hits a problem, the error message is now only visible to the person who ran it — not the whole channel. “Match over” posts and /lastmatch now link directly to the specific match page on the website.
When the server is online, status posts now show the server ID with instructions for joining directly inside the game: open the game, go to Server Browser, choose Join by ID, and paste the code. Shown on seeding alerts, live alerts, low-population alerts, /seednow, /serverstatus, and the live status message.
The Discord options for switching teams and managing matches now show a coloured dot next to each faction name: blue for Lonestar, green for Manticore, red for Valkyra. Easier to pick the right team at a glance.
Any message the bot sends in game — seeding calls, the 10-minute warning, the halfway update, faction win lines, and more — can now be replaced with staff’s own words from the staff page. The bot’s own messages stay in place for any list staff haven’t changed.
The FAL, AMR 50 sniper rifle, Scout Rifle TD, Bushmaster M17S, 9K333 Verba launcher, Stingray drone launcher, PP-19 Vityaz, MP5, M1911, Desert Eagle, and GGX 18 are now fully identified. Past kills automatically show the correct weapon name in stats and roundups.
End-of-period roundups now have a second section of awards: top three players in each role (assault, marksman, machine gunner, support, demolitions, vehicle crew), plus individual shout-outs for most headshots, longest kill, road kills, melee kills, and more. Mortar kills now count correctly towards support awards.
The longest kill record and leaderboard now only count guns, launchers, and grenades. Mines, emplacements, and vehicles are excluded — an AT mine placed 851 m from where a player was standing was the previous server record.
The staff page now streams every kill in real time and stores each player’s full kill history for the last 30 days. Each player’s headshot rate is compared against what’s typical for the weapons they use, so only statistically unusual days are flagged — snipers are not flagged for sniping.
When a new map rotation is applied, the server now starts from the first map in the list rather than continuing from wherever it was. Switching rotations can no longer accidentally play the same map twice in a row.
When a player’s VIP or reserved slot status is added, changed, or removed via Discord or the staff page, the action is now logged in the moderation history with who made the change and the reason given.
Role changes that grant admin or moderator access can now only be made by super administrators. This closes a gap where any admin-level account could silently elevate another user’s permissions.
When a password is reset by an administrator, every active login for that account is signed out right away. Previously, sessions started before the reset could remain active.
Any content submitted through the platform’s content management tools is now inspected and cleaned at the point it is saved, preventing unwanted or unsafe formatting from ever reaching other users.
gaminginit.com now has a Teams page showing faction win rates across all recorded matches. Each map shows a stacked bar of wins per team, so you can see at a glance which faction dominates where.
The seeding page at gaminginit.com now shows the players who have put in the most seeding time, alongside everyone who has earned a VIP slot through seeding, listed by when they earned it.
The single long home page has been split into individual pages for stats, leaderboard, seeding, teams, and more. A “Play with us” section on the home page gives a quick preview of each, making it easier to find what you’re looking for.
The busiest times chart now uses the median player count for each hour rather than the all-time average, so a single bad day cannot drag the whole picture down. Hours while the server is recovering from a crash are also excluded until normal play resumes.
The bot now checks players’ Steam accounts in the background for signs of suspicious activity. Only the accounts with the clearest warning signs trigger a Discord alert, keeping the signal useful and the noise low. Steam risk is also shown alongside any griefing reports.
Map rotations can be given a name, saved, and then assigned to specific days of the week. A default rotation fills any unscheduled days. Staff manage everything from a Rotations tab with drag-and-drop ordering.
A single command now allows staff to grant a permanent reserved slot with no expiry date. The moderation log on the staff page can also be filtered by action type, so staff can focus on what they’re looking for.
When a staff member bans a player, the bot now keeps removing them from the server until they have fully left, rather than trying once and stopping. The ban command also waits correctly if the player has not fully joined yet, and reports the server’s own error message if something goes wrong.
A timing issue meant matches that ended right at the final moment were sometimes saved without a winner. Results are now recorded correctly. Historical match records with this gap have been fixed automatically.
A new /seednow command lets Discord staff post a seeding call immediately, inviting players to come join and help fill the server. The call is always recorded, even if Discord has a brief outage when it is posted.
While the server is seeding, a reminder now appears inside the game every 5 minutes — not just in Discord. When someone joins during seeding, the welcome message now waits 30 seconds before appearing, giving them a moment to settle in first.
Anyone who has played on the WARDOGS server in the last 90 days now has a public page showing their match history, days played, leaderboard positions, VIP status and seeding progress. Pages are linked from the leaderboard and match summaries. Player identities are kept private — pages never show Steam IDs.
A new “busiest times” view shows which hours of the day the server typically fills up, based on the last 14 days of player counts. The chart adapts to your local time zone so you can plan when to jump in.
A dedicated Discord channel can now show a single message that updates automatically every minute: current state, player count, active map, score, time into the match, and the top three players. If the message is deleted it reappears on the next check; if the server goes quiet for three minutes it shows as offline.
Players who helped rebuild the server after a crash or a brief drop from full were not previously being credited for their seeding time. Seeding now counts whenever the server is rebuilding from low population, whether from empty or from a drop, so everyone who helps bring it back gets recognised.
The public home for the WARDOGS game server launched today. It shows live server stats, a player list, match summaries, 24-hour and 14-day activity charts, and a direct link to the Discord. Each map has its own colour, there’s a leaderboard for top-ranked players, and a call to action for seeder VIPs. The site is built and maintained by ideaSquared.
Discord members with the Staff role can now use a complete set of admin commands without leaving Discord: warn, kick, switch team, ban, unban, set next map, change map, manage VIPs, look up a player, and list available maps. Commands explain clearly if they fail, so staff always know what went wrong.
In-game messages and Discord embeds now reflect the personality of the server. At the halfway point, the bot names the leading faction with a faction-specific joke. Message lines are varied so nothing feels repetitive. Low-population alerts include a 5-minute grace period so brief drops don’t trigger unnecessary pings. Each map now shows its own colour in Discord, making it easy to see at a glance what’s running.
A code defect meant six permission checks — covering admin security settings, data exports, account deletion, and platform-wide pet management — were silently not being applied. They are now enforced correctly. No evidence of exploitation; fixed as part of routine security review.
The platform now supports sending a weekly email to adopters who have opted in to notifications. Each digest will highlight new pets matching their profile and any applications still in progress. The feature is built and ready; it will be switched on once validated.
The same image-link check applied to pet profiles earlier today has been extended to editorial and blog content on the platform. Image links in posts and articles are now checked against a safe-format allowlist before being stored or displayed.
Fields containing personal information — email addresses, phone numbers, names, postal addresses and dates of birth — are now automatically hidden when the platform writes diagnostic logs. This closes a gap where readable personal data could appear in log output.
A bug meant that searching by breed using a term containing certain special characters could return unexpected or overly broad results. Search terms are now handled precisely, so results reflect exactly what was typed.
Links added to a pet’s profile image field are now validated before being stored or displayed. Links using unexpected formats — such as those designed to run code rather than show an image — are rejected at every point they can enter the system. The check is applied both when a rescue saves a pet profile and when the image is rendered in the app.
A gap in the rescue statistics screen meant a staff member at one rescue could, in theory, view the statistics of a different rescue by changing a request identifier. Each rescue can now only see its own data. Platform-wide summary figures are restricted to platform administrators.
Previously, if the platform’s malware scanner was unreachable in a non-production environment, uploaded files could pass through without being scanned. The platform now blocks any upload if the scanner cannot be reached, regardless of environment. No files uploaded to the live platform were ever passed through without scanning.
You can now read the Privacy Policy and Terms of Service from within the Pairflix app without navigating away. Links appear in the app footer. No content has changed — only the location.
When you’re logged out due to inactivity, you’ll now see a straightforward notice and an invitation to sign back in, rather than an unexpected error screen.
Login, two-factor verification, and password resets are now rate-limited to block automated attacks. Accounts that are suspended or banned are immediately signed out. Signing in no longer reveals whether an email address is registered — a correct and incorrect email now behave identically.
Each account on the free plan can now create up to three households. The limit keeps the free-tier pick allowance working as intended. Households you’re a member of but did not create do not count toward the limit.
The “attach file” button in the messaging window was never connected to a working feature — clicking it did nothing. It has been removed to avoid confusion. Chat messaging is unaffected.
One of the cookies your browser uses to protect your account session was not always being sent with the “Secure” flag — the signal that tells browsers to only transmit it over an encrypted connection. In certain server configurations this flag could be absent. It is now set consistently, matching all other session cookies.
Three high-severity security issues found in software components the platform depends on have been resolved. The issues affected email address handling, image file processing, and configuration loading. None exposed user data, and all have been patched as part of routine security maintenance.
The platform now runs automated accessibility tests on every update, keeping the app within reach of anyone who uses a screen reader, keyboard navigation, or other assistive technology. The privacy policy, terms, and cookies notice are now linked directly from within the app — you no longer need to navigate to the main website to find them.
A gap in the admin panel allowed administrators to modify or take action on accounts with a higher level of access — including other administrator accounts. This is now blocked: only a super-administrator can act on elevated accounts. The fix protects the integrity of account management for everyone on the platform.
Rescue staff searching for animals or events by name were occasionally getting incomplete or unexpected results when the name contained punctuation — hyphens, percentage signs, and similar characters. Search now treats these correctly across both animal listings and events.
Three fixes shipped together: links containing hidden characters that could disguise their true destination are now blocked; sensitive authentication details that could have appeared in system logs are now stripped out; and a server redirect that could echo back attacker-supplied input is closed.
A “Download my data” button is now available in your account settings, next to the option to delete your account. Your information arrives as a single file you can save and inspect. The privacy policy has also been updated to accurately list the services used to run the platform.
A behind-the-scenes permissions issue was silently blocking rescue organisations from completing account setup, registering devices for notifications, managing notification preferences, and appearing in pet-matching results. All of these now work as intended. If your rescue organisation encountered unexpected “access denied” errors in any of these areas, they should be resolved.
The platform now rejects any file uploaded to an area that doesn’t explicitly allow that file type. Files outside the expected formats — documents, images, and similar — are blocked before they reach the platform. This closes a gap that existed in the upload handling.
During planned downtime the platform can now display a maintenance notice to anyone who visits, rather than a confusing error. If you try to use the app during a maintenance window, you’ll see a clear message and know when to check back.
A specific type of error from Twitch’s service was causing some channels to fail mid-import with no useful feedback. Twitch syncs now run to completion regardless of the error format returned, and any genuine problems are surfaced clearly in the dashboard.
Accounts with several social platforms connected could occasionally hit a processing limit mid-run, causing content sync to stall silently. The sync process now stays within platform limits at all times, so your content imports correctly no matter how many accounts you have connected.
A gap allowed rescue organisation staff to add or remove documents and leave notes on an adoption application that had not yet been submitted — work that belongs to the adopter alone until they choose to submit. The gap is now closed: only the adopter (and platform administrators) can write to an unsubmitted application.
When a social account fails to fetch new content, the admin dashboard now shows the actual error rather than a bare “Error” label. If the account needs the creator to re-authorise their connection, the dashboard now says “Creator must reconnect” instead of offering a resync button that would just fail again.
Previously the dashboard kept showing setup instructions even after a custom domain had been verified and switched on. The card now shows a direct link to your live site once it’s active, and continues showing the setup instructions only while the domain is still pending.
When someone shares a link to a creator’s CreatrGrid page on social media, the preview card now shows that creator’s name, bio, and profile picture — rather than a generic CreatrGrid placeholder. The page title in the browser tab also updates to the creator’s name as you navigate.
Post thumbnails are no longer hotlinked directly from YouTube, TikTok and other platforms. They are now copied to CreatrGrid’s own storage, so they load faster and won’t disappear if a platform changes its CDN links. Large channels also continue syncing where they left off between runs, rather than restarting from scratch each time.
Public creator pages are now served from the network edge, so repeat visits are significantly faster. Channels with a lot of content now load in batches rather than all at once, with a “Load more” button to keep scrolling.
Active session credentials are now stored in a one-way hashed form — a copy of the database cannot be used to take over an account. Sign-in attempts are also now limited per IP address, on top of the existing per-account lockout, making automated attacks significantly harder.
We found and fixed several inaccuracies in the published privacy policy and cookies notice. The corrections include the full list of data actually collected (more fields than were previously listed), correct cookie lifetimes and names, accurate attribution for our error-monitoring tool, and a clear description of how to request deletion of your personal data. Every claim has been verified against the running platform.
A security update to an underlying platform dependency is in place. No user action is required.
If a new release fails its automated health check immediately after being deployed, the platform now reverts to the last working version automatically — rather than leaving the site in a broken state until a developer manually intervenes. The deploy still fails loudly so the team knows, but the site stays up.
Connect your Twitch channel by entering your channel name. Past broadcasts import automatically, and a “live now” banner appears on your public page while you’re streaming. No login or special access is needed — just your channel name.
TikTok connections, previously paused while we completed platform review, are now fully available. Connect your account from your dashboard and your content will start importing automatically.
Four separate toggles in your Twitch dashboard settings let you control what gets imported: past broadcasts, highlights, clips, and the live banner. Turning a type off removes what was previously imported of that type. Turning everything off is not allowed — use Disconnect for that.
A gap in the platform meant that certain requests could reach account-protected pages without a valid sign-in. Those requests are now always turned away before reaching any content. There is no evidence this gap was exploited; it is closed as a precaution.
After a failed verification link, you can request a new one. Clicking that button was incorrectly sending you to the “Email Verified!” success screen — even though nothing had been verified and the app wasn’t going to navigate anywhere. The page now stays on the right screen and confirms your new email is on its way.
If you tried to sign up with a blank field, or typed something that isn’t a valid email address, the form would silently fail rather than tell you what was wrong. It now checks all fields before submitting and shows you exactly what needs fixing.
When rescue staff or platform administrators added a reply to a support ticket, the request was being sent to a route that doesn’t exist — so the reply was lost without any visible error. Responses now reach the right place and save correctly.
Rescue administrators can configure which staff roles are allowed to view specific fields on adoption applications — for example, an adopter’s address or referees. Changes to those settings are now recorded in the platform’s audit log, so there’s a full history of who changed what and when.
An unsubmitted adoption application — answers, uploaded documents, home-visit notes — could be read by rescue staff before the adopter chose to submit it. Only the adopter themselves can now view their own draft until they decide to send it.
The system that sends notification emails was writing recipient addresses and, in some environments, the one-time links inside password-reset and verification emails to internal system logs. Those are now masked — logs retain enough for troubleshooting without holding any personal data or usable links.
A gap in the bulk account management tool allowed platform administrators to grant staff roles — such as admin or moderator — that they weren’t permitted to assign through the standard route. The same restrictions now apply everywhere: no route can be used to bypass the role-assignment rules.
The previous sign-in pop-up (Google OAuth) has been removed. To link your YouTube channel, enter your channel handle and a YouTube Data API key instead. If you connected via the old method, you’ll need to reconnect using the new flow from your dashboard.
When a rescue invites a new staff member by email, the link contains a secret token. Those tokens were previously stored as plain text — a compromised database backup would hand an attacker ready-to-use links that could add them as staff to any rescue. Tokens are now stored in a one-way hashed form: the original email link still works, but a copy of the database is useless for gaining access.
Enabling, disabling, or regenerating recovery codes for two-factor authentication on a staff account is now recorded in the platform’s tamper-evident audit log. Rescue administrators can see a full, timestamped record of who changed what and when.
Rescue staff could previously move an adopter’s unfinished draft application into the review queue before the adopter had chosen to submit it. This gap is now closed — only the adopter can move their own draft application forward.
A misconfiguration in our automated build meant creatrgrid.com was displaying an error page to all visitors. The site is back to normal — creator pages, the dashboard and all features are working as expected.
Automated bot attempts on login, registration and password-reset forms are now blocked. The check is invisible for most people — only suspicious traffic is ever asked to confirm.
Mobile and web push notifications for application updates, new messages and rescue decisions were being silently dropped in production. They are now delivered as expected — enable them in your browser or device settings if you haven’t already.
Every file uploaded to the platform — pet photos and adoption-application documents — is now automatically checked for malware before it reaches storage. Infected files are rejected with a clear message; safe files upload as normal.
Rescue platform administrators (other than super-admins) were being silently denied access to content management, email template editing, and some chat moderation tools. A missing permissions configuration is now in place, restoring access to all affected areas.
After completing a platform review, YouTube videos now display and sync correctly on creator pages. TikTok is still undergoing a separate review and will follow when cleared.
If you filtered to a specific streaming service (Netflix, Prime, etc.) and your household had watched many recent titles, the pick could fail with no result. It now looks further back to find matching titles.
Visitors can now get one real mood-based pick on the landing page, no account needed. Sign up to save your household, track what you’ve watched together, and get unlimited picks.
Mood-based picks now search across all genres that match the mood, not only titles tagged with every genre at once. The pool of candidates is significantly wider, so you get better matches.
A configuration gap meant rescues could see adopter profiles associated with applications to other organisations. This is now fixed — each rescue sees only the adopters who have applied directly to them.
Searches and browse were previously limited to films only. TV series now appear alongside films throughout the platform.
The platform now captures a broader set of viewing preferences — not just genres, but content ratings, language preferences, release era, and more — so recommendations can reflect what you actually enjoy.
All platform emails — account confirmations, password resets, application updates — now send from a properly verified domain. This significantly reduces the chance of emails landing in spam.
Adopters now have a dedicated privacy settings page where they can review and update their data-sharing preferences at any time.
Each pick card now shows which streaming services carry the title, with a direct link to watch. Availability is region-specific and updated regularly.
Your household now keeps a record of everything you’ve watched together. Rate each title with a thumbs up or down to help future picks get better over time.
Free households get three picks per day. Premium removes the limit and adds features like LLM-assisted re-ranking and multi-region provider data. Existing users are unaffected until the limit window resets.
The app now groups everyone in the same household and picks titles to suit the whole group — taking everyone’s preferences into account, not just the person requesting the pick.
Rescue organisations can now import multiple pet listings at once, rather than entering them one by one. Supported formats include CSV and common rescue management system exports.
Rescue coordinators and adopters can now exchange messages directly within an application. All messages are visible in a shared timeline alongside status updates, home-visit notes, and documents.
Adopters can now attach supporting documents (references, proof of address, vet records) directly to their application. Rescue coordinators can view and download them from the application detail view.
