Are you shure U want to deconn the Reactor, Dude? Dialogue

[Chrysops]

What I had in mind was a dialogue like this :

 Are you sure you want to deconstruct the overmind?  Your team will not be able to evolve etc. etc. until a new Overmind is built.
  Yes, Deconstruct.
  No, I decided to live.

It would prevent accidental decons when button mashing.  It might also dissuade some deconners who are just not very bright.

But maybe you could get rid of some of the other dialogues to combat dialogue glut.

I think it is more fun when the aliens have the upper hand so I hope 1.2 isn't too balanced. . . Tyrant should have lobster claws to pinch off people's heads, scorpion tail, and fireballs at S4!!!

[n00b pl0x]

sage sage sage

[kevlarman]

sage sage sage

omg i lol'ed so hard. you trying to keep the forums clean? now i've seen everything.

[n00b pl0x]

im not trying to keep it clean, silly, but im glad i could be of service to you

[Caveman]

@OP
You really must suck at hand-to-keyboard|mouse-coordination if you need such a patch to keep from "accidental" decon.

[techhead]

I moved decon to the 'R' key, and reload to the 'E' key. Keeps that dangerous button away from my WASD. It also makes reloading easier.

[BULLSEYE@linux.be]

they just need to make another way to decon something so it can't happen by accident like nading ur base -_-

[Caveman]

Nothing can be made idiot-prove ...

[BULLSEYE@linux.be]

well they already made !denybuild and !designate

[tuple]

mark deconstruct

 nuff said

[Vector_Matt]

mark deconstruct

 nuff said

But that doesn't prevent a griefer from marking it, and building it half-way around the map from the humans' base.

[n00b pl0x]

Nothing can be made idiot-prove ...

proof

[mooseberry]

mark deconstruct

 nuff said

And it gets annoying when you're not a deconner.

[n00b pl0x]

actually, its much better when youre not a deconner, unless of course youre on one of the shitty servers that dont have the hp bar of the structure toggle when you turn mark deconstruct on and off

[mooseberry]

But it gets kind of annoying if you want to say move a turret 1/2 of a foot.

[Nux]

Unless you're talking about the stubs that seperate the humans from the ground, feet has no meaning in the tremulous realm. Try using 'units' or perhaps 'the length of a dragoon' if you want to be accurate.

Building a new turret in a similar position to the old one is not a problem as it allows you to do it. It's when you try building a node where a turret is that you get an idea of the trouble 'marked decon' can cause.

[kevlarman]

Unless you're talking about the stubs that seperate the humans from the ground, feet has no meaning in the tremulous realm. Try using 'units' or perhaps 'the length of a dragoon' if you want to be accurate.

Building a new turret in a similar position to the old one is not a problem as it allows you to do it. It's when you try building a node where a turret is that you get an idea of the trouble 'marked decon' can cause.

1) that's a known bug that will be fixed by the time 1.2 is out
2) would you prefer markdecon before my patch to allow moving a base around?

[/dev/humancontroller]

I don't know why you want a tutorial modes. Let's just disable that, and disallow n00bs to join public servers. It is possible. Everyone must walk through a single-player training session, where the most important stuff is explained and tought, especially building and deconning. Once that is done, the client sets something like cg_me_r_pro to 1. And tells you how to set it manually in case you've lost your cfgs, or consider yourself a pro. What about that?

[Nux]

1) that's a known bug that will be fixed by the time 1.2 is out

That's good. I'd like to see what the final result is like. I have worries about the way in which marked buildings disappear when the new building overlaps them. Though this helps in one way it can cause trouble in others. Given that the system is at least in part intended to help prevent deconners from doing their dastardly deed, how does the system handle an armoury being built over the only two nodes (which have been marked for decon)? Does the system not allow the last node to be deconned unless it will be replaced by another? Does it do anything to punish those who decon all but 1 node (which is almost as bad as having no nodes when large queues are concerned)? Can the armoury be replaced by a repeater? Questions like that I'd like to find answers to ^^.

2) would you prefer markdecon before my patch to allow moving a base around?

I thought it already allowed this. Can you clarfiy what you mean by "moving a base around".

[Eeeew Spiders]

As for deconning and bad building, you could also make it such that you only allow known players (lvl 1) to build, and that unknown players (lvl 0) have !denybuild automatically.
This ofcourse only works when servers are maintained like the wrath server for example, where every regular player has lvl 1.

[DHRUVINATOR]

Their wont be a s4 live with it ! Even though i want it .

[yetshi]

mark deconstruct

 nuff said

But that doesn't prevent a griefer from marking it, and building it half-way around the map from the humans' base.

easy enough.

when marked the screen displays:

"Reactor marked for deconstruction by <name>" right in the center of the screen.

[kevlarman]

mark deconstruct

 nuff said

But that doesn't prevent a griefer from marking it, and building it half-way around the map from the humans' base.

easy enough.

when marked the screen displays:

"Reactor marked for deconstruction by <name>" right in the center of the screen.

Code: [Select]

Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
<half the server drops>


[Nux]

well the first few messages can stay, then if it goes further than that (in a short space of time), display

Code: [Select]

<name> is amusing himself with the Reactor

[yetshi]

mark deconstruct

 nuff said

But that doesn't prevent a griefer from marking it, and building it half-way around the map from the humans' base.

easy enough.

when marked the screen displays:

"Reactor marked for deconstruction by <name>" right in the center of the screen.

Code: [Select]

Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
Reactor marked for deconstruction by <name>
Reactor unmarked by <name>
<half the server drops>


<name> Denybuild by console after the 3rd time.

[Nux]

I prefer my solution. It's similar but I included a mention of time-period and didn't make the result permanent for that match. Your suggestion is sort of like muting people for the rest of the match for flooding after they've said their fifth thing of the match (regardless of the many minutes the utterances were seperated by and that they were accidental anyway).

[holyknight]

I moved decon to the 'R' key, and reload to the 'E' key. Keeps that dangerous button away from my WASD. It also makes reloading easier.

nah won't work for me. I'm just too accostumed to the R button after playing CSS for so long...

that dialouge will make you feel bad... what if you are told to do it and you want to live, so you say no and get chastised and banned?

And what if you hvae to decon really quickly but is delayed by the "yes, no" dialouge.

[Nux]

Solution: The dialogue pauses the game.. FOR EVERYONE. That's less disruptive!

Unless you're suggesting forcing this dialogue upon everyone, this can already be done with some cleverly placed binds.

[Wootsicle]

When someone decides to decon the OM/Reactor, it should automatically notify every person on the team and allow them to deny the person's ability to do so. The vote should stay on their screen for 10 seconds, and if more than half the team votes to deny the ability to decon, the decon should fail.

Just a nifty idea.

[ShadowNinjaDudeMan]

But what abou8t these really quiock huried decons and moves?

The god ones,t he, sav ethe match ones?

There wouldnt be any.