engineers

[karamazovapy]

Those files aren't included; I can't post them in the repository because they aren't mine. There are instructions for how to get them yourself, though...

wait, what?

Compiling on a windows machine requires a set of files that go in the Win_Include_do_not_distribute folder. Watusimoto doesn't have a license to host and distribute those files.

[watusimoto]

Microsoft files required for compiling under Windows.

[ZoombeR]

ah, but not needed to compile under linux then. i guess it wont affect my work then.

[watusimoto]

Correct.

The reason it was so cumbersome on my Zap! server was because of how I patched the server, there was no way to add new menu items and such to the client side end, so it had to go through the chat via commands.

It should certainly have a better implementation in Bitfighter if done correctly.

[watusimoto]

I'm open to any suggestions. Currently, as implemented, you'll enter the chat commands /engf or /engt to create a ff or turret. This is a tiny bit less janky than it sounds, as there is a special "command chat" mode that is activated when you press "/". But only a tiny bit.

Given the original design was for it to be a selected module, ideally shooting would cause the held resource item to be created. Using the module would toggle between forcefield and turret placement.

[watusimoto]

I like the idea of activating the module to use it -- perhaps repeatedly applying the module without moving would toggle between ff and turret. Once you moved, your choice would be finalized.

[karamazovapy]

I like the idea of activating the module to use it -- perhaps repeatedly applying the module without moving would toggle between ff and turret. Once you moved, your choice would be finalized.

Or you could map Module 1 and Module 2 to forcefield and turret once a resource item is collected and mountable.

ZoombeR brought this up on his server (I had forgotten all about this), but in my patch to enable engineer mode, I also patched ForceFieldProjector::onEnabled() to change if(findObjectLOS(BarrierType, 0, start, end, t, n)) to if(findObjectLOS(BarrierType | ForceFieldType, 0, start, end, t, n)) to make it so forcefields cannot overlap.

This may be something you want to enable when engineering is active, either through a server option or level-specific setting (or scripting).

[watusimoto]

Yes, that's a good idea.

[watusimoto]

It sounded so easy... It's done, but it was a tad bit more than one line of code!

[ZoombeR]

if we continue to use /engf and /engt, why not change those to /bt and /bf. If you do a search in the zap folder, you'l find they keyword there. I think its in EngineeredObject or UiGame, and down near the bottom, the keys required for the input command are shown.

[karamazovapy]

Wow. Yes. Old. Done.