This post has been downvoted below -5 and collapsed, click here to expand
1. a Disarm Transport can nap a commander
>>>iam very angry
FAIL DEV
2. a Disarm Commander can Repair
FAIL DEV
3. A High Caliber Barrel Plasma Arty com with Napalm Warfare in Step.4.
In Morph Level 5 - the Napalm Removed
FAIL DEV
4. a Cloaked Com can Targeting with Ravens
I Know - its a Engine Err... but its not good.
Of course there is a way to fix this!
+0 / -13
|
|
|
Replay Disarmed Transport load my COmmander http://zero-k.info/Battles/Detail/25980922:47] Forever 5 coms dead:D [22:47] eray4561 and you did not get head hunter award.. why? [22:47] Xivender but your Transport was disarmes and he napped me [22:47] Forever cause its naping:D [22:47] Forever not killing [22:47] Forever i know Xivender [22:47] Forever :)0 [22:47] Forever buggs everywhereee [22:48] Connetable well disamr [22:48] Connetable is disarm [22:48] Connetable not emped [22:48] Forever yup Either this is a bug or I demand equal rights. Who is your reasoning Disarmed can transport my Commander invite but if the same can not jump my disarmed Recon? If that is a mistake must be corrected immediately - wenns no error, then I urge equality, then to the Jump Com can even if it is disarmed, jump.
+0 / -0
|
I brought the topic up a few times already. It's extremely confusing. Having to know which special damages affect what is just as much of a pain as having to know how much damage different units take from a weapon. This is what Starcraft does and one of the first goals of Complete Annihilation was to get rid of any such things. I'm not saying disarm is bad for Stiletto balance, it's just chaotic to have different damage types that all affect different things seemingly random.
+0 / -0
|
Wut. You can just go and fix the bugs yourself or not be so entitled to everything if you don't have the skills for it. Bug reporting can be done in a reasonable way as well. Sometimes I get the feeling that in your eyes developers of the game are some kind of evil beings whose sole aim is to ruin the game. Do you ever wonder how the game got to this playable state in the first place?
+8 / -0
|
|
|
Scuzzy has proven with his link that devs are evil.First, I am not a developer, and if I were one , then I saw it still does not as my task to correct errors that have made OTHER .Many errors that are newly come to have worked once . So something seems to have been changed by a developer without testing it adequately and conscientiously.And the resulting error shall I fix ? Think about it ! And how scuzzy further led , it is simply illogical that one and the same weapon causes a different "damage" in different units.Then something else. I have already criticized.To me it often happens as if the developers plan to organize without simply want to Good luck something . If something goes wrong, then it takes just a little .Many changes that were not wanted by the community, but were simply introduced . I have Anarchid asked in another Theard specifically for the reasons for each change .One answer he is to me still guilty until today.
+0 / -0
|
quote:
"Do not create work for other people."
Have responsibility for your changes/commit. Do not leave bug that require other people to fix. |
You might want to first look at the social rules before you as a rubbish write here. Why should I fix the errors OTHER? It has functioned ever! And where is the answer? Maybe firstonce his own front door before you try return me to teach here! Here again the site for you to read. http://code.google.com/p/zero-k/wiki/DevelopingAnd yet something is factual, except hot air?
+1 / -0
|
Well, that's basically saying "Don't create bugs". Yeah, that's how it should be done in theory, but it's far from any conceivable reality. Developing involves bugs, and some will inevitbly be found by others. The question whether or not a disarmed unit can load/repair/do whatever is primarily a balance concern. If it's unclear whether it's intended or not, you shouldn't be screaming "BUG" all over the place. You're free to voice your opinion about the desired state, but nobody really is obliged to adhere to your wishes. Lastly, you will not get any good results from being aggressive towards devs. That should be common sense, but still we see so many people communication their concerns in an angry (and childish) manner. And then they get more angry because the devs won't take them seriously. How surprising!
+2 / -0
|
delete ich reg mich jetzt nicht weiter auf. Sollen se machen.
+0 / -1
|
So now you resort to vendetta downvoting in other currently active threads? (check literally any post made by floris or me in rocko or defender thread) Edit: or this one lol
+0 / -0
|
Did I told you. Only hot air instead of answering. It's pointless. Makes her times. I've also been told that you should have the game firstonce in its foundations as possible error free and balanced before something like this posted on stream / green light and Co, otherwise the shot could go quickly backfires when half of the players has desyncs and other related errors. But you do it already.
+0 / -2
|
A textbook example of how to get your feedback discarded a priori. 72 hour forum ban for vendetta downvoting (and all your -1 votes to date have been deleted).
+6 / -0
|
As for the bugs in question: quote:
a Disarm Transport can nap a commander |
As Skasi says, a clearer rule on what disarm does and doesn't affect would be nice, but... transport is a passive, strictly non-combat ability, so BFD if disarm doesn't stop it. quote:
a Disarm Commander can Repair |
It can be given the order, but it doesn't actually do any repairing until the disarm wears off. If you're getting a different result, provide replay or methods to reproduce. If you want it to clear the repair order if disarmed, that can be argued (you might want it to proceed as repairs as soon as it can, rather than going off to do something else), but in any case you should have specified this to begin with. quote:
A High Caliber Barrel Plasma Arty com with Napalm Warfare in Step.4.
In Morph Level 5 - the Napalm Removed |
Fixed quote:
Of course there is a way to fix this! |
So can you supply said way to fix? If not, why "of course"?
+0 / -0
|
Its my fault @xivender is so angry with some bugs. I napped his com. Come on hes a good guy remove that ban, its way to much.
+0 / -0
|
quote:
I'm not saying disarm is bad for Stiletto balance, it's just chaotic to have different damage types that all affect different things seemingly random. |
It's not confusing to me. Disarm disarms. It does exactly what the word is. Your weapons cannot fire, and nothing more. The unit should be able to walk, transport others, repair, eat, sleep and knit sweaters. Here's an example of one "special thing" that did confuse me back in the old CA days. Shields blocked certain weapons. I could never remember which ones. Plasma balls? Not plasma balls? Lasers? I screamed and yelled until everyone agreed that shields should block all weapons ever made. And then they did except for some reason gauss sort of went through them for a while.
+0 / -0
|
1) Knows Lua 2) Can write widgets 3) Has written widgets 4) Knows where zk bug tracker is 5) Knows where #zkdev is 6) Knows where the bugs are 7) Bitches around instead of helping FAIL XIVENDER Edit: eh, this has already been resolved, why no lock?
+4 / -0
|
|
|
|
|
quote:
@KingRaptor Oh it's passive? Is it really? |
It does require a specific command to function, but once it's started it persists indefinitely without any commands, resource input (or output), or other interaction with the game. Nor would it be expected to IRL. Imagine hanging something from a tree by a rope. Rigging the thing up is an active process, but once it's done you can just leave it there, it won't do anything. So yeah, it's passive enough for this purpose.
+0 / -0
|
