Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: eternum update #321

Merged
merged 1 commit into from
Dec 13, 2024
Merged

feat: eternum update #321

merged 1 commit into from
Dec 13, 2024

Conversation

r0man1337
Copy link
Contributor

@r0man1337 r0man1337 commented Dec 12, 2024

Updated links, cover image, screenshots

Summary by CodeRabbit

  • Content Updates
    • Updated title and color formatting for consistency.
    • Changed image file extensions from .png to .jpg.
    • Revised homepage, Discord, Twitter, and testnet URLs to new addresses.
    • Added a new paragraph providing an overview of the game.

Copy link

coderabbitai bot commented Dec 12, 2024

Walkthrough

The changes in the realms-eternum.mdoc file involve formatting updates and content revisions. Key modifications include changing string delimiters from single quotes to double quotes for consistency, updating image file extensions from .png to .jpg, and revising several URLs for the homepage, Discord, Twitter, and testnet. Additionally, a new paragraph has been added to describe the game's dynamic nature.

Changes

File Path Change Summary
apps/nextjs/content/games/realms-eternum.mdoc - Title and color fields updated from single to double quotes.
- Chains section updated to double quotes.
- Image file extensions changed from .png to .jpg.
- Updated homepage, Discord, Twitter, and testnet URLs.
- Added new descriptive paragraph about the game.

Possibly related PRs

  • Eternum Preseason #300: The changes in the eternum-preseason.mdoc file may relate to the overall content and structure of the game, similar to the updates made in realms-eternum.mdoc, although they focus on different aspects of the game.
  • feat: update og image for eternum launch #317: The updates in layout.tsx regarding metadata and images may indirectly relate to the overall presentation and branding of the game, which is also a focus in the realms-eternum.mdoc changes.

🐇 In realms where shadows play,
A game evolves, bright as day.
With links anew and colors bright,
Screenshots gleam in morning light.
Hop along, come join the fun,
In Eternum, adventures run! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

vercel bot commented Dec 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-realms-world ❌ Failed (Inspect) Dec 12, 2024 8:21pm
frontinus-start ❌ Failed (Inspect) Dec 12, 2024 8:21pm

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2a303cb and 6948a23.

⛔ Files ignored due to path filters (11)
  • apps/nextjs/public/content/games/realms-eternum/coverImage.png is excluded by !**/*.png
  • apps/nextjs/public/content/games/realms-eternum/screenshots/0.jpg is excluded by !**/*.jpg
  • apps/nextjs/public/content/games/realms-eternum/screenshots/0.png is excluded by !**/*.png
  • apps/nextjs/public/content/games/realms-eternum/screenshots/1.jpg is excluded by !**/*.jpg
  • apps/nextjs/public/content/games/realms-eternum/screenshots/1.png is excluded by !**/*.png
  • apps/nextjs/public/content/games/realms-eternum/screenshots/2.jpg is excluded by !**/*.jpg
  • apps/nextjs/public/content/games/realms-eternum/screenshots/2.png is excluded by !**/*.png
  • apps/nextjs/public/content/games/realms-eternum/screenshots/3.jpg is excluded by !**/*.jpg
  • apps/nextjs/public/content/games/realms-eternum/screenshots/3.png is excluded by !**/*.png
  • apps/nextjs/public/content/games/realms-eternum/screenshots/4.jpg is excluded by !**/*.jpg
  • apps/nextjs/public/content/games/realms-eternum/screenshots/4.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • apps/nextjs/content/games/realms-eternum.mdoc (2 hunks)
🔇 Additional comments (3)
apps/nextjs/content/games/realms-eternum.mdoc (3)

Line range hint 38-46: LGTM! Clear and informative content addition

The new paragraph effectively communicates the game's unique value proposition and dynamic nature. The comparison to Civilization 6 helps set appropriate user expectations.


17-17: Verify the chain configuration

The chain ID "420" corresponds to Optimism Goerli testnet. Please verify if this is the intended network for the game deployment.


25-29: Verify screenshot format migration

The screenshot format has been changed from PNG to JPG. Please ensure:

  1. All new JPG files exist and are properly optimized
  2. Image quality remains acceptable after the format change
✅ Verification successful

Screenshot format change verified

The JPG files for Realms Eternum screenshots (0.jpg through 4.jpg) exist at the correct location: apps/nextjs/public/content/games/realms-eternum/screenshots/. The format change from PNG to JPG has been properly implemented and all required files are present.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify existence and check properties of screenshot files
# Check if the new jpg files exist
for i in {0..4}; do
  fd "screenshots/${i}.jpg"
done

Length of output: 204


Script:

#!/bin/bash
# Let's check if the old PNG files exist and also search for any JPG files in the repository
echo "Searching for PNG files:"
fd ".png$" screenshots/

echo -e "\nSearching for JPG files:"
fd ".jpg$" screenshots/

# Let's also check the content file to understand the context better
echo -e "\nChecking the content file:"
cat "apps/nextjs/content/games/realms-eternum.mdoc"

Length of output: 1827


Script:

#!/bin/bash
# Let's check the repository root for the actual location of screenshots
echo "Searching for any image files in the repository:"
fd -e png -e jpg -e jpeg . apps/nextjs/

# Also check public directories which commonly store assets
echo -e "\nChecking specific public directories:"
fd -e png -e jpg -e jpeg . public/
fd -e png -e jpg -e jpeg . apps/nextjs/public/

Length of output: 30452

Comment on lines +31 to +35
homepage: https://eternum.realms.world/
discord: https://discord.gg/realmsworld
twitter: https://twitter.com/RealmsEternum
github: https://github.com/BibliothecaDAO/eternum
testnet: https://eternum.realms.world
testnet: https://next-eternum.realms.world/
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Issues found with some of the updated URLs

Based on the HTTP status codes:

  • Homepage (eternum.realms.world) - ✅ Accessible (200 OK)
  • Discord (discord.gg/realmsworld) - ⚠️ Redirects (301)
  • Twitter (twitter.com/RealmsEternum) - ❌ Forbidden (403)
  • Testnet (next-eternum.realms.world) - ✅ Accessible (200 OK)

Please address:

  • Twitter link returns a 403 Forbidden error, suggesting the account might not exist or is private
  • Discord invite link redirects, which might indicate an expired or invalid invite
🔗 Analysis chain

Verify accessibility and validity of updated URLs

Several important links have been updated:

  • Homepage moved from alpha to production
  • Discord invite link changed to a general invite
  • Twitter handle rebranded
  • Testnet domain updated

Please ensure all links are:

  1. Accessible and working
  2. Pointing to the correct destinations
  3. Using HTTPS
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check URL accessibility and HTTPS
# Verify URLs are accessible and use HTTPS
for url in "https://eternum.realms.world/" "https://discord.gg/realmsworld" "https://twitter.com/RealmsEternum" "https://next-eternum.realms.world/"; do
  curl -sI "$url" | head -n 1
done

Length of output: 876

@RedBeardEth RedBeardEth merged commit 984ad54 into main Dec 13, 2024
5 of 11 checks passed
@RedBeardEth RedBeardEth deleted the feat/eternum-update branch December 13, 2024 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants