Archaegeo

Given a conversation with NQ this weekend and expected rule clarifications next week (not sure which way, just clarified rules) I plan to continue playing for the moment. This might end up being like when you plan to quit a job, you are offered some so you stay, and you end up quitting 6 months later, but we will see. I honestly do want DU to work out, I didnt put 2 years of coding into it because I want it to fail. When you have a game with GM enforced rules, they must be clear and they must be enforced, especially in PvE areas where all other players have no recourse. If we had territory warfare and could have dealt with this on our own, it would be a totally separate situation. Anyway, ArchHUD will be maintained and continue to be improved for now (as much as I was ever able to improve it).

No one should be threatening you. Especially not physically or personally abusive. This is the problem with civil discourse in the world these days.

Thanks for all the replies including the kind words, and the constructive disagreement (those who think personal insults are the way to hold public discourse I truly feel for you). I want to be clear though - This had absolutely nothing to do with having to avoid a tower. Thats how I found it. ArchHUD will avoid crashing into it (with an atmo radar), or can have a route that plots around it, so this is nothing to do with the tower, or not being able to afk autopilot, or afk mission run (its funny some people think you can legally automate the whole thing, you cannot0. This has to do with an obvious intentional griefing, a rule to prevent such griefing, and the sudden interpretation that 2km airspace only means directly over the market tile. For any newbie flying, they may not know that even if they turn to avoid the tower when it loads in, they might stall and crash. And anyone using market 12 as a market cant fly out at that heading now, cause few ships can do 38 deg up and go 500m up before going 450m forward (whats needed to avoid the tower). And the fact they posted a sign saying roughly, we are going to cover the entire north side, land elsewhere. And yes, the NQ snarky reply didn't help. This is the problem with rules in MMOs. If something isnt hard coded, players will break the rules and GMs will have to waste valuable time investigating such reports. But if that is the dev team choice, you enforce the rule, or you change the rule. Changing this rule (which they effectively did) allowed one way "pvp". By this I mean: Since the tile in question is in safe space, one player is allowed to force all other player to change their playstyle (fly a different route) and there is nothing they can do about it. We cant destroy the tower, we cant move the tower, we can only choose to change our fight paths because another player forces us to do so. And it was a choice by them, it is built perfectly perpendicular to the incoming and return flight path for the most popular mission from Alphelia, and has a scrap stand at the base. Anyway, like someone said above, straws and camels. Be good to one another, remember that PvP doesnt mean hate v hate, just two people playing a game.

UPDATE Given a conversation with NQ this weekend and expected rule clarifications next week (not sure which way, just clarified rules) I plan to continue playing for the moment. This might end up being like when you plan to quit a job, you are offered some so you stay, and you end up quitting 6 months later, but we will see. I honestly do want DU to work out, I didnt put 2 years of coding into it because I want it to fail. When you have a game with GM enforced rules, they must be clear and they must be enforced, especially in PvE areas where all other players have no recourse. If we had territory warfare and could have dealt with this on our own, it would be a totally separate situation. Anyway, ArchHUD will be maintained and continue to be improved for now (as much as I was ever able to improve it). It is with some amount of deep regret that I say goodbye to DU. I have tried to support the game, beyond ArchHUD, but NQ's attitude to blatant griefing is just too much. This is not how you help a game grow. We all know there are lots of issues, but I was hoping that the wipe and release would be a nice fresh start. I want to thank everyone who has supported ArchHUD (and ButtonHud before that) and who have provided support and kind words over the 2 years. I hated the fact we have T1 bots buying ore injecting unlimited quanta into the economy (why should coal be worth anything if no player willing to pay for it). I hated there are bots selling elements (takes way player market niche setting ceiling prices) I hated the fact that there is no decay of elements (life count is bugged, nothing on my ship goes below 2 lives left, and of course static elements never run out). I hated that we didnt get Territory Warfare (original promise) I hated that their solution to pvp problems was a stupid floor max speed no matter mass of ship. (And floor burn speed no matter size of ship). I was willing to overlook it, and hope they would make the game better, but .... I cannot continue supporting a game where the dev's ignore blatant griefing and refuse to enforce their own rules. (see below post). So I am done. I wish you all well, and will see you around the pond. So long, and thanks for all the fish. Archaegeo (Regarding ArchHUD - I will leave it up for the time being. I will not be providing support for it though going forward. There are many who will, and someone might pick up the mantel). < >

NQ-Rubicon — Today at 11:27 AM If anyone reports a construct that a player creates with intent to block or grief players, we will investigate and take any appropriate action. In this case, there is plenty of Aphelia territory and airspace unobstructed to allow players access as intended. As mentioned, the Market rules are only enforced within Aphelia territory. This has always been the objective

Also when questioned about it blocking takeoff slope: NQ-Rubicon — Today at 11:19 AM Then I advise not trying to take off while facing it's direction.

Via discord today: NQ-Rubicon — Today at 11:18 AM The construct shown is not in violation of the Market parking rules, nor is it circumventing any in-game rules. When referring to airspace, this means typical flying heights and the Market rules never apply to player owned territories.

At market 12, the turn in point for the 180k Alphelia mission, there is a tower being built 500m from the market landing pad that is in the direct flight path of anyone approaching or leaving that way. This is against the rule saying "Airspace must remain clear within 2km of market". The owners state that NQ said it is ok. So if the rule doesnt apply, remove it. They have also placed a dynamic construct with a sign at the market (another violation of rules) stating they are going to block the N side of market 12, land elsewhere if you dont like it. If this is going to be allowed, fine, but remove the rule. We know the rule was put in place due to people intentionally obstructing markets with tall towers. Yes, this tower is only 500m tall, but to clear it on takeoff, you would need a 38 deg slope, with enough sustentation speed and lift to get you over it if going that direction. All that aside, the issue here: ENFORCE YOUR RULES or REMOVE YOUR RULES.

When will we be able to apply backer DAC in order to be able to join when server goes up on 27th?

The issue is parsing the log to do outside things, aka notify on discord or via text message etc. If you intend for the log to be readable for some purposes, I would recommend a randomized delay before the log gets written so it cant be utilized for instant notification of in game events. Example from log: <record> <date>2022-01-17T19:48:50Z</date> <millis>1642450010131</millis> <sequence>18617</sequence> <logger>D:\Bamboo1\xml-data\build-dir\WC-REL21114-CSTS\Source\game\scripting\DPUnit.cpp:212</logger> <level>WARNING</level> <class>WC-REL21114-CSTS.game.scripting</class> <method>NQ::DP::Unit::execute</method> <thread>21872</thread> <message>Executing a Lua method in the wrong thread. method='setAxisCommandValue', inFlush=true, method is Flush compatible:false, method is Update compatible:true</message> </record> The above occurs whenever a method is done in flush that isnt allowed. If i was nefarious, i would do that intentionally and log parse for it for my nefarious notifications

Side Note: Removal of lua logging will not stop people reading the logs and using things written to do stuff. If logs exist, and they record things like a core turning on and off, or any producable event in game, the log can still be used for nefarious purposes.

system.soundVolume() is needed to go with play and stop so that the play volume can be less than game volume.

People are allowed to reply to your post with whatever comments they wish. This boils down to there is no reason for "Potential Methods of Alleviation" as you put it. That just means keeping OP ships in the sky.

I concur about blueprints being limited runs, and also you should not be able to make a blueprint off something built from a blueprint. Just because you can follow a blueprint to make something doesn't mean you can make a blueprint from something you built following one. This will let Blueprint become commodities and establish Artisans for the economy.

Just bought the game, so high, and I'm curious, why do owners of the game need moderator approval for posts? Anyway, hoping this and my public profile post get approved so i can get in the right areas of the discord.