fiki574

Personality type: Consul

The second request will be properly taken care off from now.

@John is this still present?

@MephistoRoss can you confirm that this is fixed?

Very weird, so it seems like occasional crashes...

@Bolrader could it be because of removed 1.5s delay?

Client sided unfortunately

This is actually client-sided problem, nothing we can do about it atm.

Seems like that difference/delay is actually intentional, will have to ask @Bolrader

According to @Bolrader's commit from few days, this should be fixed. Can anyone confirm?

Well then probably client behaving retarded as usual.

Oh hell yes, it burns time. It rekts time. 3h real time = 15min programming lmao Anyways, nice little project, good luck!

Well weird cuz only difference is: 3. Conditions = 4. { 5. PlayerHasGameLost {Player = "pl_Player1"}; 6. }, 17. Conditions = 18. { 19. PlayerHasGameLost { Player = "pl_Player4"}, 20. }, As u can see, there's ";" in first case, and "," in second but that really shouldn't cause problems. You can try changing the "," to ";" so it looks like this: 17. Conditions = 18. { 19. PlayerHasGameLost { Player = "pl_Player4"}; 20. },

If it continues to happen, i can fix it with the tool. It even says the line where the error is.

That's probably client sided, we're doing absolutely nothing to influence audio stuff at all.

EA has proven that they are not complete and utter douchies.

As far as I know, back in the day (3-4 years ago) when I was developing the server, the game was buy to play or was it?

I have a server emulator for Guild Wars 2 still lying around somewhere.

Never played the game, tho heard for it, but jesus this made me laugh....

Happy New Year. I will tend not to troll and repwhore as much as before.

I removed it for now.

When you roll a blunt and don't have a lighter. #mlg420 #problems