drincs-productions/nqtr

nqtr-time

Use when configuring or using the NQTR time system — timeTracker.initialize (dayStartTime, dayEndTime, timeSlots, weekLength, weekendStartDay, getDayName), currentTime/currentDate, increaseTime/increaseDate, nowIsBetween, isWeekend, currentTimeSlot, and the…

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/drincs-productions/nqtr --skill nqtr-time

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

NQTR time system

Official docs: pixi-vn.com/nqtr/time. Index: nqtr. Use ink for story-side time changes when available: nqtr-ink.

date and time are deliberately generic numbers: time is the time of day and resets each time date increments. Time can mean hours, minutes or an era. Use timeTracker (import from @drincs/nqtr).

Initialize (TypeScript, once at startup)

ts
import { timeTracker } from "@drincs/nqtr";

timeTracker.initialize({
    defaultTimeSpent: 1,   // default for `# wait`
    dayStartTime: 0,
    dayEndTime: 24,
    timeSlots: [
        { name: "Morning", startTime: 5 },
        { name: "Afternoon", startTime: 12 },
        { name: "Evening", startTime: 18 },
        { name: "Night", startTime: 22 },
    ],
    weekLength: 7,
    weekendStartDay: 6,    // default weekLength - 1
    getDayName: (weekDayNumber) => ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"][weekDayNumber],
});

Defaults: dayStartTime 0, dayEndTime 24, defaultTimeSpent 1, timeSlots [], weekLength 7.

Get / set

ts
timeTracker.currentTime;      // number
timeTracker.currentDate;      // number
timeTracker.currentTime = 12;
timeTracker.currentDate = 5;
ink
# set time 12
# set time 18.30
# set time 18:30   // ':' is converted to '.' internally
# set date 5

Increment

increaseTime(delta?) adds time; past dayEndTime it increments the date and restarts from dayStartTime plus the overflow. increaseDate(delta?, time?) adds days and optionally sets the time.

ts
timeTracker.increaseTime(2);
timeTracker.increaseDate(1, 8); // +1 day, time 8
ink
# wait                      // + defaultTimeSpent
# wait 2                    // + 2 time units
# wait days 1               // + 1 day, time = dayStartTime
# wait days 1 hours 2       // + 1 day and + 2 time

Queries

APIMeaning
timeTracker.isWeekendcurrent day is in the weekend
timeTracker.currentWeekDayNumber0-based weekday index
timeTracker.currentDayNamevia getDayName
timeTracker.currentTimeSlotindex in timeSlots of the current slot
timeTracker.nowIsBetween(from, to)current time in [from, to); wraps over midnight when from > to

Time-dependent images

Do not branch manually everywhere: build a small class (TimeSlotsImage) holding one image per slot and returning the right one from timeTracker.currentTimeSlot in a src getter, then use it for room backgrounds/sprites.

Pitfalls

  • Activities/commitments scheduling (timeSlot: { from, to }) uses the same time scale: keep dayEndTime consistent with the slots you write. A slot with from > to (e.g. { from: 20, to: 10 }) wraps over midnight.
  • Time changes are not automatic: the story/UI must call # wait / increaseTime when the player spends time.
du même dépôt

Autres Skills

Tous les Skills
drincs-productions
Communauté

nqtr

Index and entry point of the NQTR skill set — start here for any task on a project using @drincs/nqtr (Navigation Quest Time Routine), then follow the skill map to the right skill (navigation, time, activity, routine, quest, ink). Use when installing/configuring @drincs/nqtr, wiring vitePluginNqtr, overriding OnRunProps or the Interface types in nqtr.d.ts, writing custom Room/Location/Map/Activity/Commitment/Quest classes, or deciding whether to write NQTR logic in ink or TypeScript.

Installations / 1h
3
GitHub Stars
2
Mis à jour
17 nov.
drincs-productions
Communauté

nqtr-activity

Use when creating NQTR activities (actions the player can take, linked to rooms/locations/maps) — ActivityBaseModel, RegisteredActivities, linking at init (activities in the room constructor) vs at runtime (room.addActivity / " add activity X in room"), unlinking, timeSlot/dateScheduling, disabled/hidden, and custom Activity classes.

Installations / 1h
3
GitHub Stars
2
Mis à jour
17 nov.
drincs-productions
Communauté

nqtr-ink

Use when writing .ink files in a Pixi'VN project that uses @drincs/nqtr — every NQTR hashtag command ( enter room, set time, set date, wait, add/remove activity, add/remove routine, start/continue quest) and the quest state variables (questIdstarted, completed, failed, currentStageIndex), plus createNqtrHandler setup and options. Prefer this over TypeScript labels whenever ink is configured.

Installations / 1h
3
GitHub Stars
2
Mis à jour
17 nov.
drincs-productions
Communauté

nqtr-navigation

Use when defining or navigating NQTR rooms, locations and maps — RoomBaseModel/LocationBaseModel/MapBaseModel, RegisteredRooms/RegisteredLocations/RegisteredMaps, navigator.currentRoom, " enter room" in ink, entrance rooms, and custom Room/Location/Map classes. Navigation is the base of NQTR; activities and routines attach to it.

Installations / 1h
3
GitHub Stars
2
Mis à jour
17 nov.