Give us an adjustable Persistence timer for capital ships

From 5 minutes to 60 minutes or so. The cap ship pilot should be allowed to choose a longer timer if they wish.

eww, no. let it be a static number, -1

I have no reason to object to giving players this choice. I do see it as a waste of dev time.

Make them static forever, **** this combat logging bs.

+1 this way you can leave your capship in a sector for others to use. Dont make the minimum less than it currently is (5 min). Max should be infinite

-1

Why should a capship be active while the owner is logged off? Being logged off should mean that he no longer has any impact in game.

I think that being allowed to choose whether your trident will stay where it is is a great idea.

I think a small reduction to the basic timer 3.5 mins or so, seems to be about right for a death if the opponents are overwhelming, but not so much a rag and ship change could work.

But, being able to choose to have it persist longer sounds great, although the infinite one seems a little too much, maybe four hours or so. Or even 24 hours... i dont think a permanent persistence would be good as the verse would become eventually littered with unpiloted tridents from old players who dont even play. But... leaving a trident in place for guild members to use is useful.

So... + 0.5 i guess hehehe

+1 to 5 minute or longer persistence timers. I also think we should be able to give owner keys out to let mates we trust to fly them while we're away. With owner keys and longer persistence, it could be a way to have guild storage that's available to those we'd like to share with.

+1 to 5 minute or longer persistence timers. I also think we should be able to give owner keys out to let mates we trust to fly them while we're away. With owner keys and longer persistence, it could be a way to have guild storage that's available to those we'd like to share with.


Translation: I'm too lazy to build my own capship so I want others to be able to share theirs with me and I want to be able to use and fly them as if they are my own.

I do think allowing others to pilot a trident is a cool idea, but sounds counterproductive in the long term. It is not a gameplay positive, in the longterm will result in small guilds having a single trident between them... etc.

Essentially the capships will always be best as an individuals achievement, for which reason i will always be very much thankful to Xeha, Sten Duncan, and Slp006 for their huge help with my trident.

If dents could be shared, motivation to build would drop like a stone.

That is not true.

If I had a trident available to use while building my trident, I wouldn't have stopped building my trident just because there was one available already. I would have used that trident to build my own. If this would become a thing, trident production would sky-rocket.

But I think the biggest problem with something like this is determining how the game would choose priority of different pilots being in command of the trident.

If there is a transfer of control, the persistence of the trident should be tied to the new 'owner' and their log in state. Of course, lending tridents opens another can of worms. Do you permit theft? How do you mandate that a lent ship is returned to the original builder? Without some sort of mechanism in place to return a trident, there will be players that infiltrate guilds or buddy up to players who own tridents in order to steal the trident. Waiting for a trident to get blown up so that the builder can buy a new one can be a very long time. Especially if the thief simply parks it in a station and doesn't log on again, or deletes the character.

Not that this is necessarily a bad potential outcome from a roleplay perspective, rather something I think GS needs to carefully consider before investing time in allowing the lending of tridents. Without some sort of security, I would not lend my trident to anyone, even players I know and trust.

Yea, that's the point I was trying to make. There's far more to worry about than how it would change current building processes.

+1

I don't have a problem with making it unlimited. In the case of wormhole and station sectors, players will do a good enough job of killing abandoned ships to keep things from being cluttered. For random empty sectors, the devs could probably just adapt the sector sleep code to handle any unmanned ships left there. They're going to have to do something similar anyway, long-run, if they want to add things like player-made stations and other persistent things. But short-term, they could always just have the game impose a cap on how many unmanned Tridents can persist at once and despawn the oldest (or least-recently-visited) whenever the cap is reached.

I don't think unlimited makes sense. If their is someone online that wants to use the ship for repairs, the owner could be able to do /timeout 60 or 120 etc, if their friends will be there. But there should be a max. I can't see any reason for more than four or six hours or maybe even eight.

Either way, for as big as the verse is, the minimum five minutes could be extended to ten so friends can show up and grab appropriate ships.

as far as the trident control is concerned, a /captain command could handle transfer of command to others on the trusted owner list. /captain rin would give rin control. /captain revoke, which can only be issued by the builder, would give the top owner/builder the control back. And, keyed owners online could issue the captain command to transfer to others on the original key list set by the builder. This would prohibit race conditions and confusion because captain transfer would be explicit by those on the owner list with the builder having ultimate control.