Winter Princess and Knights: the native winter Server Missions replace #3603's inferred timetable

Offen
#3,790 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@Rebraxin arbeitet bereits daran.

Seit 16.11.2026.

  • #3791 von @Rebraxin — offen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

area: server enhancement priority: medium status: claimed

The winter Christmas mode of #3603 put the White Knight and Princess Miyene on a timetable that was inferred, not native. It tied the Snow Slaves to the snowfalls, and it dropped the 2007 Red Santa Socks. The v1.188 server and the v1.696 client show what the event really was: Winter Princess and Knights (QEV_WINTER_EVENT_2009). It was a server-wide Server Mission system, _RefServerEvent 30001-30004, counted by the shard manager.

Mission Filled by Goal Reward
30001 Snow Flake Event So-ok's snow flake exchanges 18 × players online + 100 everyone +20 % EXP/SP for 1 h
30002 Snow Slave Hunting Event Snow Slave kills 360 × players online + 100 the last hunter wins +100 % EXP/SP for 3 h
30003 White Knight summon Event each 30002 completion 1 40 White Knights on fixed points
30004 Princess summon Event every 5th 30003 completion 5 40 Princesses on the same points

Scope:

  • Snow Slaves: half of the open world's champions are born Snow Slaves. Each hit lands for 1, and a Snow Slave drops a Snow flake (ITEM_ETC_E091216_SNOWFLAKE, imported from v1.696).
  • So-ok: she trades every 10 flakes for a gift from the native table, using its native talk rows (SN_TALK_QEV_SERVER_EVENT_QUEST_A..E).
  • Missions: the four missions, with their chain, their native goals, the 10 s reward delay, the native English notices, and rows kept across restarts.
  • Winter kinds: their own characterinfo profile and sounds. Today a Snow Slave dies with a Chinese man's scream.
  • Out of scope: the client gauge (the native 0x34F2 server-event messages). It gets a follow-up issue that depends on this one.
Vorherrschende Sprache
Go
Sterne
97
Forks
61
Ø Merge
4 Std. 25 Min.
Gemergte PRs (30 T.)
953

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus opensro-dev/opensro

Alle Issues in opensro-dev/opensro

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.