Implement Event Maps

[sven-n]

Currently no event maps are implemented. Event maps include for example 'Blood Castle' and 'Devil Square'.
Different from the original game we could also change that some of these events do not run in an interval (like once every hour), but every player/party can instantly enter the map whenever they want. They could get an exclusive instance of it, so there are no other parties disturbing. Of course, this can't be done with Player-versus-Player events like 'Chaos Castle'.

• Devil Square
• Blood Castle
• Chaos Castle
• Illusion Temple
• Double Goer

[sven-n]

Update: Event tickets can be created through the chaos machine already. The required items are dropping, too.
Ofc, the events itself are still not implemented yet.

[sven-n]

I think version 0.95d was the first version to include 'Devil Square', so we should start to implement event maps ;-)

[sven-n]

Devil Square is now implemented with #227. However, the game client of version 0.95d has some minor visual flaws when entering and finishing the event. It might not have been finished in this client version yet - if my memory doesn't fool me, webzen didn't introduce it before season 1 in the global servers.

[sven-n]

See #893 for illusion temple

[apraxico]

I'm working on the Double Goer / Doppelganger event of this checklist and will open a PR soon. Before that, a few design decisions which you may want to comment on:

• One instance per party. The event is entered on demand at Lugard, so the definitions use MiniGameMapCreationPolicy.OnePerParty and no periodic start plug-in. The first member of a party enters a random one of the four maps (65–68), the other members follow into the same instance. EnterMiniGameAction isn't changed.
• Two tickets. The client accepts a Mirror of Dimensions (14,111) and a Doppelganger Free Ticket (13,125). MiniGameDefinition supports one ticket item, so the doppelganger definitions don't define one, and an EnterDoppelgangerAction checks and consumes the ticket after a successful entrance. Five Signs of Dimensions (14,110) transform into a mirror, like the Symbol of Kundun into a Lost Map.
• New monsters and chests. The monsters 529–539 are added. The reward chests 541/542 are opened by talking to them, because the client handles them as NPCs.
• Configuration. Like the Kanturu event definition, the run of the event (monsters, paths, multipliers, chests) is the configuration of a feature plug-in, so it can be adjusted in the admin panel. The defaults are simple values meant to be tuned per server.
• The monsters walk along a path of 23 areas, which revealed a bug in the ScopedGridNetwork. It's fixed separately in Fix pathfinding: include start and end in the segment of the ScopedGridNetwork #972, which this PR depends on.

[apraxico]

I'm taking the Raklion (Battle of Selupan) event of this checklist; the PR follows right away.

It runs on the existing hatchery map (58) as a continuous event, not as a mini game, like the original: the spider eggs appear, Selupan appears when they're destroyed, the hatchery gate closes after 5 minutes, and after the battle the hatchery opens again after a configurable time (12 hours by default).

[apraxico]

I'm taking the Crywolf Fortress event next. It isn't in the checklist above, but it's the remaining big Season 6 event without an owner, and I didn't find any issue or PR about it.

Like Raklion, it would run on the existing map (34) as a continuous event, not as a mini game. The plan is to split it into two PRs:

1. The event itself:
   • the state cycle with a configurable schedule;
   • the altar contracts of the elves and the statue shield;
   • the Dark Elf groups, soldiers and ballistas, and Balgass;
   • win/lose, MvP ranking with its experience, the Jewel of Bless rewards and the hero list;
   • the occupation state with its terrain;
   • the 0xBD packets.
2. The global effects of the result: the chaos mix success rate bonus, reduced monster health, and the jewel drop and experience penalties.

It doesn't touch the Castle Siege packets or classes, so it shouldn't collide with the work in progress there.