Hatchie-Studio / lotstracker

An issue tracking system for Star Wars: Legacy of the Sith
3 stars 1 forks source link

Codecrack, openhatch problem #40

Closed matt1672 closed 6 years ago

matt1672 commented 6 years ago

Not sure if this is a problem with regular ships or just the Jawa Sandcrawler on Tatooine.

I went to open it and it gave me the "Hey! That's not your ship!" message. So I used codecrack to get the password. Used 'open sandcrawler -password-' and still got the not your ship message.

Each time I codecrack it, I get a different password needed, and none of them work to open it. Password on it changing constantly with not enough time to use the password to open it?

Thanks!

matt1672 commented 6 years ago

Seems it doesn't work with other ships either. Tried to codecrack a regular ship, got the same password each time I did it, but that password 'open ship 1220' gives me the "Hey! That's not your ship!" message. and won't let me open it like it used to.

pqueen commented 6 years ago

Got to type the number n open

Sent from the Yahoo Mail app. Get yours!

On Tue, Mar 6, 2018 at 2:17 PM, matt1672notifications@github.com wrote:
Not sure if this is a problem with regular ships or just the Jawa Sandcrawler on Tatooine.

I went to open it and it gave me the "Hey! That's not your ship!" message. So I used codecrack to get the password. Used 'open sandcrawler ' and still got the not your ship message.

Each time I codecrack it, I get a different password needed, and none of them work to open it. Password on it changing constantly with not enough time to use the password to open it?

Thanks!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

matt1672 commented 6 years ago

I realize how it's supposed to work. 'open ship -password-'

What I'm saying is. It's not working that way currently.

Thanatoslots commented 6 years ago

The sandcrawler is designed not to be cracked but it seems this issue happens with normal ships and it seems doesn't even zap a player for putting in an incorrect code.

michaelirick commented 6 years ago

This is fixed :)