Posts by Apostle

Quote from CarbonDeathRide

Quote from Diesel

by Neotinea

i am sure this wasnt the case just to keep spirit of the game

we caught GO broke multiple times rules for some ppl but we cant do nothing about it, thats how GF works these days i guess

Tiz FR

Funny and truly saddening to see that Diesel's support ticket was censored, almost like someone knows that their choice broke a number of rules and does not want any incriminating evidence being released and the truth being revealed.

With the image being censored it brings into question the validity of the hit once again. It also brings the question to mind of what will happen when Zero and King are caught, as I would assume the battle would be massive and no CR would be generated. Therefore, I would then assume that the response of 'no CR, no combat' would come into play and all players would keep their fleets.

It would be great to have no favouritism towards players involved when hits like this were to happen, but we all know that is impossible.

Display More

This is why I believe to have a community that shares most their tickets - it would give an outlook on where GO set the line, if they go out of line, you can list of ticket ID to support your argument.

Quote from Zero Two

Quote from Apostle

The argument was we often have to dispute it just to get it right, when it shouldn't be.... unless it is the norm on both parties. I am curious what you guys put down in your tickets to see the other side of the coin. You know where to find me on discord if you are willing to share.

sure, and we had to go back and forth too. there were corrections on both sides, just like you’d expect when support has to manually reconstruct a fight of this scale. that’s not a flaw in the system, that is the system.

no need to read too much into it. everyone involved had the same process, the same path to dispute and clarify. and it played out exactly as it should.

Not saying I don't believe you but...I will believe it when I see it (for the sake of transparency)

It will give an insight for players outside of the loop of what they expect GF responds from on both sides.

Quote from bosne

However,

It is truth that this CR did not happen and it was MANUALLY processed, weeks after is was supposed to happen.

Does this means that all the other players in same or similar situation were simply robbed of their time and money? Maybe they didnt have enough influence or the person processing just didnt care that day... We have a funny situation now where some of us just get reply :"we cant do NOTHING about it" while others get 1. instant reactions when the fleet was frozen and 2. favorable outcome and fair fight.

Yeah unfortunately they went that route (manually processed) - part of the reason why it took a while is because the GF staff members/dev had a holiday week - so they were off work for several days. Moderators can't do anything at that time.

As for the "instant reactions" when the fleet was frozen, I talked to some of the moderators: you are allowed to reach out to them through discord for emergencies like this, but for any active ticket related details must be discussed through the ticket system.

Quote from Zero Two

thanks for laying that out, because honestly, it proves the exact opposite of what some are trying to claim.

support made an initial error, the defender provided valid evidence, and support acknowledged the mistake and corrected it. that’s not favoritism, that’s just… support doing its job. investigating, responding, updating the outcome accordingly. if anything, it shows the process worked as it should.

if that’s the foundation for the “bias” theory, it’s a pretty shaky one.

The argument was we often have to dispute it just to get it right, when it shouldn't be.... unless it is the norm on both parties. I am curious what you guys put down in your tickets to see the other side of the coin. You know where to find me on discord if you are willing to share.

Quote from Zero Two

Quote from Song

Game forge just preferred to have 4 spenders instead of one, that's it.

In some other cases this was irregular fight and nothing was done,ofc in case of Tizoc GF knows how much he needs to spend to get his fleet back.

I must say that Prongs and company tried everything to give attackers every single resource,good to know that at least someone finally listened proofs of Tizoc to get something in return.

Indeed massive fight,a lot of numbers, great teamwork,a lot of money spent on questionable queues but in the end with fight like this you can just say Congrats.

Tizoc sorry to see you down in a way like this ,when you just went to help but instead finished recycled.VFR

ah, the usual cocktail of speculation and salt.

let's keep it simple: nothing about this hit was irregular. nothing was done behind closed doors. no rules were bent, no favors pulled. the only thing questionable here is the effort to spin a clean hit into some kind of conspiracy.

everyone involved flew their fleets, took their risks, and made the hit happen. support followed procedure, just like they’ve done before in big fights where the script chokes. no more, no less.

the rest is just noise.

Display More

Well this speculation has some merits into it:

At first GF gave him their sim (using the old battle sim) as results of the battle - claiming that everything was accounted for:

1) Spacedock was accounted for but no ARP (Advance Recycling Plant (Lifeform building)) was included

- Tizzoc disputed that he has lvl 25 ARP

2) They double checked and then when "oh you have APR" but claimed he only had lvl 9 (even though no APR was accounted for from the previous response).

- Tizzoc disputed again

3) They used MMORPG as reference to support lvl 9 ARP claim

- Tizzoc provided additional evidence

4) They investigated it again and apologized that he was correct and gave out the correct results.

This wasn't his first rodeo that he been cut short but he had to dispute hard just to make sure it was done somewhat correctly.

Quote from Cathedral

"ACS split can be done as players want while all involved contributed."

You are correct, but this is a solo hit and adding a probe are not considered a "contribution"

Quote from -Arcane-

Apostle, you spout some hearty bullshit that I follow your board posts just for lols.

GG and Rain feeds off their tears.

hahaha! which part?

According to the rules and tickets - at most Rain can get is 500m (because probes don't count according to GO)

Quote from ms-h4x

What happened to the 500M res per week pulling limit? Gotta give credit for Tizoc's generosity at this point, spreading his love through the universe.

Rain account is just a throw away account for the top vmoders, Rain account been gifted around like hot potatoes to one of the top vmoders to take turns to monitor us.

Quote from ms-h4x

You had to be there and see it with your own eyes to believe it

Picture this: +1.6 billion ships were involved.

Quote from MikeGrinder6

Quote from Apostle

IF the battle was forced to put into play, expect tons of tickets reactivated to enforce all their missed crs 😀.

Is it a general rule now?

I remember having this issue years back and they passed the CR. I think it's more on a case-by-case basis.

Here is the thing, no CR was created. We expected consistency especially since last 2 similar events (when we were the attacker) it went :

"sorry, there was nothing we can do."

This time we were on the other side, so we are expecting the results to be the same since there was no public message announcement of what to do to address this when something like this happens again.

If they change ruling now before any sort of an announcement, it would seriously look bad on their part.

IF the battle was forced to put into play, expect tons of tickets reactivated to enforce all their missed crs 😀. Can't do one without doing the others.

At least make an announcement of how to proceed from this point forward before doing certain players favors.

It's the typical server lag with large fleet on the attacker. It happened two times on our end on solo, both times tickets were made (both tickets are closed and we moved on), both time the end result were the defender keeps the fleet, no CR means no DF. Attacker fleet get unstuck by GO and sent home with nothing. If the results changed now all the sudden.... it would be mighty suspicious.

This battle is 10x larger, Acs by multiple players, 15+ players lanxing every second and god knows how many playes are trying to steal the DF in the span of 3 seconds window. So.... it's kinda expected.

Ninja was well played, I started playing offensive and didn't account for the new additional lag that was put into the game. Slow probed and probed and got a delayed report leaving only a few seconds to read react. Enjoy the spoils. Starting to miss the old days when you get snappy results.

Quote from tihobor1103

Since I see some s.it talk here, and a lot of question what happened !
I wanna share so I don't need to respond to every single person..

Last 3-4 days my son is struggling with temperature nothing special, and yesterday hour before I wanted to go to sleep he came out of bed like an wet zombie
with temp. 41.4 or 41.6 , due adrenalin rush I cannot remember but still life threathening.

Next 3-4 hours we spend in ER. and the rest is history that's why I said thank God everything finished well..

So don't talk nonsence about mistakes or anything ( Song )
I had my phone all the time with me you think it ever crossed my mind to go on freaking game in situation like that ?

I had respect to all your falls and down!
So don't poke the bear without reason

Attackers enjoy the spoils and maybe we see us sometimes
GG / FR

Display More

I figured it was something happening in IRL, (it happened to me recently ) I hope your son recovers well

Hope everything's ok with you in IRL, FR if you plan on sticking around.

Diesel, you found an opportunity, and time was on your side Nice hit, thank you for letting me in and watch it unfold in front row seats.

Sweet hit, keep poking (or probing) the bear and you'll evidently get hit one way or another. FR Rain

Wow that gotta hurt, FR for the both of ya

You got lucky, by the time you get back out of vmode you wont be taking that risk

Nice hit! FR defender