Jump to content

arkark

Members
  • Posts

    835
  • Joined

  • Last visited

  • Days Won

    1

arkark last won the day on January 16 2019

arkark had the most liked content!

1 Follower

About arkark

  • Birthday December 6

Personal Information

  • ARK Platforms Owned
    PC

Recent Profile Visitors

5,740 profile views

arkark's Achievements

Hide Armor

Hide Armor (3/5)

155

Reputation

  1. There is a rule in the CoC, PVE Griefing section that says the following: Game Blocking - you are not allowed to block other tribes from playing the game on PvE servers. This can include but is not limited to: Building at their base Now, this is a fictional situation that has never happened but which I have not clear if it breaks the CoC or not: Imagine that you found a spot, completely empty of structures cause the server is fresh new. You place some structures, make a small outpost and while you are farming for more structures another tribe comes and pillars all around you blocking you from building in that spot. This means you cant continue building there because you are pillared all round. Then, weeks later, they have placed structures other than pillars. Would a report from them based on said rule saying you are building at their base be accepted and your outpost wiped so they can take all the space? From my understanding, if you place structures first you are not "building at their base" because there was nothing when you built it. I want to hear your oppinions, specially from people who is more experienced with the CoC.
  2. Gen 2 934, 935, 936, 937, 938 and Gen 2 Legacy 946, 947. All this 7 (7!) servers are on the same physical machine. When one of this servers crash it often drags all the other servers with it. Example of this morning: At 07:33 server 938 crashes. At 07:58 while 938 is not responding (crashed, crashing, generating dump, or even booting), all the other servers on the machine start crashing one after other This is just a real example of this morning. This exact same behaviour is happening 10-15 times a day on this machine. When one server crashes it grabs all the other servers on the same machine with it. I would speculate about this is some memory leakage on the crashing server that hog the resources of the machine until every server crashes, result of limited shared resources (RAM) of the physical machine. But this is just speculation. What is clear is that until you take a look at it and move some server to another machine or increase the shared resources this situation is not gonna improve. Please do it soon so we can enjoy gen2 without being worried all the time about if we can do x thing because it may crash or not. @lilpanda @Cedric
  3. This is not a problem with legacy servers. Your server 946 its in the same physical machine as our non-legacy official PVE. To be more precise, 946 and 947 are on the same bare metal as 934, 935, 936, 937, 938. This is 7 servers on the same physical machine and I would bet sharing the same memory resources. Due to the big number of crashes we have every day in our server I've started monitoring all that servers to see if there is some pattern and I can say that every time: - One of those 7 servers crashes. - There is small chance, I would say 10%, of that server normally recovering from crash. - There is a 90% chance of a domino effect, a chain of crashes on every server that is on that machine, until all crashes. This mean if our server crash there is very high chances that it will affect your server and vice-versa.
  4. 938 and other servers that were affected by the +140/70 players overcap are now super laggy during all day. Just throwing and idea, why dont you announce each of that servers its gonna be taken out of the main cluster and temporary being clustered with two new ones, allow structure pickup and open transfer during a week? After a week delete the initial servers and close transfers and move to the main pve cluster. So at least the players of that servers are splitted 70 and 70 and there is not perma lag.
  5. Genesis 2 performance its horrible. We are playing all the time in 938 with 200-255 ping. Dinos just teleport and dissapear all the time. Even taming a bee becomes a challenge. I think each bare metal server was hosting 3 servers before (27015, 27017 and 27019), but with genesis you seem to be running 5 servers or more in the same hardware (27015, 17, 19, 21 and 23) ? Whatever you are trying to do, probably with more powerful machines is not working at all, rendering to a very poor latency.
  6. Just wait for a fix or try to tame at hours where the ping is lower than 100-120, and bless no one enters and no day change or save time. This tame is very easy but it becomes a complete pain and a waste of time often due to external reason which have nothing to do with the tame itself.
  7. If anything can be suggested about this topic would be, if you use cheats then you dont get the cinematic. You can end the game, get the ascension levels, but the cinematic is locked until boss is defeated by some tribe who meet some parameters like no vr mission cheat unlock, no god mode, no infinitestats.
  8. Siempre ha sido igual, los nuevos servidores tienen 90 días en los que no se puede transferir nada más que el personaje. Cuando pase ese tiempo quitarán la limitación.
  9. Based on the experience of what is happening on my server where several tribes have carried out a massive pillaring making basic tasks such as catching fish an odyssey I would like to propose, if it is in the wildcard hand, that an estimate of pillars placed by each tribe be made and a limit established so that the enforcers can act directly without the need for users to make reports that, at the point the servers are there are pillars practically in each small flat area of land, are a extremely heavy task that could be automated by setting off triggers for a manual review once a tribe is detected to have for example 500 pillars separated by x distance. A heatmap could also help to identify this cases. Personally I had only experienced a similar situation at the launch of Extinction, where a tribe claimed almost the entire area of the Forest and was reported and the enforcers cleaned the pillars. But now the problem is that several tribes are doing this, which makes it much more tedious to report all of them giving details of the areas with pillars. Also, at least in the case of the server I'm on, the names of these tribes are type [] [] [] with more or less squares, which makes them doubly difficult to identify. In my server at least there are zones claimed by tribes from a side to a side of the zone (Ive seen that at least in rockwell garden). Idk if you are seeing that too in your official servers or its only happening in the one im playing. Would like to hear oppinions without giving names about if the pillaring is being much more aggresive in gen2 than it has been previously.
  10. They had some oc servers gentwo with 328.6 some hours ago, now there is a qa one with 329.3 which I hope it will be releasing soon
  11. You cannot uncryo a flying creature in aberration. If I remember well when u thrown the cryo a message appear in screen saying that this creature type is not allowed on the map (as long as the server has same foreign dino config as official).
  12. Weird, that server that you have marked with -96/1 has 4/100 players atm. You playing on steam client or epic?
  13. This exact same crash happened to some users back in 2018 and apparently it was some DNS problem at provider (most if not all of the ppl reporting were australian telstra users): https://steamcommunity.com/app/346110/discussions/0/1694922980046496262/?ctp=5 The crash was in the same function ValidateSendBuffer() and with exact same payload size (506 bytes), so I would bet it is the same problem. Changing the DNS or connecting through VPN seemed to work, maybe you can try that.
  14. Yes, the problem is that this two maps, due to how easy element farming is are saturated of giant bases with tons of cloners plus tons of dinos for selling / mutation breeding. But the long save times is not really the problem, I mean, I can live with 1 or even 2 minute save every 15 min, thats no problem, I accept it. Problem is that due to that long save times the game client (I think) believes that the server is down and disconnect with timeout message. And at the same time the server, after the save is done, still thinks we are connected so if Im doing an osd the zone where I am does not enter stasis and dinos and char get killed while we are waiting on the login lock screen. I think optimal solution would just be increase the timeout of the game client when a save its being done. At least until more appropiated solution is found it would workaround this kind of timeout disconnections. This is not only happening on the maps I play btw. Some months ago I considered relocating my bases to another servers and asked active playing friends about how they gen and ext were performing and almost all told me they are experiencing same thing on this two maps.
  15. Its good to see you are working on improving stability of the game but please dont forget whats going on on most (afaik) genesis and extinction official pve servers where long save time makes game clients disconnect due to timeout and then server does not allow to reconnect fast because "there is already someone connected with that account". This makes the area where the player was not entering stasis immediately, and if player was doing veins/osd/missions this much likely means player killed, dinos killed, broken gear... rendering this maps to non playable status.
×
×
  • Create New...