Revert generated GoldOSRS.com website code — awaiting actual website files

[Copilot]

All 21 previously generated PHP/CSS/JS files have been removed from the branch. The code was created from scratch before the actual website files were provided, so it has been reverted. The repository is back to its original state (README.md and LICENSE only), ready for the real website files to be applied.

Original prompt

Mega‑Prompt for Claude: Implement Website Updates (PHP/MySQL)

SITE = https://goldosrs.com
KEEP 100% OF THE SAME FRONTEND THEME AND LAYOUT!

I need you to edit my PHP/MySQL website to meet the specifications below. The website has multiple pages (home, order form, payment, gambling games, raffle, etc.) and uses a custom PHP backend with MySQL. Please first examine the existing codebase (I can provide any files you need). Then implement each step, ensuring all new code is secure (prevent SQL injection, XSS, CSRF) and follows best practices. After each step, explain what you changed and provide the modified code or clear instructions.

General Setup Assumptions:

· PHP 7.4+ with MySQLi or PDO.
· Sessions are used for user login and temporary data.
· Database tables: users, orders, order_history, bets, raffle_prizes, password_resets, etc. (You may need to create or alter tables.)
· Frontend: HTML, CSS, JavaScript (vanilla or jQuery). I’ll assume you can modify both PHP and JS files.

---

Step 1: Fix the “runes” animation on the home page

· Current issue: The runes are glitchy and not moving smoothly.
· Desired behavior: They should stream slowly and smoothly downward.
· Technical implementation:
· Locate the CSS/JS responsible (likely in home.php or a separate .js file).
· If CSS, adjust animation properties (e.g., animation: fall 20s linear infinite) and ensure transform is used.
· If JavaScript (canvas), rewrite the animation loop using requestAnimationFrame and a constant downward velocity. Remove any erratic random movements.
· Test responsiveness.

Step 2: Fix order form submission & implement payment flow

· Current issue: Order form does not submit correctly.
· Desired behavior:

1. Order form (order.php): User selects service(s) and payment method (card or Bitcoin). On submit, store order details in a basket (use $_SESSION['basket'] array).
2. Redirect to payment.php.
3. Payment page (payment.php):
   · If Bitcoin, display a static address (or generate per order) and a QR code.
   · If card, show a mock card form (or integrate Stripe if you have keys).
   · Show a countdown timer (JavaScript) starting at 60 minutes. The timer is informational only – do not clear the basket when it expires. The user can still complete payment after the timer runs out, but you may show a warning.
4. After payment (simulate a success callback), do:
   · Insert order into order_history table (user_id, service, amount, date, status='paid').
   · Clear $_SESSION['basket'].
   · Redirect to success.php.
5. If user adds multiple services before paying, all remain in basket. Basket should be displayed somewhere (e.g., in header) with a count.
   · Database changes:
   · Ensure order_history table exists: id, user_id, service, amount, payment_method, status, created_at.
   · Optionally create an orders table for pending orders if needed.
   · Security: Validate input, use prepared statements, regenerate session ID after login.

Step 3: Fix gambling games (including new RS3 games option)

· Current issue: None of the games work.
· Desired behavior:
· Add a new gambling game option labeled "RS3" (RuneScape 3 style) alongside existing games (slots, dice, etc.). You can implement it as a simple dice roll or a custom game – the exact mechanics are up to you, but make it functional and visually distinct.
· For each game, implement the game logic in PHP (for fairness) or JavaScript with server-side validation.
· User places a bet using credits from their account (store in users.credits).
· Determine win/loss based on game rules (e.g., random number).
· Update user credits and insert record into betting_history table: id, user_id, game, bet_amount, win_amount, result (win/loss), created_at.
· Display result on the game page and update betting history below.
· Technical notes:
· Use random_int() for cryptographically secure randomness on the server if real credits are involved.
· For JavaScript games, send the bet and result to PHP via AJAX to validate and update DB.
· Ensure the new RS3 game is accessible from the gambling page (e.g., a tab or button).

Step 4: Create a raffle page

· Current issue: No raffle page exists.
· Desired behavior:
· Create raffle.php.
· Display a “Prize pool” amount (e.g., sum of prize values from raffle_prizes table).
· Show a chest image/icon. On click, fetch and display the inventory (list of prizes) from the database (AJAX or page reload).
· Chest should have a CSS open animation (e.g., scale/rotate).
· Database: Create raffle_prizes table: id, name, value, added_date.
· Implementation:
· PHP script to get prizes and total value.
· JavaScript to toggle inventory display.

Step 5: Fix the reset password link

· Current issue: Email sends but link says expired.
· Desired behavior: Link should work for a set time (e.g., 1 hour).
· Debugging:
· Check...

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[marcusjenkinscode]

Remove this code as it was made before I gave you the website files to work off.

[Copilot]

Remove this code as it was made before I gave you the website files to work off.

Done — all 21 generated files have been removed in commit 1c0d67a. The branch is now back to just README.md and LICENSE. Please share your existing website files and I'll implement the required changes on top of them.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud