⭐ Single Video Package Perfect for announcements, updates, showcases, or promotional content. Includes: - 1 professionally edited video - Custom intro/outro - Background music & sound design - On‑screen text, callouts, and branding - Thumbnail included - SEO‑optimized title + description Optional Upgrades: - Additional thumbnails - Short‑form versions (TikTok / Reels / Shorts) - AI or provided voiceover - Scriptwriting support --- 📚 Series Packages 🎞️ Mini‑Series (3–5 Videos) Ideal for tutorials, devlogs, event coverage, or multi‑part storytelling. Includes: - Consistent branding across all episodes - Episode‑specific thumbnails - Series intro card - Playlist setup - Priority turnaround Upgrade Options: - Expand to 6–10 episodes - Add a recap video - Shorts for each episode - Community poll integration (YouTube or Discord) --- 🎬 Full Series (10+ Videos) For long‑term creators, servers, or brands wanting ongoing content. Includes: - Full content strategy planning - Episode scripts or outlines - Custom motion graphics - Series‑wide branding pack - Monthly analytics report Upgrade Options: - Livestream overlays + assets - Cross‑platform posting (YouTube + TikTok + Discord) - Highlight reels every 5 episodes - Community engagement package (polls, comments, announcements) --- 🔄 Per‑Update Video Add‑On Perfect for game servers, RSPS, SaaS platforms, or any project with frequent updates. Includes: - 1 video per update patch - Update‑focused scriptwriting - Before/after comparisons - Feature highlights - Thumbnail included Upgrade Options: - Developer commentary - Cinematic trailer‑style version - Discord announcement copy - Short‑form teaser for social media --- 🧩 Bundle Add‑Ons (Available for ANY Package) 🎨 Branding Add‑Ons - Custom thumbnails (bulk pricing available) - Logo animation - Lower‑thirds + motion graphics - Stream overlays (OBS / YouTube Live) 🔊 Audio Add‑Ons - AI voiceover - Provided professional voiceover - Custom SFX pack 📢 Marketing Add‑Ons - Discord announcement formatting - Social media teaser clips - YouTube tags + SEO optimization - Community engagement prompts --------------------------------------------------------------------------------- Interested? Reply here DM me here, or contact me on discord: broduer

Welcome to RuneTopic The Official RSPS Development, Discussion, & Toplist Community RuneTopic was built with one purpose: to give the RSPS community a modern, organized, and professional platform where developers, creators, server owners, and enthusiasts can grow together. This forum represents a complete step forward for the scene — free from outdated systems, neglected moderation, and cluttered interfaces. Whether you're here to share your work, learn something new, build a server, contribute resources, or simply be a part of something evolving: RuneTopic is your home. Our Mission RuneTopic exists to support a thriving RSPS ecosystem. We stand for: Transparency – A community built on clear rules, fair moderation, and honest representation. Growth – Tools, resources, and systems designed to help servers and developers flourish. Innovation – Modern standards, modern technology, and features aligned with today's RSPS expectations. Collaboration – Encouraging knowledge-sharing, open development, and meaningful contributions. Safety – A strict stance against malicious content, scams, and harmful practices. Opportunity – A place where creators can showcase work, find clients, or discover new projects. We are committed to providing a platform that respects both new developers and experienced veterans equally. What RuneTopic Provides RuneTopic offers the foundational systems the RSPS community has needed for years — all in one place: A clean, modern RSPS forum built for clarity and long-term growth. A powerful toplist with fair ranking, anti-abuse logic, and transparent performance metrics. Development categories for source releases, tutorials, tools, snippets, and research. Resource-sharing freedom without hostile restrictions on posting code, bases, or utilities. A safe service marketplace for designers, developers, editors, managers, and creatives. Community support areas for troubleshooting, help, feedback, or general discussion. Consistent updates as RuneTopic evolves with the community’s needs. What We Stand For RuneTopic is built on values often missing in past RSPS platforms: Professionalism – No drama, no favoritism, no nonsense. Fair Play – Ranking systems cannot be bought or manipulated. Respect for Developers – Sharing is encouraged, not punished. Respect for Creativity – Every contribution, large or small, matters. Community Over Ego – RuneTopic belongs to everyone. Our rules and structure exist to create a safer, smarter, and more collaborative environment. The RuneTopic Toplist The toplist is designed to be fair, accurate, and modern. Unlike outdated platforms, our ranking system: focuses on verified votes via callback systems, uses time-weighted scoring to reward active communities, actively filters bots, duplicate votes, and abuse attempts, ensures server owners cannot buy their way to higher positions, offers upcoming analytics to understand player engagement. RuneTopic aims to restore trust in RSPS toplists by making ranking transparent, consistent, and fair. Who RuneTopic Is For RuneTopic is designed for everyone involved in RSPS: Server Owners looking to advertise fairly and track performance. Developers wanting a home for snippets, sources, tutorials, and collaboration. Designers & Creators building UI, GFX, branding, trailers, and media. New Developers trying to learn the RSPS ecosystem. Veterans with years of knowledge to share. Players discovering servers based on real performance. The Future of RuneTopic RuneTopic will continue to expand, with features planned including: Detailed server analytics dashboards Developer reputation systems Safer marketplace protections Profile badges for contributions and expertise Advanced listing customization Discord-to-Forum integrations Content libraries and resource tagging RuneTopic is not a static forum — it’s a growing platform built to evolve with the RSPS scene. Thank You for Joining RuneTopic We are proud to welcome you to a community that values honesty, innovation, and opportunity. RuneTopic is built for all of us — and together, we will shape the next generation of RSPS development. This is RuneTopic. This is the new standard. This is the future of RSPS.

RSPS Vote Callback Setup Guide Super Detailed – Database Driven – RSPS & RuneTopic Friendly What This Guide Covers This guide will walk you through every step of setting up a vote callback system for your RSPS, using a database-driven method. There is enough detail here that you can follow it even if you have never set up a callback before. By the end, you will have: A MySQL table that stores votes. A PHP callback script that your toplist calls when a player votes. A clear understanding of how to hook that table into your RSPS claim system (claimvote command, login check, etc). Testing steps and troubleshooting tips, so you can confirm everything works. This is designed to work nicely alongside your RuneTopic setup or other RSPS tools. Step 0 – Requirements Before you start, make sure you have: Web hosting with PHP and MySQL (this can be the same host as your website). Access to phpMyAdmin or another MySQL client. Your RSPS database details (host, username, password, database name). Access to your RSPS source code to add the claimvote logic. Access to your toplist control panel where you can set the callback URL. Tip: Your RSPS server usually already connects to a MySQL database for things like highscores, vote logs, etc. We will use the same connection or a similar one. Step 1 – Create the Vote Table in MySQL We need a table that will store each incoming vote. The callback script will insert one row per vote. 1.1 – SQL to Create the Table In phpMyAdmin or your MySQL tool, select your RSPS database (for example server), go to the SQL tab, and run this: CREATE TABLE IF NOT EXISTS vote_rewards ( id INT AUTO_INCREMENT PRIMARY KEY, username VARCHAR(32) NOT NULL, given TINYINT(1) NOT NULL DEFAULT 0, timestamp INT NOT NULL, site_id INT DEFAULT 0 ); 1.2 – What Each Column Means id – Unique ID for each vote (makes it easy to update rows). username – The RSPS username that voted. given – Whether the reward has been claimed: 0 = Vote is unclaimed (player has not claimed reward yet). 1 = Vote is claimed (reward already given). timestamp – When the vote was received (UNIX time, seconds since 1970). site_id – Optional, useful if you add multiple toplists later (1 = Site A, 2 = Site B, etc). Important: Do not change the column names unless you also change them in the PHP script and in your RSPS claimvote code. Step 2 – Create the PHP Callback Script This PHP file will be called by your toplist when a player finishes voting. Its job is very simple: Read the username from the request (for example, ?user=SomeName). Check that the request came from your toplist IP. Insert a new row into vote_rewards with given = 0. 2.1 – Full Callback Script (with Configuration) Create a new file on your PC called callback.php and paste this inside: <?php // --------------------------------------------------------- // CONFIGURATION SECTION – CHANGE THESE VALUES // --------------------------------------------------------- // Database connection details $dbHost = "localhost"; // Usually 'localhost' $dbUser = "root"; // Your MySQL username $dbPass = "password"; // Your MySQL password $dbName = "server"; // Your RSPS database name // Toplist IPs that are allowed to call this script $allowedIps = array( "123.123.123.123" // Replace with your toplist's real IP // You can add more IPs here if needed ); // Parameter name used by the toplist for username // Common ones are: 'user', 'username', 'player' $usernameParam = "user"; // --------------------------------------------------------- // DO NOT CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING // --------------------------------------------------------- // 1. Check that we got a username parameter if (!isset($_GET[$usernameParam])) { // No username provided die("No username specified"); } $username = trim($_GET[$usernameParam]); // Basic sanity check if ($username === "") { die("Empty username"); } // 2. Validate the IP address of the caller $remoteIp = $_SERVER["REMOTE_ADDR"]; if (!in_array($remoteIp, $allowedIps)) { // Request is NOT from an allowed IP // You can log this if you want die("Invalid IP"); } // 3. Connect to the MySQL database $connection = mysqli_connect($dbHost, $dbUser, $dbPass, $dbName); if (mysqli_connect_errno()) { // Database connection failed die("Database connection failed: " . mysqli_connect_error()); } // 4. Prepare data for insertion $timestamp = time(); $siteId = 1; // Optional: set this per toplist if you use multiple sites // 5. Use a prepared statement to insert the row safely $stmt = mysqli_prepare( $connection, "INSERT INTO vote_rewards (username, given, timestamp, site_id) VALUES (?, 0, ?, ?)" ); if (!$stmt) { die("Prepare failed: " . mysqli_error($connection)); } mysqli_stmt_bind_param($stmt, "sii", $username, $timestamp, $siteId); if (!mysqli_stmt_execute($stmt)) { die("Execute failed: " . mysqli_stmt_error($stmt)); } mysqli_stmt_close($stmt); mysqli_close($connection); // 6. Output success message (the toplist may check this) echo "OK"; ?> 2.2 – Things You MUST Change $dbHost, $dbUser, $dbPass, $dbName – Set these to match your MySQL login. $allowedIps – Replace 123.123.123.123 with your toplist’s IP address. $usernameParam – If your toplist sends ?username= or ?player= instead of ?user=, change it accordingly. $siteId – If you only have one site, leave it as 1. If you add more sites later, you can use different IDs. Important: The callback script never gives in-game rewards directly. It only inserts rows into the database. Your RSPS will handle rewards separately using the claimvote logic. Step 3 – Upload the Script and Get the Callback URL 3.1 – Upload the File Connect to your webhost using FTP or File Manager. Upload callback.php into a public folder (for example, /public_html/vote/). 3.2 – Example Callback URL If your domain is example.com and you uploaded to /public_html/vote/, your URL will be: https://example.com/vote/callback.php We will enter this URL into your toplist settings in the next step. 3.3 – Quick Manual Test Before touching your toplist, test the script manually: In your browser, visit: https://example.com/vote/callback.php?user=TestUser You should see: Invalid IP (this is good – it means the script runs, but rejects your IP because it is not the toplist IP). Now temporarily add your own IP to $allowedIps, refresh that URL, and you should see OK. Check your vote_rewards table – you should see a row with username = TestUser. Remove your IP again from $allowedIps so only the toplist IP stays. Step 4 – Configure the Toplist Callback Now you need to tell your toplist where to send the callback after a vote is completed. 4.1 – In Your Toplist Panel The exact names vary per site, but you are looking for settings like: Callback URL / Postback URL / Vote Callback Success URL or Return URL (not always needed) In the Callback URL field, enter the full URL to your script, for example: https://example.com/vote/callback.php 4.2 – Username Parameter Some toplists let you choose how the username is sent: ?user=USERNAME ?username=USERNAME ?player=USERNAME Match this with your $usernameParam value from the PHP script. 4.3 – Test Callback in the Toplist Many toplists have a Test Callback button in their panel. Use it: Click Test or Send Test Callback. Check your vote_rewards table – you should see a new row with their test username. If they show the callback response, it should say OK. Step 5 – Add Claim Logic to Your RSPS Now the database is filling with votes. The last step is to make your RSPS: Check the vote_rewards table for that player. Give rewards for any rows where given = 0. Set those rows to given = 1 so they cannot be claimed again. 5.1 – Basic Claim Algorithm (Human Explanation) Player types ::claimvote (or your command name). Server connects to the same MySQL database. Server runs: SELECT * FROM vote_rewards WHERE username = playerName AND given = 0; If there are 0 rows: tell player "You have no votes to claim." If there are 1 or more rows: Give rewards (points, items, keys, etc). Run: UPDATE vote_rewards SET given = 1 WHERE id = thatRowId; for each row. 5.2 – Example SQL Queries Find all unclaimed votes for a player: SELECT * FROM vote_rewards WHERE username = 'PlayerNameHere' AND given = 0; Mark a specific vote row as claimed: UPDATE vote_rewards SET given = 1 WHERE id = 123; In your RSPS code, you would replace PlayerNameHere with the logged-in player's username, and 123 with the actual id from the row. Note: Every server base is slightly different, so the Java code will vary, but the logic above is always the same: SELECT unclaimed rows → give rewards → UPDATE them as given. Step 6 – Full Testing Checklist Visit the callback URL manually with your own IP allowed: https://example.com/vote/callback.php?user=TestUser Confirm you see OK. Check database – row for TestUser should exist. Remove your IP from $allowedIps so only toplist is trusted. Use the Test Callback button in your toplist panel: Check database for test rows. Log in to your RSPS as that username. Type ::claimvote (or your command) and confirm: You receive the correct rewards. The rows in vote_rewards change from given = 0 to given = 1. Step 7 – Common Problems & Fixes Problem 1 – No rows appear in vote_rewards Check that your callback.php is reachable in the browser. Check your database credentials ($dbHost, $dbUser, $dbPass, $dbName). Check $allowedIps – make sure the toplist IP is correct. Check that your toplist callback URL matches your script URL exactly (https vs http, www vs non-www). Problem 2 – Rows exist, but claimvote gives nothing Make sure your RSPS is connecting to the same database and not a local test DB. Run the SELECT query manually in MySQL with the username you are testing. Check that your claim logic uses given = 0 and then updates rows to given = 1. Problem 3 – Player can claim the same vote multiple times Make sure you are running the UPDATE vote_rewards SET given = 1 query after each reward. Verify in the database that given actually changes to 1. Problem 4 – Callback sometimes responds with errors If you see messages like "Prepare failed" or "Execute failed", double-check that your table name and columns are spelled correctly. Enable basic logging by writing errors to a file if needed (for advanced debugging). Your Vote Callback System Is Now Fully Set Up You now have a professional, database-driven vote system that works great with RSPS and RuneTopic.

RSPS Toplist Community Rules & Guidelines A Safe, Fair, Open Environment for RSPS Owners, Developers, and Advertisers Welcome This platform exists to help server owners advertise their RSPS, share development resources, and connect with the RSPS community in a productive and professional way. These rules ensure that: All servers have an equal opportunity to grow Developers can safely publish and share their work No malicious or harmful content threatens the community Advertising stays fair, transparent, and non-abusive This is not an RSPS server’s forum — it is a Toplist + Development Hub where sources, tools, downloads, advertisements, and services may be posted freely, as long as they follow the rules below. 1. General Behaviour Be respectful and professional. Personal attacks, harassment, or toxic behaviour is not welcome. No discrimination or hate speech. Racism, sexism, homophobia, or any targeted harassment is forbidden. No drama / witch-hunting. If you have an issue with someone, take it to private messages or report it. No extreme vulgarity. Light swearing is fine; aggressive or hostile language is not. No impersonation. Do not pretend to be another user, developer, community, or staff member. 2. Allowed Content on This Platform This is a development-friendly RSPS platform. The following content is fully allowed: RSPS Source Releases (any base, any revision) Client Downloads (.jar, .zip, project folders) Snippets, tutorials, development guides Tools & utilities such as cache editors, model viewers, packers, and launchers Paid services (graphics, development work, systems, plugins, tools) Advertising your RSPS with media, updates, features, and links Code samples and GitHub links Runelite / custom client integrations This forum promotes open development — you may post almost any RSPS-related resource as long as it is not harmful or malicious. 3. Forbidden Content The following is strictly prohibited and will result in removal or permanent bans where applicable: Malicious downloads (backdoors, RATs, token loggers, malware, corrupted sources) Doxxing or sharing real-life personal information Illegal content of any kind Scamming in service trades, source sales, or ad campaigns Fake vouches or review manipulation Attack/raid tools (DDoS software, IP stressers, botnet tools) Posting someone else’s paid product without permission Advertising malware-infected cheat clients Reminder: If you post a tool or source with a backdoor, you will be permanently banned — no warnings. 4. Server Advertisements All RSPS owners are welcome to advertise here. However, ads must follow these rules: No fake player counts. Do not inflate numbers with screenshots, edited images, or false claims. No server trashing. Do not advertise your server by insulting other servers. No abusive bumping. Follow the bump cooldown rules for your section. Listings must use accurate links. The website, client, or Discord must go to the correct project. No referral manipulation (fake votes, automated vote bots, fake reviews) This section is intended to give every RSPS a fair platform to grow. 5. Resource Releases & Development When posting a release, you must follow these guidelines: Include a proper description of what you are releasing Include instructions if your resource requires setup Do not steal others' paid work and release it for free Be honest if something is unfinished, experimental, or outdated Do not post broken sources without warning (mark them as educational use only) 6. Trading, Services & Hiring The following is allowed: Paid development (coding, client work, content development) Graphic design (logos, banners, animations) Server management Website development Commissioned tools or patches The following is not allowed: Charging money for someone else’s open-source work Fake resumes or fake experience claims Scamming by accepting payment and not delivering 7. Account & Security Rules No account selling. Do not buy or sell forum accounts. No impersonation. Do not pretend to be a developer, staff member, or well-known figure. Keep your credentials secure. We will never ask for your password. Two-step verification is strongly recommended for service providers. 8. Punishments Depending on the severity of the rule break, punishments may include: Thread removal Warning points Temporary suspension Permanent forum ban Blacklist from advertising or trading Malicious actions such as backdoored releases or scamming result in instant permanent bans. Final Notes These rules exist to protect both server owners and developers. If you believe a rule needs to be added or updated, you may suggest it in the Feedback Section.