-
Posts
5371 -
Joined
-
Sorry I'm late to the thread. I finally have my schedule for this month and I should be fine to come to this. It'll be nice hanging out with you guys on a Saturday again.
Robin has not switched fully to Hero yet, but I'll get moving on her.
If for some reason I don't do it in time, Tabby will still be available to help out. -
If it were on the East Coast again, I'd probably go. I went to the one at Jillains in Boston last time and it was a blast!
I hope you have fun at the event. -
Quote:As a Rogue, you will still be able to run the Patron Arc and unlock the power. Just make sure you get the badge before you fully switch to Hero.My zombie/pain is another story. I want him to have the "mace mastery patron power set" Right now, he is a rogue, level 39. Guess I have to become a villian again to get that patron power huh? lol. Thanks guys!!!!
On a side note, they can be unlocked at lvl 40. You don't have to be lvl 41. Lvl 41 just happens to be the next lvl you can choose a power. You can get your Patron badge at level 40, switch back to a Hero, and still have access to the Patron Powers when you reach lvl 41. -
If you look at your map, you will see neighorhoods outlined in different colors. The Red area will be much higher in level. In your case, you must be wandering too far into the Gulch. Try to stay on the streets along the outer edge and you should be fine.
You are right though, some unlucky mission-door positions in that zone can have you headed into dangerous territory.
You could also decide not to do the Hollows contacts and head back to your previous contact to possibly get one in Kings Row instead until you get a little higher to start working your way back through the Hollows. -
Sometimes they can act a little strange. After logging in and earning full credit for a dayjob badge, it might not actually award until you zone or relog again. If it is still not awarded to you, I'd /petition it.
-
Quote:Ahh, so it positions you in front of the wrong portal. That's kinda silly. I can see how that would be confusing when trying to use RWZ as a connecting zone. Yeah, it's just a matter of running back over to the correct portal to go back.This I know. What I meant when I said RWZ portholes was when going through those portholes, if you immediately turn around once your enter the Vanguard base, the porthole will show the opposite zones. I guess what I need to do is run to the other side and exit back through the right porthole rather than just turn around.
Quote:And as for the Ouroboros Porthole, then is it my understanding that until we can complete the "full" alignment and when I say full, I mean that your Villain bar is full and your full title is now a villain and conversely your hero bar full and your title bar now is hero, that we will always get the reverse zone from Ouroboros?
Quote:And thus, if we intend to use Ouroboros, not to have any tip mission we intend to do? I guess I need to read more up on this.
There isn't really anything more to it. If you are a Vigilante or Rogue, you will have access to both the blue and redside zones, but you can't cross back and forth at your leisure without losing the tips you got from one side or the other. -
Quote:I took it as meaning that using the O-portal after traveling to those other co-op zones will also give you the blue zones, which is also intended if they are Vigilante.To me, that claims if you enter RWZ from redside as a Vigilante holding redside tips, when you exit RWZ back to redside you'll lose the tips. Is that right or am I mis-reading?
I don't think co-op zones should act that way, but maybe it's WAI.
But now that I take another look at it... It appears like they are saying that if you attempt to leave RWZ by using those portholes on the wall, it is giving the wrong side's zones.
Remember Fusion_7, there are TWO portal exits in RWZ. One goes to Paragon City. The other goes to Rogue Isles. Make sure you are in front of the correct one.
As for the Pocket D issue.. I believe it is programmed to ALWAYS give you that warning. It's not telling you that you are about to lose your tips. If you read it closely, you will see that it actually tells you that if you entered PocketD from the Redside and you are going back to the red side, you wont lose your tips. -
Quote:I think they meant that when using the O-portal while in Pocket D, it brought them back to the blueside and lost the tips, even though they entered from the red-side.That's how I understand it too.
I didn't realize the same problem happened in Pocket D and RWZ though.
Fusion_7, the side you are on or the side you entered the co-op zone has NO bearing on which Ouroboros you will go to. It's decided by your actual alignment.
You are right Catastrophe, as long as you entered a co-op zone from the redside, and then exited back to the redside, you should not lose your tips.
Remember, Ouroboros is not actually a Travel device. While doing tips on the opposite side, you will have to get to your missions the "old fashioned way". lol -
Hero and Vigilante should ALWAYS go to the blue Ouroboros because they cannot interact with red contacts.
Villain and Rogue should ALWAYS go to the red Ouroboros because they cannot interact with blue contacts.
This is regardless of where you are, where you have been, or whose portal you click on.
As for losing your tips, this is also intended behavior. For example, if you are a "blue" character doing tips on the red side, but you travel back to a blue zone, including the blue Ouroboros, you will lose those tips.
*Edited for further clarification. -
-
There is a very small opening under one of the ramps. You'll have to go behind the cargo containers/crates.
-
September 2010:
Septemer 2010 GR Calendar
September's Calendar features Praetor Tilman, the Praetorian alternate of Mother Mayhem!
I wanted to feature something from the new zone, so I had to wait for Going Rogue to be released. I had a few great suggestions of what areas to feature, and I was going to go with the Power Plant, but it was hard to take a good daytime shot of it because of the "smog" effect in that area, so I went with one of the Praetor statues until I have more time to mess with the Keyes Reactor a little more. I hope it was a good decision.
I'm aware the grid might be a little bit "too" yellow. I didn't realize it until I put the GR logo under it. At that point, I wanted to get it released by midnight, so I'll just work on a better shade for next month's calendar.
Edit:
I haven't really had many suggestions, so I'm probably not going to make any more of these unless a bunch of people tell me to. Thanks for all the support! -
-
That badge is only available Heroside. A Villain can only get it by going Rogue, at which point I think you can earn credit for it, but still cannot be awarded the badge until you become a full Hero.
-
My theory is that Nemesis is really led by Jet Li, and he is moving his way through each dimension defeating his alternate selves to gain more and more power. It's only a matter of time before we foil his plan with more Clones! That is, of course, if Emperor Cole lets us!
Then again, maybe Emperor Cole IS Jet Li is disguise. As an alternate self, it would explain Statesman's power and leadership as well. We MUST investigate.. until Chuck Norris comes along and kills everybody. He already defeated almost all his alternate selves and possesses the greatest power of all! The last one is the Aspect of Rularuu, which he can only attempt to defeat if he accepts invite to an SG. Every time somebody extends him an invite, he kills them... so that might be tricky. haha -
But there was no Ouro back then either.. lol j.k
-
Just a quick note:
When making those bind files, you wouldn't put "/bind" on each line. -
Not for nothing, but old news is old news. As far as many of us could tell... 10.7 already fixed most of the issues already. I've been using both those options together since the end of July. Version 10.8 seems to just polish the overall performance and fix a couple other minor issues with the FSAA in general.
-
To comment on this, there are floor spikes identical to that in the Orenbega maps that are usually semi-transparent like that as well. At the right angle, you can get inside of it at the top.
-
Quote:If somebody uses the [Reveal] power before you zone into the mission map, it will be uncovered for you as well. If you are inside the mission when the power goes off, nothing happens... but leave the mission for any reason, you'll usually come back in to see it uncovered as well.Oddly, I have had the opposite occur in instanced maps for SFs that I do regularly. Sometimes I'll will zone in and there will be no FoW at all. The entire instanced map will be revealed.
Doesn't happen always, or even frequently, but has happened more than once.
I'm not sure if that's working as intended or anything, but that's the way it's been working since it was released.
Either way, I'm not sure it's really connected to the issue in this thread. It's more likely a simple side-effect of the mission maps being shared by the team.
As for the actual issue in this thread.. I have certainly run into the "cap" as well. Once I moved a Hero to Villainside, almost none of the Rogue Isles zones will stay uncovered.
And for the secondary issue in the thread, corruption.. I have seen this almost since day 1 playing the game, but not quite to that extreme. Occasionally, I'll see an uncovered area of a map that I couldn't possibly have ever visited. For example, a small patch of water at the edge of a zone with no other lines connecting it, as if I was TPd there and back at some point. It seems silly. Even on new characters, it would happen now and then. Once uncovered, I'll see that same patch every time I go back to that zone.
On my main character, even after the previous "cap" was raised, there were areas toward the South end of some Shadow Shard maps that would refuse to stay uncovered. The top 80% would be fully uncovered, and I'd have a path at the bottom to my mission, and when I get out of the mission, the line was gone. The top 80% was still uncovered, but I was standing in a black area. At some point later, that stopped happening as well.
I guess when the number of possible zones increases, so does the degree of corruption.
Just to provide a little more specific info:
I have never downloaded or used any add-on maps for this game... which means that couldn't be any kind of possible cause for the issue. -
I had a prolem with it a week or so ago when they were changing IP addresses or whatever, but it's been fine for me since, including the last few days.
Sorry -
Yep, sounds like your rent is unpaid. As mentioned.. if it's actually already paid up, send a /petition to try to get it sorted.
-
Quote:See below. Since the Market merge, all items and money are interchangeable between Alignments.http://boards.cityofheroes.com/showp...&postcount=330
This was in the wiki page. And as funny as it is, how does that work now with praetoria?
-
Quote:That's right, because you already have the + effect working from the +forward/backward commands. It's already going to run twice.Tinkering with the idea of putting the "+$$" in front of my forward/backward commands and using "toggleon"... waddya think? .... might have to switch the order of hover & fly in the string?
EDIT: hmmm... nope. getting "backward 0" when I try that
.
If it's working backward for you, make sure you have Hover on, or both flights off before you attempt to go forward. The whole idea is to have Fly only turn on when you move forward, so if you have Fly already on when you attempt to go forward, that's why it's bouncing back to Hover.
If you have Hover already turned on when you attempt to go forward, the position of each power in that string will not matter, but you already have it listed correctly to default to Fly if both of them are off as well, so I'd leave it alone.
Edit:
NVM, I see what you mean now... After you enable your autofly bind, it leaves Fly on when it's done, which screws up your other bind.
There really isn't any way around that other than using another bind that switches the two of them, like:
/bind KEY "powexecname hover$$powexecname fly", so you wont have to double-tap your other bind when it gets messed up.
Either that, or you can make your own "auto-fly off" button as well. Something like:
/bind KEY "autorun 0$$powexecname hover"
That should revert you back to your previous state of being stopped while Hovering, at which point you can use forward for manual control again. -
Not quite... you can actually activate two under special circumstances..
Flight 2:
numpad0 "+$$powexec_toggleon sprint$$powexec_toggleon ninja run$$powexec_toggleoff hover$$powexec_toggleoff fly$$bind_load_file c:\CoH_binds\flight1.txt"
If using two toggles, you can start your command line with "+$$" to activate the command line twice.. once on key-press, and again on key-release, which will activate both toggles you specified with the single keypress.
The side-effect for your particular bind is that it'll end up loading the bind file twice a well, which I guess doesn't hurt anything, but you'll see it pop up in the chat twice if you don't use one of the silent load commands instead.