Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Talk:Serpentis Haven

Discussion page of Serpentis Haven

Latest comment: 28 March 2023 by Minatorra Critchaou in topic Incorrect pattern

Incorrect pattern

The gas haven pattern is not correct:

  • Initial Wave is as described
  • Wave 1: 3 - 4 Frigs; 3 - 4 Cruisers; 3 - 4 Battle Cruisers; 3 - 4 Battleships (trigger: BC)
  • Wave 2: 2 - 3 Frigs; 3 - 4 Battle Cruisers; 3 - 4 Battleships (trigger: BC)
  • Wave 3: 2 - 3 Frigs; 3 - 4 Battle Cruisers; 3 - 5 Battleships (trigger: BC)
  • Wave 4: 3 - 4 Frigs; 3 - 4 Battle Cruisers; 5 - 8 Battleships (trigger: BS)
  • Wave 5: 3 - 4 Frigs; 4 - 6 Battleships (can have Shadow, Dread or Titan spawn)

The numbers might vary from the list above. -- Minatorra Critchaoo (talk) 09:36, 27 March 2023 (UTC) Minatorra Critchaou (talk) 08:14, 28 March 2023 (UTC)Reply

I am a bit confused. You mention a wave 1 which is not used on the page. I assume it should be:
  • Initial wave
  • Wave 1 > Wave 2
  • wave 2 > Wave 3
  • wave 3 > Wave 4
  • Wave 4 > Wave 5
  • Wave 5 > Shadow Serpentis Boss ??
Also it is good practice to "sign" your contributions to a talk page. The easiest way to do that is by using four tildes (~~~~) the wiki will expand that to your name and a timestamp. -- Evon R'al (talk) 10:06, 27 March 2023 (UTC)Reply

Actually, there is one wave missing in the wiki description and wave 1 is not correct. It caused me always confusion, when I ran a gas haven until I wrote the waves down for myself. The boss/dread/titan is an additional spawn in wave 5. Similarly to the rock haven. I need further investigation for the wave triggers. Either it is a very specific ship or it changes from haven to haven (e.g., in one gas haven, wave 5 spawned after the destruction of the last BS. In another haven, the last wave spawned after a "random" destruction of a BS, while there were still BS from wave 4 present)

Minatorra Critchaou (talk) 08:14, 28 March 2023 (UTC)Reply