Loading in durring PvP. My take and how it "should&quo

[Novall]

Ok, reading other replies and talking to my members who were involved. If your going to run into the starport and wait for a fight, wait till the person physically moves. I'm not saying wait to be shot but you need to wait till they atleast do something like look at you, start walk/running, ect.

I understand heat of the battle and all that, but lets not lose our heads. Lets be fair about how all this goes down. Unfortunately guild war TEF doesnt give you the pause for loading in like GCW has. Its probably a bug.

Anyhow, this is more of a respect and common sence issue then anything else. If you wouldnt want to be load killed, then dont load kill someone else.

[toront]

Also, if several people are loading in, or you know OOC that several guild members are coming, don't load gank and jump the guys turning red first. Let everyone load in, both groups be what they are, then go at it.

If we want to look at immersion, it's not likely that everyone will be coming in completely staggered, but we can't account for things like individual computer load times and such, unless we all agree to hold off.

We're red to each other all the time, what's an extra 10s?

[Dwilah]

Why not take the extra ten seconds to hide behind some barrels or something? There's usually stuff like that at starports and there's ample opportunity to increase the immersion in ten, thirty seconds rather than decrease it.

[Ekade]

The funny thing about the scenario.. we were actually leaving.. heading to Dohrian because that is where the RP was taking us.

Kirt loaded as is Isleh was out doing something, and Vreese was trying to trade me a swoop because some @#$$%% NPC's had just blown up my BARC 1500m from where we were (gawd I was so pissed about that). The last thing I needed was to be without viable ground transportation. When outgunned, movement is your only defense.

A blast from Kirt's weapon literally hit the wall behind my toon in the little room where the travel terminals are. That's how I knew we were under attack. I hit escape several times to close all the trade/inventory/travel windows I had up. Then hit 'Tab' to target an enemy, saw that it was Kirt. *heart poounding*.. it was definately a holy sh-- moment. He TOTALLY surprised me.

Isleh was at less than half health, later review of the combat logs reveals she took dmg 4-5 times from Kirt before he took any in return.

I charged out and started attacking.. then we dropped Kirt. We *had* to respond to his attack.


Then the other folks loaded in, which I already described.

[Ekade]

Also, if several people are loading in, or you know OOC that several guild members are coming, don't load gank and jump the guys turning red first. Let everyone load in, both groups be what they are, then go at it.

If we want to look at immersion, it's not likely that everyone will be coming in completely staggered, but we can't account for things like individual computer load times and such, unless we all agree to hold off.

We're red to each other all the time, what's an extra 10s?

That makes sense, and I agree. However, part of the immersion is *not* knowing the enemy was coming, which we did not. I assure you, I jumped in my seat when Kirt surprised us.. I was immersed.

We can do it both ways. The element of surprise is fun, but so is having an arranged encounter. I guess we should use whatever is appropriate for the flow of RP at that moment.

This is where having a GM set up the encounters would be useful. One interpretation of "fair and realistic" is better than 6-10.

[Isleh]

I am not happy that others were upset. This is suppose to be fun. Not being fun is what chased me away from PvP in the first place.

As of now we've run into a few problems. For the most part. all of them have been resolved fairly so far. This one can be as well.

This issue begs the following questions the needs to be answered and it also applies to Kashyyyk's loading areas ( and Trials too when it's available ).

How do you tell when they are fully loaded? When they open fire? When they move? Some spatial signal?. What should the signal be? There are another problems. These areas are prone to LDs as anyone who has seen someone or themselves just stop and stand there on the threshold of a starport entrance for a few seconds. What then?

Also, waiting for the other group to fully load? Yes? No? If a general call for help was given asking anyone available of an opposing side arriving to show up, would it be fair for the other side already there to sit there and do nothing as, one by one, more and more of the opposing side trickle in?

Maybe at Loading Zones:

When arriving, You are not there until the last person coming has arrived and is fully loaded.
When departing, You are not there when the first person in your group has departed.

The loading side is at an extreme disadvantage. They should be the ones who decide when combat starts.

[KirtViza]

I loaded in and was all YES ISLEH ALONE! but then when I KDed her and moved closer the door to the starport terminal opened and I saw Ekade and Vreese in there, "F@CK" was all i knew and I started to move but Ekade had me.

Adun, and Crystal were both in my group loading in, Adun on Vent and he said clearly he loaded in incaped, and crystal said it in Groupchat.so they were heated about that, I knew I was out cause I was fully there but the two of them were load incaped. So we decided on I came you Kncoked me out befor I could retreat and took off cause your not stupid and knew more owuld follow when my com goes dead .
I would say best way to fix this problem is to pretty much in spatial go (( here)) or somthing to alert that you are there and no longer loading, the Bug novall refers to is probally the problem since GCW you get a min i believe after loading.

[Isleh]

The funny thing about the scenario.. we were actually leaving.. heading to Dohrian because that is where the RP was taking us.

Kirt loaded as is Isleh was out doing something, and Vreese was trying to trade me a swoop because some @#$$%% NPC's had just blown up my BARC 1500m from where we were (gawd I was so pissed about that). The last thing I needed was to be without viable ground transportation. When outgunned, movement is your only defense.

A blast from Kirt's weapon literally hit the wall behind my toon in the little room where the travel terminals are. That's how I knew we were under attack. I hit escape several times to close all the trade/inventory/travel windows I had up. Then hit 'Tab' to target an enemy, saw that it was Kirt. *heart poounding*.. it was definately a holy sh-- moment. He TOTALLY surprised me.

Isleh was at less than half health, later review of the combat logs reveals she took dmg 4-5 times from Kirt before he took any in return.

I charged out and started attacking.. then we dropped Kirt. We *had* to respond to his attack.


Then the other folks loaded in, which I already described.

Actually, I went over the bazzar terminal to find restoration kits. Getting several locations so, what happened to Ekade's BARC could be undone and we had spares just in case it happened again.

[Isleh]

I loaded in and was all YES ISLEH ALONE! but then when I KDed her and moved closer the door to the starport terminal opened and I saw Ekade and Vreese in there, "F@CK" was all i knew and I started to move but Ekade had me.

Adun, and Crystal were both in my group loading in, Adun on Vent and he said clearly he loaded in incaped, and crystal said it in Groupchat.so they were heated about that, I knew I was out cause I was fully there but the two of them were load incaped. So we decided on I came you Kncoked me out befor I could retreat and took off cause your not stupid and knew more owuld follow when my com goes dead .
I would say best way to fix this problem is to pretty much in spatial go (( here)) or somthing to alert that you are there and no longer loading, the Bug novall refers to is probally the problem since GCW you get a min i believe after loading.

I saw that. Adun was un-attackable... Then he suddenly changes direction and turned red. Everyone's opening shot is a KD and we are no exceptions. And, as I have found out on more than one occasion, once you go down and you have 3+ on you, you usually don't get a chance to stand back up.

It was not done out of maliciousness, but out of ignorance and a misunderstanding of the system.

I'm not a programmer but how hard is it for the server to check to see if a players load screen is still up and, if so, make them unatackable? That is how I, up until now, understood the system to work. I mean, we have this complex macro system that allows players to create buff bots but somehow, it's impossible to check this one thing?

[Dwilah]

Novall and I just tested it. You are blue until you load in completely.

[KirtViza]

Ok novall being there and being red when loaded in is weird since he has an UBERl337 machine, Try with Adun later and see, cause he has horrible lag on most planets, I know Im fine since I dont catch lag except on Dant...which mostly everyone does.

[Isleh]

Okay, how was the lag? Bad? Good? What planet? Connection?

[Ekade]

Novall and I just tested it. You are blue until you load in completely.

Thanks for taking the time to test it for us!

[Dwilah]

Load was fast for me, it was Lok, and it was during the day. Will test again during peak times with another person.

[Isleh]

Loading in today, I had the initial load screen and I heard a tell chime. So I thought I'd test something and while I was watching the the radial indicator, grind up, I typed.

"/r looking at the load screen"

When I finally loaded in fully, there in my chat box was the reply.

"load screen?"