Warzone 2100 Forums

Not completely sure, but I think the tech level selector is moved in with the rest of the game settings now, after selecting the map instead of before. There might even be a T4 now. It shouldn't be removed, at least.

They should show as regular maps. When running from that branch, check Entropy in the 6p map section or WaterLoop in the 10p map section.

I meant to compile from Github, since only that branch knows how to open game.js maps. There might be automatic builds somewhere though, not sure.

There's two example maps in that pull request (see the game.js files). To see them you have to compile the branch, though. The two example maps are a bit different each time you play and/or click the map preview.

Probably not what you're looking for, but with https://github.com/Warzone2100/warzone2100/pull/1019, it's possible to make maps with a regular text editor.

Was it a NullBot ally attacking you at the end? If so, it's this bug: https://github.com/Warzone2100/warzone2100/issues/1026

Think AIs are rather unreliable in general. Think the BoneCrusher AI is supposed to play the least badly.

The blend factors for all terrain types should probably sum to 1, so it doesn't give light/dark bands.

That note about breaking the game is probably from the old days when Warzone 2100 was coded as an RTS, and a long time between frames would mean projectiles or droids would be more likely to miss where they're trying to go. Now there are always 10 logical frames per second, independently of the grap...

At least it doesn't say “WE DON'T ACCEPT PULL REQUESTS” on GitHub in caps like it used to (maybe with some note about preferring Trac tickets with patches attached for some reason I didn't really understand).

Might have been replying to a now-deleted spam post rather than reviving it, not sure.

If you put a CB sensor or tower near things that are getting shot at by the enemy artillery, then your own artillery using the CB sensor can see and target the enemy artillery that's shooting at you, no matter where it's shooting from.

A long time ago, the limit used to be 8 players (7 players + scavs or 8 players without scavs). To increase the maximum, just change MAX_PLAYERS in lib/framework/frame.h. Think the main reason why it ended up set to only 11 (10 players + scavs) is so that there would still be enough room in the GUI ...

In graphics frames between game ticks, their locations are interpolated. My guess is that the initial locations don't have a sensible height coordinate. Looking at the code seems to confirm this. It's probably my fault, sorry.

Untested patch: https://github.com/Warzone2100/warzone2100/pull/719

I think I've seen that occasionally.

The bug tracker is dead, and substituted by the Github issue tracker.

Don't know, but if you're stuck on Windows, then try updating your graphics drivers in case it helps.

Search found 608 matches

Re: T2 & T3 Unavailable for Skirmish

Re: Help, to create map in linux

Re: Help, to create map in linux

Re: Help, to create map in linux

Re: Help, to create map in linux

Re: Is this warzone heavier than the original?

Re: Models by MaNGusT (AR)

Re: What's the latest version with a playable Campaign?

Re: Suggestion: Remove the "stop with the silly ideas & suggestions" thread

Re: 2.3.9 - Saves Won't load from Alpha 11

Re: Sensors - something changed? Lets clear the use (last mission)

Re: The project to a 12 players support on Warzone

Re: A problem and a not-working bug tracker...

Re: A problem and a not-working bug tracker...

Re: i just recently downloaded the game