Make the Duskcaller Castle bound instead of Clan bound

Comments: 7

Oldest • Newest • Most likes • Fewest likes

• Add a comment
• 20 May, '25
  HighTec

  Highlighted comment
  
  The Dusk Caller is a great QOL feature, but its not well thought through. on my pve server, we basicslly clan hop all the time just to get prisoners to the right castle. its very annoying. Even just transporting them between your own 2 castles is so tedious. I vote for Niks idea. Just let us choose which castle to send them to.

  1 Copy link to this comment
• 07 May, '25
  Nik

  I'd like to propose an alternative solution to this suggestion.
  
  The Dusk Caller is a very annoying item to work with in a Clan, perhaps it could open the map when you use the Dusk Caller and you can manually select which Castle to send the servant to, like the map interaction when you're on the throne to send a servant to a zone to harvest materials.
  
  It could display a number of 'Available Cells' that are in the castles on the map.
  
  I run a PvE server with clan number of 4, and it's rather annoying to hunt for blood types in the map, since using dusk caller usually sends the servant to the nearest friendly castle, which means I have to talk to my friends and co-ordinate with them to remove any empty cells or if they are offline, I have to go to their base and dismantle their cells, then re-send my servant and HOPE it goes to my castle this time. Eventually just jumping around from base to base.

  33 Copy link to this comment
• 07 May, '25
  SinisterCP

  Just have us be able to bind a dusk caller to a particular empty cell after crafting, taking the guess work out of it at the expense of making it un stackable. Problem solved.

  3 Copy link to this comment
• 08 May, '25
  Ferd

  Adding a Dusk Caller Beacon should help. It will always teleport your dusk caller to that castle. The only hassle is it won't work while your cells are full. But in a clan you can send someone home to dismantle your beacon then re use it again. Have the Dusk Caller Beacon limited to 1 per player or per castle.

  4 Copy link to this comment
• 08 May, '25
  Illium

  Could simplify it to send the prisoner to whichever castle you are bound to a coffin in. Since you can only bind to one it would work as a good target.

  6 Copy link to this comment
• 09 May, '25
  Darkest King

  I think of all the proposed alternative ideas here, Nik's is the simplest.
  
  Tying each dusk caller to a specific cell would be tedious and un-necessary since once the victim is at your castle you are free to move them around as you wish.

  1 Copy link to this comment
• 22 May, '25
  Nick

  Why choose between personal or clan based duskcaller, when they could make it function as both?
  It can simply prioritize sending to your own castle first, and if you have no available cages then send it to any available clan cages.
  
  Game even already have all the necessary data.
  -For Duskcaller to work, it'll need to fetch data on all available friendly cages (which means it checks map for any friendly territory), list all the cages and calculate the closest available one to the player.
  -They could simply add additional check on the cages "is this cage on [playername] plot" (which they know, based on the map listing individual player names) and save the result to a second list
  -Then the Dusk can check list 2 first (your own castle) for any empty cages, and if there's none defaults to list 1 (closest clan ones) and then send the prisoner accordingly.

  6 Copy link to this comment