Find space stations w/ observatory #1085
Comments
dmodoomsirius
changed the title
|
Removing enhancement in title as i added tag. |
|
I've considered something like this in the past and I do like the idea, the only issue I have with it is that I don't want people to be able to recover chips from other people's space station easily. Will see if something can be figured out |
|
@zmaster587 That's why I made it so you have to specify the station ID, not just find all the space stations at once. Unless you know the ID of someone's space station, you have to guess. Security would be massively increased if station IDs were a random 3-4-digit code (almost random, anyway; no duplicates could be generated, obviously). Less neat than station 1/2/3/etc., but anyone trying to find someone's station uninvited could be searching for many hours or days. |
|
you could put the space station to you only like galacticraft and can invite players to your station. |
|
@cwashington1217 That's a really awkward system. There are ways to keep stations secure without immersion-breaking things like username whitelisting and player invites. |
|
Oh I see, your right your system is has easy to know ways of getting your
stations back, but someone could still just type out as many codes in a 3
to 4 digit password has, but a on the other hand who would want to take
that long trolling someone so i guess that is a good idea.
…On Mon, Jan 22, 2018 at 12:31 PM, Ithronyar ***@***.***> wrote:
@cwashington1217 <https://github.com/cwashington1217> That's a really
awkward system. There are ways to keep stations secure without
immersion-breaking things like username whitelisting and player invites.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1085 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AiA_5zKVYTDvh1KmA3h_KSRGvqCFPHzuks5tNNQSgaJpZM4RmGzy>
.
|
|
do you know when zmaster is going to make the last texture for the creative
power plug for 1.7.10 or do you just play the latest version.
…On Mon, Jan 22, 2018 at 12:31 PM, Ithronyar ***@***.***> wrote:
@cwashington1217 <https://github.com/cwashington1217> That's a really
awkward system. There are ways to keep stations secure without
immersion-breaking things like username whitelisting and player invites.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1085 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AiA_5zKVYTDvh1KmA3h_KSRGvqCFPHzuks5tNNQSgaJpZM4RmGzy>
.
|
|
@Ithronyar I like the idea of the code, though I feel like if people lost the chip then they'd lose the station. Though rather than a random ID that you're given, another solution would be to allow the player to set a PIN of some kind or password (if a password is used then it may take even longer to guess). With a random ID I fear that players will forget too easily. Though that could introduce the a minigame where in PvP servers you can "hack" or "search for signals" from other people's space stations. That'd also make it so a space station isn't some permanent hidey hole where you can't be touched (config to disable ofc). Another system that may work is that the space station can have an inexpensive "beacon" or "security block" where allowed people can be entered or removed from the system (creator is in the system by default) and then players can just select their station from a list. @cwashington1217 I agree with @Ithronyar Having to use commands to invite and disinvite people from space stations feels kinda clunky to play with. |
|
@zmaster587 The security beacon/block thing sounds only slightly less annoying than the Galacticraft system, honestly. The basic idea has potential, though; maybe instead of just some "whitelisted players" block, it could be an active station defense block/turret/beam thing. Basically, unwanted intrusions get zapped with the beam, using a lot of power but blowing up whatever is approaching. Instead of dealing with player names and invites and such, approaching rockets need a radio transmitter block programmed with an authorization PIN. If the pin matches what's entered in the defense block/beam thing, the rocket is allowed. If not, it gets blasted. It doesn't really solve the whole station recovery problem, but it allows for a more immersive solution: If they're determined, any player can eventually find a space station without needing any sort of chip/ID/username/password. That makes sense anyway, since real orbital stations aren't exactly invisible, nor do they need a PIN or password to fly up to. There's no need to lock players out with an unimmersive whitelist/password/username system if you can build a death ray that blows up anyone you don't want around. |
Very funny. |
|
@nonenothing The explosion could have a large player-damaging radius that the intruder couldn't get away from. On top of potentially hours trying to find a particular station and having their rocket destroyed and probably dying, I don't think anyone would want to troll/grief/invade space stations unless they were either psychotically determined to ruin someone's day, or literally at war. No casual troll would be able to do anything. |
and instant effect at distance of 1000 blocks (or anyone can fly away) - not much difference from galacticraft white list
several titan ingot - such loss, such tragedy
Wrong. |
|
@nonenothing Lol This would work great with Suggestion- Weapons+ Tools+ Combat+ Compatability And [enhancement] Lasers and shields! Just saying! |
Basic idea: The observatory can scan for space stations in orbit, in a new "Space Station" tab or something similar.
With a specified space station ID (or orbit location, I don't know) input by the player, the observatory scans the sky for the space station. Once it finds the station, the observatory writes it to a space station ID chip.
This provides an important extra functionality to the observatory, and allows a space station to be recovered if its ID chips have been lost or destroyed.
Quick and mediocre concept I made for the new tab GUI:
The text was updated successfully, but these errors were encountered: