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

added god mode to sepolia #2673

Merged
merged 1 commit into from
Jan 30, 2025
Merged

added god mode to sepolia #2673

merged 1 commit into from
Jan 30, 2025

Conversation

aymericdelab
Copy link
Collaborator

@aymericdelab aymericdelab commented Jan 30, 2025

Summary by CodeRabbit

  • New Features
    • Updated Sepolia testnet configuration with modified gameplay mechanics
    • Zero stamina costs for travel and exploration
    • Adjusted hyperstructure creation costs
    • Modified battle grace periods
    • Increased quest resource requirements
    • Updated travel speed for donkeys

Copy link

vercel bot commented Jan 30, 2025

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

Name Status Preview Comments Updated (UTC)
eternum ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 30, 2025 5:47pm
eternum-docs ❌ Failed (Inspect) Jan 30, 2025 5:47pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
eternum-landing ⬜️ Ignored (Inspect) Visit Preview Jan 30, 2025 5:47pm

Copy link
Contributor

mentatbot bot commented Jan 30, 2025

Hi @aymericdelab! You need to be added as a user to interact with me. Please ask @ponderingdemocritus to add you on the settings page.

You are receiving this comment because I am set to review all PRs. That is configurable here.

Copy link
Contributor

coderabbitai bot commented Jan 30, 2025

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

config/environments/sepolia.ts

Oops! Something went wrong! :(

ESLint: 9.18.0

ESLint couldn't find an eslint.config.(js|mjs|cjs) file.

From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:

https://eslint.org/docs/latest/use/configure/migration-guide

If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.

Walkthrough

The pull request modifies the Sepolia testnet environment configuration (sepolia.ts) to customize gameplay mechanics for testing purposes. The changes include setting stamina costs to zero, defining hyperstructure creation costs, removing battle grace periods, increasing quest resource requirements, and adjusting travel speed. These modifications are designed to create a more flexible and rapidly testable environment by removing typical game constraints.

Changes

File Change Summary
config/environments/sepolia.ts - Added SepoliaEternumGlobalConfig with zero stamina costs
- Defined Lords hyperstructure creation cost at 3,000
- Set battle grace periods to zero
- Increased quest resource requirements dramatically
- Set donkey travel speed to 1 second per kilometer

Possibly related PRs

Suggested reviewers

  • bob0005

Poem

🐰 In Sepolia's digital domain,
Where rabbits test without a strain,
Zero stamina, resources galore,
Battles swift, quests to explore!
A testnet playground, wild and free! 🚀

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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. (Beta)
  • @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

Failed to generate code suggestions for PR

Copy link
Contributor

@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: 0

🧹 Nitpick comments (2)
config/environments/sepolia.ts (2)

26-30: Consider testing with varied hyperstructure costs.

While a fixed cost of 3,000 Lords simplifies testing, consider adding test cases with different cost ranges to ensure the system handles varying amounts correctly.

   hyperstructures: {
     ...CommonEternumGlobalConfig.hyperstructures,
-    hyperstructureCreationCosts: [{ resource_tier: ResourceTier.Lords, min_amount: 3_000, max_amount: 3_000 }],
+    hyperstructureCreationCosts: [
+      { resource_tier: ResourceTier.Lords, min_amount: 3_000, max_amount: 3_000 },
+      { resource_tier: ResourceTier.Lords, min_amount: 10_000, max_amount: 50_000 },
+    ],
   },

31-37: Consider minimal delays for battle timing edge cases.

While zero delays speed up testing, consider keeping minimal delays (e.g., 1 second) to potentially catch race conditions or timing-related issues that could occur in production.

   battle: {
     ...CommonEternumGlobalConfig.battle,
     graceTickCount: 0,
     graceTickCountHyp: 0,
-    delaySeconds: 0,
+    delaySeconds: 1, // Minimal delay to catch potential race conditions
   },
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7689e84 and 62f0348.

📒 Files selected for processing (1)
  • config/environments/sepolia.ts (1 hunks)
🔇 Additional comments (5)
config/environments/sepolia.ts (5)

9-17: Well-structured and documented configuration file!

The file is properly documented with JSDoc comments explaining its purpose and relationship to the common configuration.


90-94: LGTM! Clear speed configuration for testing.

The 1 second per kilometer speed setting is well-documented and appropriate for testing purposes.


Line range hint 95-98: LGTM! Reasonable season start delay for testing.

The 1-minute delay before season start allows for quick testing while still maintaining a realistic sequence of events.


20-25: Verify this configuration is test-environment only.

Setting stamina costs to zero removes core gameplay mechanics. While this is appropriate for testing, we should ensure this configuration cannot be accidentally deployed to production.

✅ Verification successful

✓ Configuration is correctly isolated to test environment

The zero-cost stamina settings are only present in the Sepolia test environment configuration, with no instances found in other environment files. This confirms the configuration is safely isolated from production environments.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if similar zero-cost configurations exist in other environments
echo "Checking for zero-cost configurations in other environment files..."
rg -l "travelCost: 0" config/environments/ | grep -v "sepolia.ts" || echo "No other environments found with zero travel cost"
rg -l "exploreCost: 0" config/environments/ | grep -v "sepolia.ts" || echo "No other environments found with zero explore cost"

Length of output: 497


38-89: Verify handling of large resource amounts.

The significantly increased resource amounts (e.g., 1,200,000,000) could potentially cause integer overflow issues depending on the system's implementation.

✅ Verification successful

Resource amount handling is safely implemented

The codebase demonstrates robust handling of resource amounts with:

  • Type-safe implementation using Cairo's u128
  • Explicit overflow protection and validation checks
  • Safe arithmetic operations with proper scaling

The configured amounts (max 1.2 billion) are well within the system's safe limits.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for type definitions and value constraints
echo "Checking for type definitions of resource amounts..."
rg -A 5 "type.*Resource" || echo "No explicit resource type definitions found"
rg -A 5 "interface.*Resource" || echo "No resource interfaces found"

# Search for overflow checks
echo "Checking for overflow protection..."
rg -A 5 "(MAX|max).*_amount" || echo "No maximum amount constraints found"

Length of output: 89962


Script:

#!/bin/bash
# Search for resource amount validation and arithmetic operations
echo "Checking resource amount validation..."
rg -A 5 "amount.*=|=.*amount" "contracts/game/src/"

echo "Checking arithmetic operations on resource amounts..."
rg -A 5 "amount \+|\+ amount|amount \*|\* amount|amount -|- amount|amount /|/ amount" "contracts/game/src/"

Length of output: 75937

@edisontim edisontim merged commit bb4d335 into next Jan 30, 2025
5 of 6 checks passed
@edisontim edisontim deleted the sepolia-god-mode branch January 30, 2025 18:07
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