-
Posts
290 -
Joined
-
Days Won
8
guerringuerrin last won the day on July 26
guerringuerrin had the most liked content!
Recent Profile Visitors
4.619 profile views
guerringuerrin's Achievements

Triplicarius (5/14)
347
Reputation
-
@hyperion https://drive.google.com/file/d/15vGn4ddL1nNRbtZeXqI5sqKLhm7zyNAt/view?usp=sharing This is another example. The game was originally hosted by @erictommy, and everything was going fine until several spectators joined at some point. One of them caused an OOS, but we continued the match for a few seconds until the simulation completely froze (the GUI was still responsive). levai was one of the active players in the match — I don’t remember if he left on his own or was kicked, but once he was out, the simulation started working again. When he rejoined, the same thing happened: simulation frozen, GUI functional. We decided to save and rehost the match, this time with me as the host. After everyone loaded in, the simulation was frozen again. Once levai left, it resumed. So we saved and hosted again, but this time replaced levai with RangerK — who happened to be the player that, when kicked or banned, allowed the simulation to continue normally — as if there was a problem tied specifically to that slot or civilization. What’s strange is that the simulation started failing when a spectator joined the game. Until then, everything worked fine and levai hadn’t shown any lag or other performance issues. A preliminary hypothesis is that this bug occurs when a player or spectator finishes loading the game or map. Why do I think this? Because the only thing I can clearly identify in common between a match just starting and one already in progress when a spectator joins, is the act of loading the game/map.
-
@hyperion https://drive.google.com/file/d/1BUfQS7Vyi9jUcRVY7M2IW_P4VFA_JUF_/view?usp=drive_link Sharing through drive bc file is too big This happened today. Unfortunately, I didn’t start recording from the beginning, but the behavior is exactly what we mentioned earlier: The game starts, the GUI is responsive, you can select units and buildings and issue commands, but nothing moves and unit production doesn’t start either. The suspected player gets kicked or leaves, and everything starts working normally. In this case, it was reza-math, who often plays in my matches. It could be a "false positive" and just a connection issue. But I think this is the kind of behavior we’ve been seeing more frequently lately. @Atrikcould you confirm this is more or less what you described? reza-math is using Windows 10
-
Team based border line style
guerringuerrin replied to ffm2's topic in Game Development & Technical Discussion
I think it's a cool idea, and would be nice to have a way to configure it so player can choose use them or not, or maybe assign each style to desired teams -
I've experienced this as host. Max Lag for observer set to -1 on my case. Didn't test kicking observers. I've experienced this with at least 3 different hosts that often hosts games, including me as host. Idk, will ask next time I'm not sure but I think it happens with both versions. Currently using 0.27.1 but i'm not sure if everyone is using it
-
It looks like similar behavior of game stuttering due to PC performance Are you referring to cases where no unit moves and no orders are executed, but the GUI and camera remain responsive? I’ve also noticed that in cases like this, hosts start kicking players until units begin to move again. But after the suspected bugged player rejoins, the game continues with exaggerated stuttering.
-
ResetSeed - A patch for fixed Seed and MapScript bug
guerringuerrin replied to Atrik's topic in Game Modification
@Atrik oh u might want tu change it's label in mod.json to describe what it does -
ResetSeed - A patch for fixed Seed and MapScript bug
guerringuerrin replied to Atrik's topic in Game Modification
6 lines of brilliant code, thanks @Atrik. plz PR for the next release -
Ohh lol ok I went to an art high school, does that sound like a good excuse? I was doing (5+(3)*7) + (8+(3.5)) / 3.5 Why? there is no why
-
+1 Yes but, please, get rid of that slash and put the attack interval on a new line. This is heresy against the sacred grid btw: where the 49 DPS comes from? my maths are not working there
-
I prefer this version with 1 stat (hack, pierce) per line I think this version is more difficult to read and to identify the different stats Also, the green color greatly improved its legibility, as it allows you to identify different types of values within the same block of text (just like the orange used for the stat name), and I think it helps associate the bonus % with the actual bonus value. I love it, @Atrik! Yeah, I'm not sure about this either @Dunedan
-
Yeah that's pretty much what we have been discussed with @Atrikin the previous messages. I do like more a vertical layout design rather than an horizontal you propose (as the vanilla is) because I think it's much more easy to read and identifies the different stats as can be seen here: @Atrikmaybe you could share a screenshot of this same damage tooltip of a melee unit so we can see how is shown? ( I'm at the cellphone rn ) About DPS number shown next to the unit portrait. I rather put the final damage of the unit instead of the DPS calculation as I find it a bit confusing. I guess some would say it's better to compare different units damage per second as different units have different attack intervals.
-
This is an example for the opposite point because in aoe2 there are lots of different hidden stats per unit that aren't shown. Its actually a great system to only show the basic stats of the unit, because showing all the stats would take up too much space and cloud out critical basic stats that can change with upgrades. I'd say going from this: To this: Is definitely an improvement in that direction
-
Wolf of 0ad Street - Market pump exploit
guerringuerrin replied to Seleucids's topic in Gameplay Discussion
Here: -
Wolf of 0ad Street - Market pump exploit
guerringuerrin replied to Seleucids's topic in Gameplay Discussion
Sure I guess one thing is to use the market another to exploit a vulnerability. I guess the important thing is this has been noticed and could be a fix of its mechanic to avoid this kind of exploits in the future