NZScruffy

I'm getting the same problem. Only crash when i try to list servers. It seems to happen when it hits a particular server. My guess is, someones found a way to inject code in server name that borks the list.

umm.. what else did you do to make this stay?

Good idea, but your discord channel setup is yuck. I'm not trolling through 100's of grid channels trying to find things...

... 'someone told me' is how the rumor mill works. I generally ignore anything people say without some sort of proof or reference as to how they came by it. Most of the time such information is completely made up.

have you tested this? I suspect this is the issue, but have you tested it? What limit? you saying limit of 800 npc crew per grid? In game, my admin debug says NPC: 12125 Active NPC: 486 StasisedNPC: 11639 Hmm..i dont' think i can get a count on crew npc specifically... But I doubt it's 800 in this grid... So I don't think that's an issue.

Play unofficial where rates are so high it doesn't matter. Or where the tax bank structure can be easily removed from the game.

If you get to the point you don't want to play Atlas official ever again, there are alternatives. Unofficial servers offer the same fun gameplay, especially for PvE, and active admins to ban problem players. Doesn't solve the game exploits, but you at least have admin to deal with it.

I'd like to re-ask this question, post Patch 11.4 which has failed to solve the problem? When will this be fixed, as it's still not fixed. You can still sink other players ships. The change also introduced new problems which I and other don't want: 1. We cannot have friendly players on our ship without allying them, which is not what you want to do all the time. 2. Any player boarding a non-allied ship is permanently stuck hovering above it, unable to move. This results in player having to die and respawn loosing all their gear. Disabling this gets us back to pre-patch 11.4 state still with the griefing issue. - Disabled non allied players and creatures basing on anchored or docked ships which can be toggled with a server-setting on PVE servers with the in Game.ini - set bPvEAllowNonAlignedShipBasing=true If you want to allow non allies to be able to be on your ship

I do not dispute there is a decline, but the numbers you gave don't have any relevance to the statement....you gave numbers for different lengths of time what are you on about? If you want to look at the decline in players playing the game, you need to look at a minimum time frame of 1 week period vs another 1 week period. People play at different times of the week for different reasons. Eg. Weekends, before/after work/school. If you were to compare 1 US Saturday to 1 US Monday, you are going to see more people on a Saturday, not because of a decline, but because many people work/school on Monday and not on Saturday. Some basic common sense in this one. Likewise, you are going to see a fairly consistent rise and fall in players online over every 24hr period. As large chunks of people play the same time each day. So you cannot compare players from between time period 20:00-21:00 with time period 01:00-02:00. You need to at the very least compare the same time period from different 24hr sections of time (eg. 20:00-21:00 today and yesterday). And even then, you cannot compare weekends to weekdays (keeping in mind time zones mean one person weekend can be other persons Monday etc). So you'd probably want to try and compare Tuesday this week from Tuesday last week. When making statistical comparisons, you need to make sure to address any factors of difference in gathering the data. Your claims become invalid when there are too many variables of difference in data collection.

That wasn't true in my testing. Only 'level 1' crew stop you hiring more. just level the crew above level 1, and now you can hire more. HOWEVER, there seems to be another bug that is preventing people hiring crew at all with previously existing crew recruiter NPCs. creating a new npc, or wiping your old save and respawning the world results in ability to hire again. I have no idea what the issue is.

I suspect the reason that worked was not from the idling but because other events meant you could now hire and couldn't before. I wonder if this is because there are 20 level 1 crew 'nearby'. not in your company, or owned by you, but still there, and blocking the purchase of more. My players are suffering this problem also, and i cannot find a solution.

They knew full well that change wouldn't solve the overweighing issue. As was stated before the change in many forum threads. I don't have any way to directly contact Jat. I also believe Jat knows all the information passed through the forums regarding this, so there's nothing new I can add. I think they released this change knowing full well it wouldn't 'solve' the problem, but rather be a step towards dealing with it. And they believe the problems created with the change aren't important enough to stop the release. It's 10x more productive for me to get my hands on a dev kit to fix the problems I can't fix by clever use of server settings. Hell, I'd work for grapeshot for free, just give me access to the source and i'll fix the problems for them. I wish.

1. Contact them how? 2. They've received the bug and exploit reports. I don't think me wasting 15 mins to provide the same info again helps any. 3. The problem here isn't that the devs don't know. it's that they aren't fixing it.

Oh I can definitely still sink boats, i tested it, creative folks will figure it out quickly i'm sure. The other big issue is the fact you can't do ANYTHING once you are stuck hovering above someone else's boat. So now we have another big problem, plus you can't sail on other peoples boats, plus the exploit it was meant to solve is still there.... net result? more problems, no solutions. Normally I'd dub this 'epic fail', but lets be honest, this is just normal every day stuff for grapeshot

OK, i see there is sufficient 'feedback' on how ridiculously stupid this change was and doesn't even 'fix' the overweight sinking a ship issue. So i'll just add my +1 here for a terrible change that ADDS more problems and doesn't solve them. And spend my energy on trying to fix this myself, as I have no faith in devs to do it. NB: It's highly unlikely devs will change this, for all their talk of 'not repeating past mistakes', that's precisely what's happening here. And i can count on my fingers the number of times they reversed a 'change'. This 'bug' is here to stay. Fingers crossed for dev kit soon so players can fix the game for the devs.