smiley

Something like this? <ResourceGatherer> <Modifiers>[]</Modifiers> </ResourceGatherer>

You can probably symlink to 68 as 67 and run the game.

Or make the produce abstract and call it something along the lines of "forge output", but not as bluntly and merge attack and armour into one secondary resource as you called it. Rather than a spearman costing 5 armour and 7 spears, they would cost 12 X.

I recall some days ago when there were Devs who played the game almost on a daily basis on SVN along with lobby players. The last time I was part of that, that led to the discovery of several issues. That of course was possible since active developers were so to say direct liaisons to the active multiplayer base and quite frankly part of them. No need to dwell on who they were and what happened to them.

Hot take, but end user software is meant to be developed for, well, end users. You can have the game be a fancy tea party for Devs, but if there are no end users, it's all for nothing. Something to keep in mind before blurting out "you aren't entitled to anything, we made this without getting paid, take it or leave". You might get what you wished for. Developers are entitled to end users, not the other way around. That is of course, if the objective is to build a solid community around the product.

Since the message was posted, unfortunately, irl took up all time. If you have code, feel free to post for review. I might be able to suggest some things.

Unix timestamps of course. A game titled "-2208988800" is sure to arouse some curiosity.

If I recall correctly, it wasn't discord being evil that derailed the whole thing. I assumed the concern was that IRC users don't get to agree to the evil policy in the first place. If the matrix bridge didn't exist, there is nothing against discord. All participants would have agreed to terms.

You misunderstood what Vulkan is. Vulkan is a new framework that is an alternative to OpenGL (* important to note it's not meant to be a replacement). Rather than the monolithic state machine OpenGL is, Vulkan implements a completely different pattern where you can squeeze out even more performance since Vulkan doesn't suffer from most of the overheads OpenGL does. I noticed that drawcalls in Vulkan are pretty much negligible overhead whereas in OGL, it's a nightmare. Since 0AD does not have instanced drawing, switching to Vulkan will actually help a lot. Then again, who's got the time to write a new rendering backend.

No. What you want to do is entirely supported.

So does your router. A compromised machine forging L3 packets would do more harm than a DoS ever could. Your router would be blindly routing all of them.

I get the theory behind it of course. Merely remarking the absurdity of the solution.

Who does that?

Seems like you don't need to host to incur the wrath of the DoS gods.

Basic enterprise grade hardware can withstand a DoS. A DDoS on the other hand, while expensive to launch is also expensive to mitigate, which is why you rent virtual servers on the cloud. The previous thread regarding this topic has somehow been locked down now, I am not sure if its global or just for me, but I can't reply to that in my own discretion now. I would want to be once again the bearer of bad news, but I no longer care and its getting old at this point.

There are two functions exposed to JS in the lobby. You can use these functions. See, https://github.com/0ad/0ad/blob/d15248f72db6116fec09fe11b50f55a39aba5917/source/lobby/scripting/JSInterface_Lobby.h#L44 void SendRegisterGame(ScriptInterface::CmptPrivate* pCmptPrivate, JS::HandleValue data); void SendUnregisterGame(ScriptInterface::CmptPrivate* pCmptPrivate);

From your graphs, it looks like the router is being overloaded with packets, not necessarily bandwidth. A million tiny packets on a home router would still starve it. All this need in an interface to do. Alternatively, proxy the requests done through the lobby. That way, the DDoSer would need to connect to the host before he can get a public IP. Basically, don't advertise public IPs, just relay them to the actual host when they want to connect.

There is nothing that can fix losing 90% of one sex and the gene pool that goes along with it. That's just extinction.

I doubt home routers will have that capability. I would assume who ever does this would know how to to actually knock out a router. DoS detection is a complex problem. Usually, DoS attacks starve out the end host, not the hardware in between. Home routers with limited memory aren't hard to starve unfortunately. Find where it comes from, find what it sends, null route all trafic that match the both criteria. You aren't running a server, you can safely block out entire regions.

See if the game shows up on the LAN discovery menu, maybe the IP is wrong. Regardless, rather than going through the public network, playing in your LAN would be better. Menu -> Join Game -> Search LAN for Games.

I made that mod and posted it on this forum sometime in 2018. Performance was alright, nothing intensive was needed to be done. I am not sure whether defining quadrants will be an issue. What I did was take the relative rotation of two entities in attack, translate for attack direction if needed and just take the circle quadrants based on angles. I recall having to revise it to only take the relative rotation of attacked and the attack, because missile attacks can have vastly different attacker and attack orientation depending on projectile speed.

Can't even do that. Replays have nothing but commands. There is pretty much zero uses for these replays. Unless of course, 0AD itself is bugged and DoSing clients.

Not really. You cannot have spaces in a URL. It should be encoded as %20, but browsers today display it as a space. If you open the browser console, the requests themselves still use %20 and you can see it as such.

Changing the terrain from a grid to a polygon map or something similar will allow for some remarkable art. If you can make it in blender, you can make it in Atlas kinda thing. Even allow for importing actual meshes to Atlas. Fun to think about, not fun to implement. Basically involves overhauling the entire terrain renderer.

None of them are well known for their amazing UI/UX. I find it unnecessarily verbose and lengthy. And in my entire life, I have never found anyone who got confused by AM/PM. But by my own logic, I should be arguing for 24 hours. And I fail to see how moving from one arbitrary standard to another improves things. That's the point of locales. It's completely subjective. So the best thing to do is just have the default be the industry standard, which is also what all software and operating systems use out of the box. And maybe ask IPB devs to implement locales how everyone else does it. Regardless, this is not a hill I am gonna die on. I am pretty confident I can parse out dates in any locale.