- Joined
- Feb 10, 2015
- Messages
- 36
- Reaction score
- 16
In fact that is the person who owns the server is writing the positive review. So extra points in my eyes.
Last edited:
Positive Review: Mikeland AUS Server
- Thread starter mikesheen
- Start date
- Status
- Joined
- Jan 27, 2013
- Messages
- 352
- Reaction score
- 104
Right, for a while i have been following this whole SNAFU.
And i must say i am really quite impressed with the lengths that Mikelands AUS will go to in order to discredit a negative review; including:
-Mustering a swarm of new players with little experience in the StarMade community to make positive 'reviews' (commonly known as sock-puppeting.)
-Reviewing his own server. (You expect people to take you seriously?)
-Banning the plaintiff from open discussion (That's a good one. It happens far too often. It also proves how you prefer to ignore the negative.)
-The most damming of them all: Lying.
Unless you're some Schema-level genius, you can't tell what's docked and whats not docked. That's the truth. There are no logs of such. I know this because i run a starmade server myself. I have run several. You have abused your power merely because someone had irritated you; you have called upon the masses to white knight for you by spreading lies and mis-information.
It's nice to see that people have the guts to call you out on your vile acts, and i applaud SuperWookie.
And i must say i am really quite impressed with the lengths that Mikelands AUS will go to in order to discredit a negative review; including:
-Mustering a swarm of new players with little experience in the StarMade community to make positive 'reviews' (commonly known as sock-puppeting.)
-Reviewing his own server. (You expect people to take you seriously?)
-Banning the plaintiff from open discussion (That's a good one. It happens far too often. It also proves how you prefer to ignore the negative.)
-The most damming of them all: Lying.
Unless you're some Schema-level genius, you can't tell what's docked and whats not docked. That's the truth. There are no logs of such. I know this because i run a starmade server myself. I have run several. You have abused your power merely because someone had irritated you; you have called upon the masses to white knight for you by spreading lies and mis-information.
It's nice to see that people have the guts to call you out on your vile acts, and i applaud SuperWookie.
- Joined
- Feb 10, 2015
- Messages
- 36
- Reaction score
- 16
There is a way to do stuff just fine and it is to dock things constantly the same way when there is no server lag. I have never had a issue with undocking ships EVER on any other server. Expect as I mentioned on mikeland where one of our ships was undocked and then stolen soon after. Only to learn later that it was K10wn who did it as I watched him do it to other ships of ours. (K10wn being the main admin in charge on the server.)
- Joined
- Jan 27, 2013
- Messages
- 352
- Reaction score
- 104
I should clarify that you can't see what's docked or not docked from logs.
- Joined
- Jul 9, 2013
- Messages
- 229
- Reaction score
- 71
You indeed can. There is a dock event recorded anytime a ship is docked or undocked (or used to be with the old docking system). If there is a docking timeout and a ship becomes undocked because of this, this is also recorded in the logs.
Example:
[2015-05-13 21:53:29] [DOCKING] NOW UNDOCKING: Ship[Calavera-1](73764); Server(0); DOCKED TO TYPE: 289; curpos: (121.0, -44.5, 121.0)
Last edited:
- Joined
- Feb 10, 2015
- Messages
- 36
- Reaction score
- 16
K1own I can call out your lie again. When we lost a ship to that so called bug you said you made a post on the bug tracker and it was rejected because no one could repeat it. You had NO idea how it was done or even if it was true. You only claimed to have saw some player do it when you requested and that is ALL that was ever mentioned of it. You keep claiming you can see it all in the logs but that is also a lie and will not work on people who in fact host servers. Your lie may work on the players who you accuse of cheating on the server. But here it will not.
[DOUBLEPOST=1432676550,1432675724][/DOUBLEPOST]http://bugs.star-made.org/issues/1647
- Joined
- Jul 9, 2013
- Messages
- 229
- Reaction score
- 71
You were asked to repeat this bug, and could not do it. I did manage to repeat the bug once, but could never do it again, nor could the testers on the bugtracker, hence it was rejected.
The bug SuperWookie was exploiting is not the same bug. This I could reproduce without fail. I've not seen this bug since the docking update.
- Joined
- Feb 10, 2015
- Messages
- 36
- Reaction score
- 16
Yet as Wookie claimed you have no proof of this "bug" yet are still perfectly sure that is what happen.
- Joined
- Jul 9, 2013
- Messages
- 229
- Reaction score
- 71
The bug was explained directly to AndyP and others on slack and they seemed to understand how it was happening. I'm going to assume nothing was done about it due to the rollout of the new docking system in the next update anyway.
Explaining how to exploit a bug is not something that should be discussed in an open forum!
- Joined
- Feb 10, 2015
- Messages
- 36
- Reaction score
- 16
Would it even matter? As you stated the new docking system fixes it.
- Joined
- Jul 9, 2013
- Messages
- 229
- Reaction score
- 71
This is not what I said. I said I've not seen it happen. This does not mean it is fixed and could still be possible to do under the right circumstances.
- Joined
- Feb 10, 2015
- Messages
- 36
- Reaction score
- 16
If it is the case you have failed to see it again and I assume you tested it a bit to see if it reproduced and it clearly has failed to. Then other people knowing of the possible glitch will allow more people to test it and see if it is even real.
- Joined
- Jul 9, 2013
- Messages
- 229
- Reaction score
- 71
The people who need to know about it do. This does not include you.
No, I have not tested for it since the docking update. When I receive reports of ships mysteriously becoming undocked again, then I will force the circumstances needed to reproduce the bug to see if it still exists.
Lecic
Convicted Lancake Abuser
- Joined
- Apr 14, 2013
- Messages
- 5,107
- Reaction score
- 1,228
I'd love to see these logs of yours. Also, if the bug was supposedly recreate-able on demand but has been fixed with the rail update, you should be able to tell us the bug and let us test for ourselves, shouldn't you?
EDIT- How about you go test it and tell us if it still exists after the rail update? Or, better yet, how about AndyP comes in here and tells us if you're telling the truth?
- Joined
- Feb 10, 2015
- Messages
- 36
- Reaction score
- 16
So far that seems like the magical logs they requested and you did not provide. But back to topic. You had no proof via your magical logs that Wookie did this glitch you claim is still real and may still be possible to do and you ban him on that notion. So HOW did you know he did this glitch that no one else seems to know about?
- Joined
- Jul 9, 2013
- Messages
- 229
- Reaction score
- 71
The logs show the docking events of the entity. The last docking event in the logs before it was destroyed was a dock to the station. There was no undock or dock timeout event between this and when it was destroyed. This same pattern of docking events were also present for the previous instances where other players had complained. This is why a ship was left there that I certainly knew was docked waiting for him to repeat what he had been doing.
Anybody who has taken the time to read these long boring logs knows they are overwritten usually within 24 hours of being made. MikeSheen has written a script since Wookie was removed to copy these logs to another location daily so there is a few weeks of logs at hand. The logs of what Wookie did on all occasions were overwritten the day after they happened. They were checked within hours of the events and complaints were made to see what had happened. You can't show what isn't there when they are asked for 3 or 4 days later. This will not happen again since Mike added his script to keep logs for a longer time period.
Anybody who has taken the time to read these long boring logs knows they are overwritten usually within 24 hours of being made. MikeSheen has written a script since Wookie was removed to copy these logs to another location daily so there is a few weeks of logs at hand. The logs of what Wookie did on all occasions were overwritten the day after they happened. They were checked within hours of the events and complaints were made to see what had happened. You can't show what isn't there when they are asked for 3 or 4 days later. This will not happen again since Mike added his script to keep logs for a longer time period.
Lecic
Convicted Lancake Abuser
- Joined
- Apr 14, 2013
- Messages
- 5,107
- Reaction score
- 1,228
- Joined
- Feb 10, 2015
- Messages
- 36
- Reaction score
- 16
- Joined
- Jan 27, 2013
- Messages
- 352
- Reaction score
- 104
AndyP
Customer Experience Manager
- Joined
- Aug 15, 2013
- Messages
- 1,199
- Reaction score
- 264
Just to clear this up
The exploit used to undock ships was "load order",
our (and this is Lancake and me) contact with rabid concluded in the base most likely being build over the sector border.
Because of this systems are not fully initialized depending on the load order,
as systems built from a base in other sectors may not get loaded at all or in time.
The assumption and also one snippet from a log we have seen (forgot where it was supplied from) stated the base was not initialized and the docking timed out.
This usually happens when only the "physical avatar" (ribexorig in log) is loaded and not the actual systems that reside in another sector.
However, this only shows again: Building stations over multiple sectors causes a lot of problems. And when people try to do this, they get sometimes unexpected results.
Also the recorded video (that was mentioned a few times) was being cut in different subscenes.
Unfortunately the cuts always happened when a continuous recording would have been the proof. So we got into direct contact with him, resulting in above assumption, as we could not reproduce the described bug/exploit.
So there is a "known way" this happens, but this requires mistakes while building the base, like extending a base over 3 sectors and cutting out one sector in the middle. (Improper moving/spawning of stations with help of admins may also result in issues)
- Andy
(in the future I would like to have a @ in front of my name in case it is used, so I can see this earlier and do not have to get called in by third parties.)
The exploit used to undock ships was "load order",
our (and this is Lancake and me) contact with rabid concluded in the base most likely being build over the sector border.
Because of this systems are not fully initialized depending on the load order,
as systems built from a base in other sectors may not get loaded at all or in time.
The assumption and also one snippet from a log we have seen (forgot where it was supplied from) stated the base was not initialized and the docking timed out.
This usually happens when only the "physical avatar" (ribexorig in log) is loaded and not the actual systems that reside in another sector.
However, this only shows again: Building stations over multiple sectors causes a lot of problems. And when people try to do this, they get sometimes unexpected results.
Also the recorded video (that was mentioned a few times) was being cut in different subscenes.
Unfortunately the cuts always happened when a continuous recording would have been the proof. So we got into direct contact with him, resulting in above assumption, as we could not reproduce the described bug/exploit.
So there is a "known way" this happens, but this requires mistakes while building the base, like extending a base over 3 sectors and cutting out one sector in the middle. (Improper moving/spawning of stations with help of admins may also result in issues)
- Andy
(in the future I would like to have a @ in front of my name in case it is used, so I can see this earlier and do not have to get called in by third parties.)
- Status