I'm working on fixing the flamer. Soon. Very soon.

Originally posted by Naifned⁻ᴸᴹᴬᴼ:

Originally posted by Crafting..... BOO!:

No, you don't. Just connect to our servers, it should download the files that are required. That's all you have to do.

Well yeah the plugin actually will download when you will join.

Actually, all you dl when you join the server is the models, textures, and sounds. All the logic for the weapons is handled by the server. I'm now imagining what would happen if servers could download/execute plugins to players *shudders*

Not the owner, but the owner said many times that an x10 server is planned. When that'll happen though, I have no idea.

Originally posted by a Larry with Mustacho:

Originally posted by mnster:

hello i cant see fp models help

Originally posted by Crafting I Tf2W:

All Servers have been FIXED!

They aren't 100% fixed, it's more like 75%.

Added a known bugs section to the main post.

Originally posted by Crafting | cTF2w:

Originally posted by Thrynity:

but when their is like 5 player, better decrease super shoot spawn chance

I will see if I can, Stop that Tank mod is a outside plugin, so it might not be possible

Remember you have a team a coders that can help you. I had something in a private plugin that did certain things depending on player count. I could easily change that to blocking giants.

Originally posted by Orion™:

~Important point: Medic and EVERYONE with an item that gives health regen ARE IMMUNE to Infection. ( ͡° ͜ʖ ͡°)
There, Infection is now nerfed xD

Didn't I fix that a while ago?

Originally posted by Thrynity:

Originally posted by Orion™:

Tf2's problem, not ours.

why does the old version was working well without doing mini-crit due to fire

Another problem, it's with the hook cloak, you have to reactive it sometime to stop hook
sometime it's a problem for ninja trick

I'm aware of the issue, been looking for solutions. May have some possible fixes.

Originally posted by The655:

Originally posted by Theray070696:

You downloaded the models from my forum post, right? I check for the attribute when a custom weapon is spawned, after all attributes are given. Though, you got me thinking. Do you have another custom weapon equipped besides the amplifier/node wrench? If so, I may know the problem.

No I dont.(AND MAYBE THE DELAY IS ACTUALLY CUSTOM MODEL DELAY,NOT WEAPON, SORRY)

No, it's weapon delay. There's a forward in cw2 which is called once a weapon is done being spawned. That's what I'm using for the check.

Originally posted by The655:

Originally posted by Theray070696:

I check when a custom weapon is spawned, I originally did it on resupply but it caused this very issue. Checking custom weapon spawn avoids the issue. WAIT! Are you saving your weapon? Not saving it might be causing this, as you are not given the amplifier wrench when you resupply, thus causing my check to destroy the amplifier, as it's no longer detecting the amplifier attribute. Repair node might also have this issue.

I save it,but there delay from the actual weapon model and the custom.Maybe because of ping?Since I didnt see the actual model when I do some attribute testing in my server.

You downloaded the models from my forum post, right? I check for the attribute when a custom weapon is spawned, after all attributes are given. Though, you got me thinking. Do you have another custom weapon equipped besides the amplifier/node wrench? If so, I may know the problem.

Originally posted by The655:

Originally posted by Theray070696:

It shouldn't be doing that, I remember testing it thoroughly so that exact case wouldnt happen.

Maybe the equip other melee destroy attribute destroy the building?Since you load your actual weapon back before the custom weapons.

I check when a custom weapon is spawned, I originally did it on resupply but it caused this very issue. Checking custom weapon spawn avoids the issue. WAIT! Are you saving your weapon? Not saving it might be causing this, as you are not given the amplifier wrench when you resupply, thus causing my check to destroy the amplifier, as it's no longer detecting the amplifier attribute. Repair node might also have this issue.