[CLIENT] Nodes 1.0.2 (Page 3 of 7)

After playing nodes 1.0.1 for quite some time, I have some suggestions.

• A vote for deconstructing the reactor
  Usually when the reactor sends out messages of it obviously being deconstructed, I say: "Who the hell is deconstructing the reactor?"
  *silence*
  Me: "..." *fixes reactor* *annoyed*
  Having a vote sent out only to the team that wishes to deconstruct their reactor and a message of who called it and their reason, would help a lot.

• Team-member's hammer collision off when fixing buildings.
  Super annoying when you're trying to fix something and you keep on accidentally hitting your tee-mate.

• A special sound for when a spawn point is built
  Since they're a vital importance to have they deserve their own sound.

• Fix teleport bug
  When someone tries to fix a damaged teleport it won't stop teleporting him from one tele to another. Kinda annoying.

• Fix explosion?
  When you build or repair a building, it have a explosion effect in the bg?

• Repeler
  A gun or building simular to shield generator (but with longer recharge time), that would send out a shock wave sending enemy tees flying (even if they where stationed by hooking the ground) but having no effect on tee-mates. The main reason for this is the time period before you get tech level 2 is a very hard one. Tees keep on kamikaze-ing over to your base. It would help with getting those little buggers out of your hair so you have more time fixing what they've tried to destroy.

• Doors?
  Conventional appearing and disappearing unhookables are cool but they don't do back and forth from closed to open. Just a thought...

And a new buff idea:

buff: Bubble
buff description: The holder has the option to create, lets say 3, bubbles around any object or in thin air at will with the aim and click of the mouse. Bubbles are allowed to appear around the holder, his tee-mates, his team's buildings, enemy tees, but perhaps not around enemy buildings and not in solid objects since it'd serve no purpose. The Bubble is simular to a shield but not as powerful and stays on an object for quite sometime if no damage is done to it. Instead of reflecting projectiles, it absorbs enemy and turret projectile and damage (up to 5-10) then goes away when its limit is reacted. If put over a tee, the tee can not shoot others until the bubbles damage limit is reached. When stationed in the air, it wouldn't effect tee-mates or enemy tees if they walk or hook though them but still absorbs damage.

graphical effect: The holder has a different skin or special hat. A yellow or white bubble expands into existence when the holder clicks. Energy-like-absorption-effect when absorbing projectiles. Quickly fades out of existence when its damage limit is reacted.

The following idea came up my mind: what about creating a team edit: vote if so wants to deconstruct a building?

@all: I'm reading all your comments and suggestions carefully, but I do not have the time to answer them.

I don't understand your idea... Perhaps you need to reword it.

Oh, I get it. Inset of the conventional, you stand on the teleport for it to teleport you, you must hit a button for it to tele. That could fix the issue. Nice idea Elite!

I love the idea
Although non-voters can be quite the nuisance so I suggested that verdicts are based on those who actually voted. Say there are 12 blue players and a reactor deconstruction vote is called. 4 yes, 1 no, and 7 undecided. Normally the vote would turn out to be 33% yes and 8% no; resulting in nothing getting done. However if based on those who actually voted, it would turn out to be 80% yes and 20% no; resulting in the reactor's deconstruction.

This gets more complicated by the second
How about "Vote for Deconstructor"
Make a certain player on your team privileged to have the reactor deconstruct ability.
A person who the team has the most trust.

afaik you can repair teleporters if you stand near them and repair them from there.

Regarding question 1:

Try to add that stuff to the config:

sv_register 1
sv_max_clients 16

If you like more then 16 players you MUST change the masterservers as described in this thread (otherwise you would get banned).... but if you change the master-server you would just get visitors that even did this step at their client manually. So until next release I think it's better to keep it at 16 player max.

Regarding question 2:
A classic regarding the "wrong password" stuff is that you did not enter your password between quotes "" and made a space after your PW. Sou you enter it - get wrong password... disconnect... doublecheck in the config to get sure (don't see the blank space for sure)... try it again and get again wrong password. That could be annoying

Greetings,
Mo(2)

@Mo2: The kottizen server is not ready yet, we must wait, it will be in the future Aaand to tell you the truth, I rather wait then earn me a Second Ban

Question 2: Come on this is my 11-th server Think I'd make that mistake? Well mb it was temporary, but I rechecked and it's ok now, everything in the cfg is spotless

Can't wait for the special master for nodes only, the clients shouldn't really mix up, very kind of kottizen ^^

I've made a (currently still beta) map that can hold more then 16 players without every tee is hooking on the other one but even reduced the max_player limit to 16 right now.

The ban would be with a good reason because you can crash normal TW-players with your server afterwards. I had already more then 16 players on my server and was informed by heinrich5991 (DDRace developer) afterwards regarding that issue. Currently there are not too less Nodes-Servers. The servers that are currently online seems all to be well connected (from europe).

In my opion Nodes currently needs:
*) More players!! (btw. even if I would find it cool to host more then 16 players if we fully switch to kottizens 32-client server lesser would see that new stuff in the server-list - so advertising in serverlist would be lower)
*) More bugfixes (look at old 0.5.2 "C"-DDRace server versions...they are pretty stable and got protection against such multi-IP-voting-crap, ...)
*) More cheatfixes (self-destruction-protection that works even in hot moments but don't bother fair players. Info is good but too less)
*) Servers that are placed in Asia, Afrika, US ... (not for me... I would not need it for myself - but I even played CTF on russian servers). Nodes is less ping-critical then CTF/DM (you can have a lot of fun with just building stuff) but imho more ping-critical then DDRace - because building is just one part of the game (so you have to "fallback" to normal DM/CTF-like gameplay).
*) Maps that was balanced and bugfixed:
nds_sunlitForest got tiling bugs (near blue reactor) - the blue reactor is placed bad and it's more easy to play red (but even with that bad points many seems to already like it so it's at a good start-position) - supremacy got FPS problems even it looks good (I would not switch all the time between high and low detail just because of one map). Hill and nodes1 are too much identical and are just "ctf5-clones"... one clone should be enough. Facility looks good at first but is pretty confusing if you play... which tiles are backround and which are solid (I would recommend to rework at least the background - it remember me on some city maps).

Optional:
*) Possibility to play normal TW with Nodes-Client: I did not read the source of the client so far. But if there is no good reason to filter for "NODES" I would recommend to take it out and give the possibility to make the client a one fit for (mostly) all. Probably we can make a fine installer (InnoSetup for example would be easy) and push Nodes-Clients as a standard afterwards. At least I would recommend to filter for "NODES*" so even testing or modified versions could be tested or run and even be found by (currently rare) nodes-players. After I put the "min-score-for-selfdestruction" into my svn-checkout-source I thought about calling my gametype different (Nodes+ or whatever - to show others that it's a hacked version). But it does not make sense if I get just myself as player afterwards. On the the other side I've already made too much experience with such team-building-killers in a few days to take ot out without protest (currently it's well working).
*) Better scoring for "engineers". Even if you help your team a lot because you are defending and keeping your stuff alive you would not get any note in the score-list regarding that. Remembering to such games as "TFC" as engineer you could even be in the top of the scorelist if you built a well placed evil sentry-gun that took down many enemies. Nobody notices regarding such stuff in nodes. So you can help your team to win but the scorelist give you some minus-points because of some bad self-kills. And on the other side I found some positions where I can respawn quickly and kill one enemy after another (and die lot of times in between) and run on top of the score fast. Nodes is a team-game. So I don't really need a scorelist at all. But if there is a scorelist it should be at least a little bit more fair to all your team-members. One that is just on a self-destructing mission and hurries to the enemies again, and again and again as long one building falls would get a good score but the guy that is keeping your reactor alive is a looser in the scorelist.

Btw. I would thank all guys that developed Nodes so far. Even it's buggy and somewhat unbalanced it already makes a lot of fun. 

Greetings,
Mo(2)

Cool. A brand new OS called widows that uses just 62bit? If you can get SDL gcc and python for it you have maybe luck. TW is open source so try to compile yourself on it.

Serious: You should not have troubles to run 32bit TW on your 64bit windows - It's more important that you get a PC that includes a useable graphic-card.

Greetings,
Mo(2)

You cannot see your own server into the Internet tab, this is also true with the pure versions of Teeworlds.