OpenWF/SpaceNinjaServer
12
6
Fork 15
Code Issues 45 Pull Requests 6 Actions Packages Projects Releases Activity

feat: cycle 1999 calendar season every week #756

Merged
Sainan merged 2 commits from 1999-seasons into main 2025-01-10 22:18:42 -08:00
Conversation 3 Commits 2 Files Changed 7 +333 -3
7 changed files with 333 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
src/controllers/dynamic/worldStateController.ts
View File

@ -1,5 +1,9 @@
import { RequestHandler } from "express";
import staticWorldState from "@/static/fixed_responses/worldState.json";
import staticWorldState from "@/static/fixed_responses/worldState/worldState.json";
import static1999FallDays from "@/static/fixed_responses/worldState/1999_fall_days.json";
import static1999SpringDays from "@/static/fixed_responses/worldState/1999_spring_days.json";
import static1999SummerDays from "@/static/fixed_responses/worldState/1999_summer_days.json";
import static1999WinterDays from "@/static/fixed_responses/worldState/1999_winter_days.json";
import { buildConfig } from "@/src/services/buildConfigService";
import { IMongoDate, IOid } from "@/src/types/commonTypes";
@ -14,7 +18,10 @@ export const worldStateController: RequestHandler = (req, res) => {
...staticWorldState
};
const week = Math.trunc(new Date().getTime() / 604800000);
const day = Math.trunc(new Date().getTime() / 86400000);
const week = Math.trunc((day + 4) / 7); // week begins on mondays
const weekStart = week * 604800000;
const weekEnd = weekStart + 604800000;
// Elite Sanctuary Onslaught cycling every week
worldState.NodeOverrides.find(x => x.Node == "SolNode802")!.Seed = week; // unfaithful
@ -79,6 +86,17 @@ export const worldStateController: RequestHandler = (req, res) => {
][week % 8]
});
// 1999 Calendar Season cycling every week
worldState.KnownCalendarSeasons[0].Activation = { $date: { $numberLong: weekStart.toString() } };
worldState.KnownCalendarSeasons[0].Expiry = { $date: { $numberLong: weekEnd.toString() } };
worldState.KnownCalendarSeasons[0].Season = ["CST_WINTER", "CST_SPRING", "CST_SUMMER", "CST_FALL"][week % 4];
worldState.KnownCalendarSeasons[0].Days = [
static1999WinterDays,
static1999SpringDays,
static1999SummerDays,
static1999FallDays
][week % 4];
res.json(worldState);
};
@ -88,6 +106,7 @@ interface IWorldState {
SyndicateMissions: ISyndicateMission[];
NodeOverrides: INodeOverride[];
EndlessXpChoices: IEndlessXpChoice[];
KnownCalendarSeasons: ICalendarSeason[];
}
interface ISyndicateMission {
@ -115,3 +134,12 @@ interface IEndlessXpChoice {
Category: string;
Choices: string[];
}
interface ICalendarSeason {
Activation: IMongoDate;
Expiry: IMongoDate;
Season: string; // "CST_UNDEFINED" | "CST_WINTER" | "CST_SPRING" | "CST_SUMMER" | "CST_FALL"
Days: {
day: number;
}[];
}

2
src/services/purchaseService.ts
View File

@ -14,7 +14,7 @@ import { getVendorManifestByOid } from "@/src/services/serversideVendorsService"
import { IMiscItem } from "@/src/types/inventoryTypes/inventoryTypes";
import { IPurchaseRequest, IPurchaseResponse, SlotPurchase, IInventoryChanges } from "@/src/types/purchaseTypes";
import { logger } from "@/src/utils/logger";
import worldState from "@/static/fixed_responses/worldState.json";
import worldState from "@/static/fixed_responses/worldState/worldState.json";
import {
ExportBoosterPacks,
ExportBundles,

77
static/fixed_responses/worldState/1999_fall_days.json Normal file
View File

@ -0,0 +1,77 @@
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
[
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "day": 276, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillScaldraEnemiesEasy" }] },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"day": 283,
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"events": [
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/CompanionDamage" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/GasChanceToPrimaryAndSecondary" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/ElectricStatusDamageAndChance" }
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
]
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
},
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"day": 289,
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"events": [
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/WeaponUtilityUnlocker" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarMajorArtifactPack" }
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
]
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
},
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "day": 295, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillEnemiesWithMeleeEasy" }] },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"day": 302,
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"events": [
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarArtifactPack" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/WeaponSecondaryArcaneUnlocker" }
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
]
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
},
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "day": 305, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillEximusMedium" }] },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "day": 306, "events": [{ "type": "CET_PLOT", "dialogueName": "/Lotus/Types/Gameplay/1999Wf/Dialogue/EleanorDialogue_rom.dialogue", "dialogueConvo": "EleanorBirthdayConvo" }] },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "day": 307, "events": [{ "type": "CET_PLOT", "dialogueName": "/Lotus/Types/Gameplay/1999Wf/Dialogue/ArthurDialogue_rom.dialogue", "dialogueConvo": "ArthurBirthdayConvo" }] },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"day": 309,
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"events": [
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/Forma" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Gameplay/NarmerSorties/ArchonCrystalBoreal" }
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
]
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
},
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"day": 314,
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"events": [
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/PowerStrengthAndEfficiencyPerEnergySpent" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/ElectricalDamageOnBulletJump" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/MeleeSlideFowardMomentumOnEnemyHit" }
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
]
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
},
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "day": 322, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillEnemiesMedium" }] },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"day": 328,
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"events": [
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/WeaponSecondaryArcaneUnlocker" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/Types/StoreItems/Packages/Calendar/CalendarKuvaBundleSmall" }
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
]
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
},
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "day": 337, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillScaldraEnemiesWithAbilitiesHard" }] },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "day": 338, "events": [{ "type": "CET_PLOT", "dialogueName": "/Lotus/Types/Gameplay/1999Wf/Dialogue/QuincyDialogue_rom.dialogue", "dialogueConvo": "QuincyBirthdayConvo" }] },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"day": 340,
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"events": [
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/MeleeCritChance" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/RadiationProcOnTakeDamage" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/AbilityStrength" }
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
]
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
},
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"day": 343,
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"events": [
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/WeaponPrimaryArcaneUnlocker" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/FormaAura" }
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
]
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
},
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "day": 352, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillTankHard" }] },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"day": 364,
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
"events": [
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarMajorArtifactPack" },
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
{ "type": "CET_REWARD", "reward": "/Lotus/Types/StoreItems/Boosters/ModDropChanceBooster3DayStoreItem" }
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
]
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
}
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->
]
coderabbitai[bot] commented 2025-01-09 21:35:25 -08:00 (Migrated from github.com)
Review
Copy Link

⚠️ Potential issue

Address calendar coverage gaps and edge cases.

Several calendar coverage issues need attention:

  1. Gaps between all seasons:
    • Winter → Spring: days 88-99
    • Spring → Summer: days 177-185
    • Summer → Fall: days 271-275
  2. End of year coverage:
    • Day 365 is not assigned to any season
    • Leap year handling is not defined

These gaps could affect the weekly cycling functionality.

Consider these solutions:

  1. Extend season ranges to eliminate gaps
  2. Add explicit handling for transition days
  3. Document behavior during gap days
  4. Add leap year handling logic

Would you like me to propose a specific implementation for handling these edge cases?

_:warning: Potential issue_ **Address calendar coverage gaps and edge cases.** Several calendar coverage issues need attention: 1. Gaps between all seasons: - Winter → Spring: days 88-99 - Spring → Summer: days 177-185 - Summer → Fall: days 271-275 2. End of year coverage: - Day 365 is not assigned to any season - Leap year handling is not defined These gaps could affect the weekly cycling functionality. Consider these solutions: 1. Extend season ranges to eliminate gaps 2. Add explicit handling for transition days 3. Document behavior during gap days 4. Add leap year handling logic Would you like me to propose a specific implementation for handling these edge cases? <!-- This is an auto-generated comment by CodeRabbit -->

75
static/fixed_responses/worldState/1999_spring_days.json Normal file
View File

@ -0,0 +1,75 @@
[
{ "day": 100, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillScaldraEnemiesEasy" }] },
{
"day": 101,
"events": [
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/EnergyOrbToAbilityRange" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/ElectricStatusDamageAndChance" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/EnergyRestoration" }
]
},
{
"day": 102,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Gameplay/NarmerSorties/ArchonCrystalBoreal" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarMajorArtifactPack" }
]
},
{ "day": 106, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillTechrotEnemiesEasy" }] },
{
"day": 107,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarArtifactPack" },
{ "type": "CET_REWARD", "reward": "/Lotus/Types/StoreItems/Packages/Calendar/CalendarKuvaBundleSmall" }
]
},
{ "day": 122, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillTechrotEnemiesWithMeleeMedium" }] },
{
"day": 127,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/Forma" },
{ "type": "CET_REWARD", "reward": "/Lotus/Types/StoreItems/Packages/Calendar/CalendarVosforPack" }
]
},
{ "day": 129, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillEnemiesWithAbilitiesMedium" }] },
{
"day": 135,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarArtifactPack" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/WeaponMeleeArcaneUnlocker" }
]
},
{
"day": 142,
"events": [
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/BlastEveryXShots" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/MagnitizeWithinRangeEveryXCasts" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/GenerateOmniOrbsOnWeakKill" }
]
},
{ "day": 143, "events": [{ "type": "CET_PLOT", "dialogueName": "/Lotus/Types/Gameplay/1999Wf/Dialogue/JabirDialogue_rom.dialogue", "dialogueConvo": "AmirBirthdayConvo" }] },
{ "day": 161, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillScaldraEnemiesWithAbilitiesHard" }] },
{
"day": 165,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/Forma" },
{ "type": "CET_REWARD", "reward": "/Lotus/Types/StoreItems/Boosters/ModDropChanceBooster3DayStoreItem" }
]
},
{ "day": 169, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarDestroyPropsHard" }] },
{
"day": 171,
"events": [
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/GasChanceToPrimaryAndSecondary" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/AbilityStrength" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/MeleeCritChance" }
]
},
{
"day": 176,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarArtifactPack" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Recipes/Components/WeaponUtilityUnlockerBlueprint" }
]
}
]

75
static/fixed_responses/worldState/1999_summer_days.json Normal file
View File

@ -0,0 +1,75 @@
[
{ "day": 186, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillScaldraEnemiesEasy" }] },
{ "day": 191, "events": [{ "type": "CET_PLOT", "dialogueName": "/Lotus/Types/Gameplay/1999Wf/Dialogue/AoiDialogue_rom.dialogue", "dialogueConvo": "AoiBirthdayConvo" }] },
{
"day": 193,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Gameplay/NarmerSorties/ArchonCrystalAmar" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarMajorArtifactPack" }
]
},
{
"day": 197,
"events": [
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/MeleeAttackSpeed" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/AbilityStrength" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/CompanionDamage" }
]
},
{ "day": 199, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillScaldraEnemiesWithMeleeMedium" }] },
{
"day": 210,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarArtifactPack" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Upgrades/Mods/FusionBundles/CircuitSilverSteelPathFusionBundle" }
]
},
{ "day": 215, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillTechrotEnemiesWithMeleeEasy" }] },
{
"day": 228,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Recipes/Components/WeaponUtilityUnlockerBlueprint" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarRivenPack" }
]
},
{ "day": 236, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarDestroyPropsMedium" }] },
{
"day": 237,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/Types/StoreItems/Packages/Calendar/CalendarKuvaBundleLarge" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarMajorArtifactPack" }
]
},
{
"day": 240,
"events": [
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/RadialJavelinOnHeavy" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/SharedFreeAbilityEveryXCasts" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/CompanionsRadiationChance" }
]
},
{ "day": 245, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillEnemiesWithAbilitiesHard" }] },
{
"day": 250,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/Types/StoreItems/Boosters/AffinityBooster3DayStoreItem" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Recipes/Components/OrokinReactorBlueprint" }
]
},
{ "day": 254, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillTankHard" }] },
{
"day": 267,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarArtifactPack" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/WeaponSecondaryArcaneUnlocker" }
]
},
{
"day": 270,
"events": [
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/EnergyOrbToAbilityRange" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/PunchToPrimary" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/OvershieldCap" }
]
}
]

75
static/fixed_responses/worldState/1999_winter_days.json Normal file
View File

@ -0,0 +1,75 @@
[
{ "day": 6, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillEximusEasy" }] },
{
"day": 15,
"events": [
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/MagazineCapacity" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/Armor" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/EnergyRestoration" }
]
},
{ "day": 21, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillScaldraEnemiesEasy" }] },
{
"day": 25,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarMajorArtifactPack" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Gameplay/NarmerSorties/ArchonCrystalGreen" }
]
},
{
"day": 31,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Recipes/Components/WeaponUtilityUnlockerBlueprint" },
{ "type": "CET_REWARD", "reward": "/Lotus/Types/StoreItems/Packages/Calendar/CalendarKuvaBundleSmall" }
]
},
{ "day": 43, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillEnemiesWithAbilitiesMedium" }] },
{ "day": 45, "events": [{ "type": "CET_PLOT", "dialogueName": "/Lotus/Types/Gameplay/1999Wf/Dialogue/LettieDialogue_rom.dialogue", "dialogueConvo": "LettieBirthdayConvo" }] },
{
"day": 47,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/Types/StoreItems/Boosters/AffinityBooster3DayStoreItem" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarMajorArtifactPack" }
]
},
{ "day": 48, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillScaldraEnemiesWithMeleeMedium" }] },
{
"day": 54,
"events": [
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/CompanionsBuffNearbyPlayer" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/OrbsDuplicateOnPickup" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/FinisherChancePerComboMultiplier" }
]
},
{
"day": 56,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/BoosterPacks/CalendarArtifactPack" },
{ "type": "CET_REWARD", "reward": "/Lotus/Types/StoreItems/Packages/Calendar/CalendarKuvaBundleSmall" }
]
},
{ "day": 71, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarKillTechrotEnemiesHard" }] },
{
"day": 77,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/WeaponSecondaryArcaneUnlocker" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Upgrades/Mods/FusionBundles/CircuitSilverSteelPathFusionBundle" }
]
},
{ "day": 80, "events": [{ "type": "CET_CHALLENGE", "challenge": "/Lotus/Types/Challenges/Calendar1999/CalendarDestroyPropsMedium" }] },
{
"day": 83,
"events": [
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Recipes/Components/OrokinReactorBlueprint" },
{ "type": "CET_REWARD", "reward": "/Lotus/StoreItems/Types/Items/MiscItems/WeaponUtilityUnlocker" }
]
},
{
"day": 87,
"events": [
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/EnergyOrbToAbilityRange" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/MeleeAttackSpeed" },
{ "type": "CET_UPGRADE", "upgrade": "/Lotus/Upgrades/Calendar/CompanionDamage" }
]
}
]

0
static/fixed_responses/worldState.json → static/fixed_responses/worldState/worldState.json
View File