Kartanian

March 31, 2024 on Everlasting. A Vice City supergroup base officer with /sgpasscode and base editing privileges for Vice City (7008), asked two players to have their characters leave the base. Characters were using space in a private area of the base reserved for staff. Got no response to tells or local chat. I changed the base passcode but neither of them were booted and they were NOT SG or coalition members. I removed Coalition privileges and they were still there. I changed the passcode again, and checked to make sure that I was receiving confirmation of the change each time. Still, the characters remained. I had to call for GM support (GM_Impervium responded first) to get them removed. There is a possibility that both characters had been AFK long enough to put them in some unobservable inactive status, except for being inside the instance, perhaps? I don't know but I have never seen a password change not remove a character before, and this time it was two characters, neither of whom were removed and who did not come in through a coalition or SG team leader access. The support ticket is below, before I close it, if this data is helpful.

NPC activation distance. Having a character 150 ft away, through multiple walls, activates NPCs. It also "counts" in the AE system for mission objectives as "bring Person A to Person B" and prematurely finishes the mission. Consistent across maps and for a number of years. Known issue. But no remedy available to AE arc writers, yet. I would LOVE to have activation distance equal regular NPC aggro range as a remedy. (Not really a bug; working as coded intended, but ends up being a bug to what we can do with the toolkit.)

Arachnos VEAT Widow: Widow Collar is only option now Previously, I could have a "No Collar" option on my widow costume. At the moment, the only option available is "Widow Collar." Not sure what changed. I probably last edited widow costumes in Feb-March 2023, I am guessing, but today (June 27, 2023) I don't get the option from Trina or War Witch in costume mode. They insist that the costume file be "Attempt Fix" instead. Albion v1.0.costume

I can't get the second technique to work on pre-placed NPC base objects. The closest thing my character's foot hitbox is next to is the NPC and that still does not find the NPC with the tab or shift+tab. Doing a "hover place and tab" works okay. This is REALLY clunky, though. Whoops. No. This doesn't work for me, either, to move or adjust the NPC object. I can only make it work to delete the selected object, but not get it selected for movement. Are we supposed to be able to get the NPC adjusted with rotation or height before placing? I can't manage to do that. And then when I get them placed, I can't select them to adjust again. Dang.

No, sorry. I'm not going to do this. And in an unusual turn, I feel strongly enough about this to post a comment. This is too complex for what was supposed to be a very simple "vote on the forum" process. I appreciate the CRs' and judges' efforts. If there is a perception problem, this will not fix it. It just creates (or feeds) cynicism, in my opinion. How and why do you expect votes to change with a re-vote? How does an expectation of bias and manipulation affect a re-vote? How does this affect the case(s) where people were encouraged to vote for someone without seeing the bases? I voted once, though I have multiple accounts and have relationships with several of the base owners. If I have to go through special hoops to re-vote, it's not worth it. It is no longer fun. And fun, IMO, is the whole point. No need to reply to this. Just register it as my vote of disapproval. Again, this is not a knock on the usual process or the CRs' or judges' actions, but I wanted to let you know that I'm opting out of what is now a "not fun" thing.

With the newer Homecoming Launcher and the change to the file structure underneath it as a result, and with the actual game directory being DRIVE:\Homecoming\bin\win64\live\cityofheroes.exe, where should the \data\customwindows folder go? If I put it under \win64\live then I get launcher errors.

From long experience, the problem is the scroll in the Chat window, and not the chat bubbles, visually. So what we're really looking for is a shorter range limit of 15-25 feet on Local. Or, an alternate short-range channel, but NOT another player-created global channel. EDIT: I think the suggestions for a 25 ft range make the most sense, so you can see someone nearby and say hello, draw them over and still be in "audible attention range," and yet move your little group not very far away to get out of "noisy" range of everyone else.

Still a problem. Solutions presented here for simply reducing Local range globally or creating a new limited-range chat channel remain in the options bucket as likely effective. Any opportunity to test this out?

That helped, thank you, but maybe not in the way laid out. 🙂 I went looking for the install directory and found that there was already a Mids Reborn folder there with a .json file different from the Mids Reborn 3.2.17 install folder. I deleted both folders and tried installing fresh from the installer and that worked. The behavior of Mids on my system is a bit klunkier than before (red/blue color changes, inability to easily grab and drag the app window to resize it, etc.), but at least it is working properly.

Nope. For some reason, this continues to fail on the other computer. I have uninstalled, scrapped the .exe installer, re-downloaded it, and installed again, with this error code. I am really not sure what the problem is.

I think I have fixed this on the desktop. I uninstalled the attempted (new) installation and deleted the old folder in its entirety. I reinstalled from scratch, leaving the install location as the default. (This is NOT my preference, but it seems to be required.) I was able to launch the Mids Reborn app after this reinstall. I then went to Options > Configuration > Updates & Paths and set the "Save Builds To:" location to my previous builds folder. Everything appears to work as long as I accept the default install location. I will go test this on my laptop and see how that works there, too.

I have had the unable to check for updates error since the January patch, but now on a new install to try to fix that, I have a new error that makes Mids completely unable to launch. I downloaded and attempted to install the 3.2.17 release with file 3.2.17.72, database 2022.02.22 on two different computers. One is a brand new laptop and I left the Camel defaults unchanged. On the older desktop, I installed to a D:\Programs\Mids Reborn\ folder. In both cases, I got the same error on launch. The new install to the older computer did not give me any messages about removing or updating the old version. It just installed. Any suggestions?

I provided the "please report this up the chain" request and the traceroute results to a pretty clueless end user support person at CenturyLink through chat, as well. "Did you reboot your modem?" "Everything appears fine with your connection and speed..." "Do you want to schedule a technician to come out?" No, Ma'am, I just want you to report this upstream to Engineering. I have little confidence that actually got reported or went anywhere. And the problem (as others have noted) could be outside of CenturyLink's direct control, too. Still, I can't reach OVH this morning and it is now 18 hours since it went down, dumping me from the game. I would think that the network techs would have identified and solved this by now.

NOOOO! Don't route my game traffic through the Ukraine! j/k, but one does have to wonder.... Given the situation, I would not be surprised in the slightest to have cyberwarfare/information operations activity going on in that region right now (2022-02-21).

Finally calculated some pathroute results Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 User-PC.Home [192.168.0.N] 0/ 100 = 0% | 1 4ms 1/ 100 = 1% 1/ 100 = 1% modem.Home [192.168.0.1] 0/ 100 = 0% | 2 11ms 0/ 100 = 0% 0/ 100 = 0% stpl-dsl-gw13.stpl.qwest.net [207.109.2.13] 0/ 100 = 0% | 3 13ms 1/ 100 = 1% 1/ 100 = 1% stpl-agw1.inet.qwest.net [207.109.3.97] 0/ 100 = 0% | 4 14ms 0/ 100 = 0% 0/ 100 = 0% 4.68.38.177 0/ 100 = 0% | 5 11ms 0/ 100 = 0% 0/ 100 = 0% mini-b2-link.ip.twelve99.net [62.115.190.220] 0/ 100 = 0% | 6 20ms 0/ 100 = 0% 0/ 100 = 0% chi-b23-link.ip.twelve99.net [62.115.123.243] 100/ 100 =100% | 7 --- 100/ 100 =100% 0/ 100 = 0% 142.44.208.208 0/ 100 = 0% | 8 --- 100/ 100 =100% 0/ 100 = 0% 192.99.146.140 0/ 100 = 0% | 9 --- 100/ 100 =100% 0/ 100 = 0% 192.99.146.147 0/ 100 = 0% | 10 --- 100/ 100 =100% 0/ 100 = 0% ... This gets to Node 12, stops, and closes the Run window.