Vyolette

Bug reports!

67 posts in this topic

Hi there!
First for a short introduction, I'm Vyolette, the newest member of the WU team. My role is to collect information on bug reports and attempt to duplicate said issues on my own, and report my findings to the team. I'm also happy to help with any technical issues that don't require the attention of the coders. That said, bug report away! If you'd like to report bugs directly to me, my email address is vyolette@wurmonline.com - but please, include as much detail as possible, including version and mode of server you're running, any changes you've made to the settings and any mods you're running. Thanks so much!
                 --Vyolette

2 people like this

Share this post


Link to post
Share on other sites

Hell creatures not spawning (been that way since day one). (Hell Horse, Hell Hound, Lava fiend).

Wand of the seas and rod of eruption not working (becoming un-planted at 90 dmg).

Epic Terra forming events do not work at the end of scenario, nor does the winner receive a endgame item (tome).

Normally non attack-able creatures can be attacked and killed (Salesman, Bartender, and so on).

 

(1.0.0.7 non modded server, non modded client)

 

Characteristic skill gain broke (Requires mod to fix).

 

I'll amend this post when i think of more.

 

Edited by ausimus

Share this post


Link to post
Share on other sites
3 minutes ago, ausimus said:

Hell creatures not spawning (been that way since day one). (Hell Horse, Hell Hound, Lava fiend). Fixed in Beta 1.1.0.0

Wand of the seas and rod of eruption not working (becoming un-planted at 90 dmg). 

Epic Terra forming events do not work at the end of scenario, nor does the winner receive a endgame item (tome).

Normally non attack-able creatures can be attacked and killed (Salesman, Bartender, and so on).

 

(1.0.0.7 non modded server, non modded client)

 

Characteristic skill gain broke (Requires mod to fix).  Broke is a relative term. It does scale better than it did at launch. This isn't so much a bug but a need for a possible feature to set stat gain separate from skill gain.

 

I'll amend this post when i think of more.

 

 

2 people like this

Share this post


Link to post
Share on other sites

I'll add more below as i think of them or we work on a mod to fix them.  

Edited by razoreqx
did not list 100 bugs yet. still digging through my list

Share this post


Link to post
Share on other sites

Email sent but i posted for other admins to be aware: 

 

The following are bugs broken down by cluster issues, server issues.  All have been tested on vanilla versions of the maps with no mods installed.  
Hardware:
i7 quad core 3.1GHz
32GB ram
1TB SSD raid 5 configuration
 
Wurm.ini
#Wurm online server initialization file.
#Tue Jun 09 14:29:34 CEST 2015
NUMBER_OF_DB_PLAYER_POSITIONS_TO_UPDATE_EACH_TIME=500
USE_SCHEDULED_EXECUTOR_TO_SAVE_DIRTY_MESH_ROWS=true
SITE_DB_USER=
LOGIN_DB_PORT=1
USE_POOLED_DB=true
USE_SCHEDULED_EXECUTOR=true
USE_SCHEDULED_EXECUTOR_TO_SEND_TIME_SYNC=true
PROSPECT=false
DB_PORT=1
USE_SCHEDULED_EXECUTOR_TO_UPDATE_CREATURE_POSITION_IN_DATABASE=false
USE_TILE_LOG=false
CREATE_TEMPORARY_DATABASE_INDICES_AT_STARTUP=true
USE_SCHEDULED_EXECUTOR_FOR_SERVER=false
USE_SCHEDULED_EXECUTOR_TO_COUNT_EGGS=true
LOGIN_DB_USER=
SITE_DB_PASS=
USE_SCHEDULED_EXECUTOR_TO_UPDATE_ITEM_DAMAGE_IN_DATABASE=true
DB_USER=root
ANALYSE_ALL_DB_TABLES=true
PLAYER_CONN_MILLIS=1000
DBPATH=.
OPTIMISE_ALL_DB_TABLES=true
LOGIN_DB_PASS=
USE_SCHEDULED_EXECUTOR_TO_UPDATE_PLAYER_POSITION_IN_DATABASE=true
CHECK_WURMLOGS=false
USE_SITE_DB=true
USE_ITEM_TRANSFER_LOG=false
USE_SCHEDULED_EXECUTOR_TO_SWITCH_FATIGUE=false
DB_PASS=
TRELLO_BOARD_ID=
TRACK_OPEN_DATABASE_RESOURCES=false
USE_SCHEDULED_EXECUTOR_TO_UPDATE_TWITTER=true
TRELLO_MUTE_VOTE_BOARD_ID=
NUMBER_OF_DIRTY_MESH_ROWS_TO_SAVE_EACH_CALL=10
DB_DRIVER=
MAINTAINING=false
LAG_THRESHOLD=500
SITE_DB_HOST=localhost
USE_LOGIN_DB=true
DEVMODE=false
SITE_DB_DRIVER=org.gjt.mm.mysql.Driver
DBSTATS=false
SCHEDULED_EXECUTOR_SERVICE_NUMBER_OF_THREADS=15
USEDB=true
USE_DATABASE_FOR_SERVER_STATISTICS_LOG=false
USE_QUEUE_TO_SEND_DATA_TO_PLAYERS=false
CAVEIMG=false
LOGIN_DB_HOST=localhost
LOGIN_DB_DRIVER=
USE_MULTI_THREADED_BANK_POLLING=false
USE_SCHEDULED_EXECUTOR_FOR_TRELLO=false
USE_SCHEDULED_EXECUTOR_TO_TICK_CALENDAR=true
RUNBATCH=false
WEB_PATH=.
DB_HOST=localhost
USE_SPLIT_CREATURES_TABLE=false
PLAYERLOG=numplayers.log
STARTCHALLENGE=false
CHECK_ALL_DB_TABLES=true
NUMBER_OF_DB_CREATURE_POSITIONS_TO_UPDATE_EACH_TIME=500
CREATESEEDS=false
NUMBER_OF_DB_ITEM_DAMAGES_TO_UPDATE_EACH_TIME=500
SITE_DB_PORT=1
USE_DIRECT_BYTE_BUFFERS_FOR_MESHIO=true
PRUNEDB=true
PREPSTATEMENTS=false
CRASHED=true
USE_INCOMING_RMI=true
 
I also want to note we have added several mods to decrease clutter in an attempt to reduce counts per zone and this greatly reduced our poll timers but as the population grows we're still having major issues with poll timers because of some the core thread and DB locks listed below.
 
On startup (can toggle off and on)
Mod removes all off deed piles, rock shards, tree stumps, log piles, dirt piles, creature corpses, wood scraps.
Switch to purge all creatures off deed unless branded, hitched or have horse shoes (not run on every restart and only in maintenance mode)  Gets rid of creatures out of bounds, in the water, and or bad ID's.
 
Normal operation:
As zones are polled (but before count function) dirt, clay, tar, log, shards, and butchered items are purged if over 20 damage.  Tree stumps are removed as tree is cut down.
Achievement mod to fix cluster adate to login server change
Mod to put a 10% random roll on domestic creature being spawned otherwise a random aggro creature is spawned and randomly placed on map (water tile check) also checks against maxCreature count
Mod to remove light tokens if more than 2 are dropped.  They are deleted leaving only 2
Mod to stop dense fog function removing 400 fog spider spawn as well
 
Startup Headless:
-d64 -server -Djava.library.path=C:\WurmServer\nativelibs -Xmn256M -Xmx8192M -Xms8192M -XX:+OptimizeStringConcat -XX:+AggressiveOpts -jar
 
The following was off peek time

Login server: 50 active users on login server (creative)
cluster 1 has 33 active users on (creative)
cluster 2. has 14 active users on (EPIC)
 
Snippet of Polling timers: Taken from login server:

This is a combination of issues which cause an increase in increase polling timers.   Eventually you end up with micro lag spikes, warping, and worst case data corruption.

[05:13:01 PM] WARNING com.wurmonline.server.items.DbItem: SaveItemLastMaintained batch took 1258 ms for 701 updates.

[07:46:36 AM] INFO com.wurmonline.server.creatures.Communicator: Jotam deposited 20 copper and now has 16 silver, 88 copper and 22 iron
[07:46:36 AM] INFO com.wurmonline.server.Server: Elapsed time (1262ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2898
[07:46:42 AM] INFO com.wurmonline.server.zones.Zone: Zone at 1408, 2112 polled 34 tiles. That took 1429.9583 millis.
[07:46:43 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.974 seconds
[07:46:43 AM] INFO com.wurmonline.server.Server: Elapsed time (1975ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2899
[07:46:49 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.391 seconds
[07:46:49 AM] INFO com.wurmonline.server.Server: Elapsed time (1392ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2900
[07:46:57 AM] INFO com.wurmonline.server.zones.Zone: Zone at 1088, 2432 polled 120 tiles. That took 1630.144 millis.
[07:46:57 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.639 seconds
[07:46:57 AM] INFO com.wurmonline.server.Server: Elapsed time (1640ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2901
[07:47:01 AM] INFO com.wurmonline.server.zones.Zone: Zone at 1088, 2432 polled 120 tiles. That took 1355.0742 millis.
[07:47:01 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.367 seconds
[07:47:01 AM] INFO com.wurmonline.server.Server: Elapsed time (1368ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2902
[07:47:06 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 0.533 seconds
[07:47:08 AM] INFO com.wurmonline.server.zones.Zone: Zone at 1088, 2432 polled 120 tiles. That took 1443.9132 millis.
[07:47:08 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.452 seconds
[07:47:08 AM] INFO com.wurmonline.server.Server: Elapsed time (1453ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2903
[07:47:09 AM] INFO com.wurmonline.server.webinterface.WebInterfaceImpl: [IP redacted] Add money to bank 2 , 7000 for player name: Beylaron, wid -1
[07:47:09 AM] INFO com.wurmonline.server.Server: Polling MoneyTransfer 0 deleted: MoneyTransfer [num: 89, wurmid: [Redacted], name: [Redacted], detail: 7/31/167:47AM37Laoks - Ages of Urath, newMoney: 584604, moneyAdded: 7000]

[07:47:16 AM] INFO com.wurmonline.server.zones.Zone: Zone at 128, 1024 polled 273 tiles. That took 1546.2078 millis.
[07:47:16 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.556 seconds
[07:47:16 AM] INFO com.wurmonline.server.Server: Elapsed time (1558ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2904
[07:47:22 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 2.575 seconds
[07:47:22 AM] INFO com.wurmonline.server.Server: Elapsed time (2576ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2906
[07:47:29 AM] INFO com.wurmonline.server.zones.Zone: Zone at 1088, 2432 polled 120 tiles. That took 1664.6566 millis.
[07:47:29 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.679 seconds
[07:47:29 AM] INFO com.wurmonline.server.Server: Elapsed time (1679ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2907
[07:47:33 AM] INFO com.wurmonline.server.zones.Zone: Zone at 1088, 2432 polled 120 tiles. That took 1423.1288 millis.
[07:47:33 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.434 seconds
[07:47:33 AM] INFO com.wurmonline.server.Server: Elapsed time (1435ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2908
[07:47:37 AM] INFO nofogspiders: Hey, I'm in CreateAchievement!  This is our mod which turns off function of dense fog which spawns 400 fog spiders and then deletes them (if it can find them as some spawn outside the zone)
  This even locks the wurmcreature.db and the login threads.   This mod also addressed the adate issue which is fixed in beta branch, to prevent errors in achievements table.

[07:47:40 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.481 seconds
7:47:40 AM] INFO com.wurmonline.server.Server: Elapsed time (1484ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2909
[07:47:46 AM] INFO com.wurmonline.server.zones.Zone: Zone at 448, 1792 polled 49 tiles. That took 1510.9019 millis.
[07:47:46 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.523 seconds
[07:47:46 AM] INFO com.wurmonline.server.Server: Elapsed time (1525ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2910
[07:47:50 AM] INFO com.wurmonline.server.zones.Zone: Zone at 1088, 2432 polled 120 tiles. That took 1092.83 millis.
[07:47:50 AM] INFO com.wurmonline.server.Server: Lag detected at Zones.pollnextzones (0.5): 1.099 seconds
[07:47:50 AM] INFO com.wurmonline.server.Server: Elapsed time (1100ms) for this loop was more than 1 second so adding it to the lag count, which is now: 2911

As you can see some zones take as long as 1 second or more to complete.   This is a compiled issue which causes the server to become behind in cluster to server communication and synchronization.
 
Cluster / login server issues
1. When Money transfers from clusters to login server is run the DB on the login server is locked.  This causes refreshes on the login server and backs up any information required to be logged on the login server.
2. Player login:  also locks the DB.  Slow connections cause even longer delays in locking of DB.
3. Ships transporting large amounts of items can crash the cluster.  This often results in the ship to vanish and the items to become bloat in the DB and lost from the player.  This often causes the login thread to hang in a refresh until the player is kicked from the server or the target server crashes.
 
4. When a player logs in and the login server has the player set for a cluster it logs out the character and attempts to log them into a cluster.  IF the cluster for some reason doesnt respond (stuck in refresh) the player is placed in a void zone.    The player is then flagged on the cluster as last seen on login server and the login server has the character flagged on the cluster.   The player then needs to log out as they get a void screen.  When the player logs back in in this situation they are presented with a create character screen.  If they create a character all their stats are replaced as a new character and all their items are flagged as unknown including deeds. Event though the last stats of the player are still on the cluster once they are fixed in the DB to point the cluster back to the login server, when they return to the cluster there stats are then overwritten there as well and all items and property are set to unknown.
5. support tickets opened on cluster servers are not recorded on login server until they are edited by a CM or GM.   Often the wrong character gets associated with the ticket other than the original owner of the ticket.  This causes confusion as to who actually opened the ticket.  This is most likely a mismatch of ID's on the ticket.
6. NUMBER_OF_DIRTY_MESH_ROWS_TO_SAVE_EACH_CALL=10  when this function is called it locks the DB and login threads and the players get a refresh which can last up to 10 mins   No errors are ever reported.
[03:39:50 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'FlagsMesh', which took 1301.1642 millis.
[03:40:16 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 500.03824 millis.
[03:40:18 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 641.60065 millis.
[03:40:20 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 624.5482 millis.
[03:40:21 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 641.3299 millis.
[03:40:28 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 658.16833 millis.
[03:40:32 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 754.4819 millis.
[03:40:38 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 610.24805 millis.
[03:40:41 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 505.49808 millis.
[03:40:42 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 549.75916 millis.
[03:40:45 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 591.0337 millis.
[03:41:09 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 574.38727 millis.
[03:41:48 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 628.82025 millis.
[03:42:55 PM] INFO com.wurmonline.server.Server: current mem in use: 8362M free mem: 6306M Max mem: 8362M
 
7. Prune:  This is not working correctly.   Players are not always getting deleted after 3 months of no login or other flags required to purge them from the player DB.   We have tested this with an alt that just logged in and logged out and still show up in the DB for several months to present.    The server also does not delete associated records like achievements, items owned, items in inventory,  which leads to DB bloat.  The deed is disband leaving the villagers without a home.   There should be some type of check to give another villager the mayor role for the deed.  Players can also be pruned on the login server but not the cluster.   When the player logs into the game they go to the void as the login server thinks they are still on the cluster.

8. Mail is destroyed if the cluster is unavailable or loses connection to the login server temporary.   Still happening in new beta branch randomly

[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159572721122562
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159572352023810
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159577586515202
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159577569737986
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159577603292418
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159578190494978
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159578173717762
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159572301692162
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159578106608898
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159578341489922
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159578257603842
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159572519795970
[01:40:33 AM] INFO com.wurmonline.server.items.WurmMail: Checking expired WurmMail 159578324712706

 

9. Permissions on boats move to the original owner of the ship to the commander during zone transfer
 
Non cluster issues:
1. When GM's use or test inter server portals they lose the ability to use the wand to teleport.   The GM has to be set back to implementer and relog to fix the issue.
2. Characters that are purged and are caring for an animal leaves the animal belonging to unknown player in the wurmcreatures.db
3. Fog spider during dense fog lag. The wurmcreature.db is locked while 400 fog spiders are removed.   Players get a refresh screen up to 40 seconds. 
4. When a player logs in and the login server has the player set for a cluster it logs out the character and attempts to log them into a cluster.  IF the cluster for some reason doesnt respond (stuck in refresh) the player is placed in a void zone.    The player is then flagged on the cluster as last seen on login server and the login server has the character flagged on the cluster.   The player then needs to log out as they get a void screen.  When the player logs back in in this situation they are presented with a create character screen.  If they create a character all their stats are replaced as a new character and all their items are flagged as unknown including deeds. Event though the last stats of the player are still on the cluster once they are fixed in the DB to point the cluster back to the login server, when they return to the cluster there stats are then overwritten there as well and all items and property are set to unknown.
5. support tickets opened on cluster servers are not recorded on login server until they are edited by a CM or GM.   Often the wrong character gets associated with the ticket other than the original owner of the ticket.  This causes confusion as to who actually opened the ticket.  This is most likely a mismatch of ID's on the ticket.
6. NUMBER_OF_DIRTY_MESH_ROWS_TO_SAVE_EACH_CALL=10  when this function is called it locks the DB and login threads and the players get a refresh which can last up to 10 mins   No errors are ever reported.
7. Prune:  This is not working correctly.   Players are not always getting deleted after 3 months of no login or other flags required to purge them from the player DB.   We have tested this with an alt that just logged in and logged out and still show up in the DB for several months to present.    The server also does not delete associated records like achievements which leads to DB bloat.  The deed is disband leaving the villagers without a home.   There should be some type of check to give another villager the mayor role for the deed.
8. Mission ruler:  When the text option is flagged it word wraps long dialog to three words or less per line.   Very hard to read and ugly. Not useful for storyline or quest detail instructions.
9. When objects associated with missions are deleted the triggers, effects and mission are also removed. 
10.  Creatures still spawn in water even in the new beta branch and tend to clump together in massive amounts in one biome area.  They need to be spread out better.  Creatures also wander into the water and remain there.   Creatures can also spawn outside the map zone boarder and are no longer polled making them live forever and ignored by the max creature count.
11. Max creature count is being ignored by mostly domestic creatures continue to spawn.   This makes lairs no longer spawn. Still a problem on beta branch.
12. When light tokens in large quantities are dropped to the ground they cause the cluster to crash or lock all threads in a perm refresh requiring a restart
13. 20 threads is to high for default setting in wurm.ini   Often threads will stale and when called cause a global refresh for up to 60 seconds or require a restart of the cluster or login server. 
14 If a HOTA is active during a restart the last statue is lost and the HOTA is broken until it is recreated.
15. Noticed some geo tears in mining areas since cave dwellings was introduced. Players have fallen through the geometry and require summoning.
16. Locks to doors in cave dwellings ignore village permissions.
17. Cave Bugs, Rats and lava fiends are spawning outside instead of in caves.
18. Walls and fences are taking damage on deed down to 0 and never disappear.
19. Horses with certain traits will roam with saddle equipped.  Prior to 1.0.0.7 this was not happening.
20 Eggs stop hatching after a period of time and require a purge from the DB to reset.
21. GM's fall to death when landing on a mine tunnel tile, ignoring invulnerability tag.
22. After 1.0.0.7 was updated invalid item id's show up on startup which appear to be from Wurm Online code.
23. Changing creature kingdom has no function.
24. Lots of dsync issues

[08:47:27 AM] WARNING com.wurmonline.server.creatures.Creature: [Player redacted] set to 1815,965 but at 1815,964
java.lang.Exception
    at com.wurmonline.server.creatures.Creature.setNewTile(Creature.java:794)
    at com.wurmonline.server.zones.VolaTile.addCreature(VolaTile.java:1543)
    at com.wurmonline.server.zones.VolaTile.creatureMoved(VolaTile.java:2431)
    at com.wurmonline.server.zones.VolaTile.creatureMoved(VolaTile.java:2270)
    at com.wurmonline.server.creatures.Creature.moved(Creature.java:11383)
    at com.wurmonline.server.creatures.Communicator.movePlayer(Communicator.java:933)
    at com.wurmonline.server.creatures.Communicator.pollNextMove(Communicator.java:1132)
    at com.wurmonline.server.Server.pollComms(Server.java:2559)
    at com.wurmonline.server.Server.run(Server.java:2437)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)
 
25. Virtual zones are being created randomly for no reason.  Normally this is seen for new players being created or someone logging in.  This increases tolling timers and over head if the zone is being polled. (more refresh)

[08:32:13 AM] WARNING com.wurmonline.server.zones.Zone: Old virtualzone being removed:[name redacted]
java.lang.Exception
    at com.wurmonline.server.zones.Zone.addWatcher(Zone.java:2142)
    at com.wurmonline.server.zones.VirtualZone.initialize(VirtualZone.java:238)
    at com.wurmonline.server.creatures.VisionArea.sendNextStrip(VisionArea.java:421)
    at com.wurmonline.server.Server.run(Server.java:2364)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)
 
26. Still seeing duplicate authentication issues
[08:30:18 AM] INFO com.wurmonline.server.LoginHandler: Duplicate authentication
[08:30:18 AM] INFO com.wurmonline.server.LoginHandler: Unauthenticated user trying to login, with ip: /[redacted]
 
27. Protected items with no decay, no pickup (locking down props) tend to delay the count in polling.  This is useful for NPC cities for quest areas and large roleplay capital cities with storytelling quest lines, and also props for dungeons so they don't walk off....   Which also brings me to notice in large NPC cities made by GM's for these types of areas also appear to slow down poll timers.  Creating a living breathing city was a great idea to add depth to the NPC potential for immersion but turned out to be the longest areas to poll.    Might want to address why these are taking so long to poll if everything is set to no decay.  Maybe a focus zone that excludes those areas from being polled all together? 
Edited by razoreqx
1 person likes this

Share this post


Link to post
Share on other sites

Welcome first of all, from an australian WUrmian 

 

i created 2 chairs for my house yesterday (thrones) planted and placed in house, then went to create a coffer. I came back with said coffer, the chairs had vanished into thin air.

 

i logged out and back in, thinking that would fix it, but nada, they were gone

Share this post


Link to post
Share on other sites
Special note noticed today:   This obviously shows the 10 calls per execute are being ignored.  As you can see below more rows than 10 were called.   This could be because the cycle is getting behind due to all the other issues previously posted bug report above in the OP. 
6. NUMBER_OF_DIRTY_MESH_ROWS_TO_SAVE_EACH_CALL=10  when this function is called it locks the DB and login threads and the players get a refresh which can last up to 10 mins   No errors are ever reported.

 

[05:40:27 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1216.0104 millis.
[05:40:37 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 988.4304 millis.
[05:40:42 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 636.4794 millis.
[05:40:43 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 577.8503 millis.
[05:41:28 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1349.197 millis.
[05:41:31 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1766.2379 millis.
[05:41:33 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1101.3564 millis.
[05:41:38 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1432.1106 millis.
[05:41:44 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 537.2059 millis.
[05:41:47 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1354.727 millis.
[05:41:50 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 877.7358 millis.
[05:41:52 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1497.3422 millis.
[05:41:54 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 614.0413 millis.
[05:41:57 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1552.397 millis.
[05:41:58 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 799.65393 millis.
[05:42:01 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1498.4039 millis.
[05:42:05 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 2803.2869 millis.
[05:42:07 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1816.9575 millis.
[05:42:12 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1669.2803 millis.
[05:42:14 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1243.011 millis.
[05:42:16 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 992.0 millis.
[05:42:21 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 2141.295 millis.
[05:42:24 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1691.5933 millis.
[05:42:29 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1513.8566 millis.
[05:42:31 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 745.98236 millis.
[05:42:33 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1153.8894 millis.
[05:42:35 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1070.0671 millis.
[05:42:37 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 613.5479 millis.
[05:42:39 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 816.8997 millis.
[05:42:40 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 706.8953 millis.
[05:42:42 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 775.7071 millis.
[05:42:44 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1066.9762 millis.
[05:42:52 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 2883.217 millis.
[05:42:55 PM] INFO com.wurmonline.server.Server: current mem in use: 8362M free mem: 5953M Max mem: 8362M
player count: 57
bytes in: 529415 bytes out: 1962726 total in: 24729153 total out: 193774353
Server uptime: 18900 seconds. Unanswered questions:3
[05:42:55 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1508.4789 millis.
[05:42:57 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 799.7522 millis.
[05:43:05 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 748.0111 millis.
05:43:07 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 742.3907 millis.
[05:43:09 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 533.76654 millis.
[05:43:12 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 833.92816 millis.
[05:43:19 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 573.82275 millis.
[05:43:24 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 757.8361 millis.
[05:43:27 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 779.5829 millis.
[05:43:36 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 665.87006 millis.
[05:43:37 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 649.9792 millis.
[05:43:40 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 746.05975 millis.
[05:43:51 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 755.5276 millis.
[05:43:58 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 945.705 millis.
[05:44:02 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 774.75604 millis.
[05:44:05 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 782.8338 millis.
[05:44:08 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1353.8624 millis.
[05:44:12 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 593.274 millis.
[05:44:15 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 984.4186 millis.
[05:44:18 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 937.72516 millis.
[05:44:21 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 659.0224 millis.
[05:44:25 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1907.9918 millis.
[05:44:27 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1058.2137 millis.
[05:44:31 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1165.3512 millis.
[05:44:35 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1187.5641 millis.
[05:44:37 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1780.7241 millis.
[05:44:42 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 508.22415 millis.
[05:44:44 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1017.12384 millis.
[05:44:49 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1190.565 millis.
[05:44:51 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1077.9474 millis.
[05:44:55 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1064.9136 millis.
[05:44:58 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 2200.3115 millis.
[05:45:00 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 955.72614 millis.
[05:45:02 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1267.9751 millis.
[05:45:05 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 946.73126 millis.
[05:45:10 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 657.0445 millis.
[05:45:14 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1803.8623 millis.
[05:45:18 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1808.8801 millis.
[05:45:22 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 632.30536 millis.
[05:45:25 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 535.3096 millis.

Edited by razoreqx

Share this post


Link to post
Share on other sites

Characteristic stats curve horribly at 30, not sure if this is intended or a bug.

Share this post


Link to post
Share on other sites

I sometimes get this error on the text on large signs, quite often actually. (upper part missing). Especially when just logged in. If sign gets re-planted, the text shows...until sometimes later when the problem re-occurs.

 

sign_text_error.jpg

Share this post


Link to post
Share on other sites
On 7/31/2016 at 7:49 PM, razoreqx said:

[05:40:27 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1216.0104 millis.

 

What kind of storage are you using? This is extremely slow. Either your server is badly bottlenecking on IO throughput or you have some broken hardware.

 

Share this post


Link to post
Share on other sites
12 hours ago, bdew said:

 

What kind of storage are you using? This is extremely slow. Either your server is badly bottlenecking on IO throughput or you have some broken hardware.

 

 

SSD raid 5. 

It was actually a thread thrashing issue.  

I changed USE_SCHEDULED_EXECUTOR_TO_SAVE_DIRTY_MESH_ROWS=true to false which forces this to run on the core game thread limit instead of the executor

SCHEDULED_EXECUTOR_SERVICE_NUMBER_OF_THREADS=8

This fixed this issue.

 

As a side note you should only see the entries below in the logs if there is a problem.  

[05:42:55 PM] INFO com.wurmonline.server.MeshSaver: Finished saving 10 rows for 'SurfaceMesh', which took 1508.4789 millis.

Edited by razoreqx

Share this post


Link to post
Share on other sites

Just had this hit us on Valoria tonight... Got a feeling it's that thing you talked to me about today Razor. If it is... damnit Razor you talked this up!!

 

Quote

[05:36:46 AM] INFO com.wurmonline.server.Server: current mem in use: 2321M free mem: 458M Max mem: 4107M
player count: 34
bytes in: 0 bytes out: 0 total in: 45090042 total out: 376344527
Server uptime: 769500 seconds. Unanswered questions:0
[05:37:22 AM] INFO com.wurmonline.server.players.Player: Nils lost link 5 secstologout.
[05:37:22 AM] INFO com.wurmonline.server.players.Player: Anders lost link 0 secstologout.
[05:37:24 AM] INFO com.wurmonline.server.players.Player: Lumi lost link 0 secstologout.
[05:38:37 AM] INFO com.wurmonline.server.Server: Lag detected at Player Moves (13): 1.559
[05:38:37 AM] INFO com.wurmonline.server.Server: Lag detected at socketserver.tick (15.5): 1.56
[05:38:37 AM] INFO com.wurmonline.server.Server: Numcommands=27, last=0, prev=0 target=0, Message=
[05:38:37 AM] INFO com.wurmonline.server.Server: Size of connections=25 logins=0, redirs=0 exceptions=0
[05:38:37 AM] INFO com.wurmonline.server.Server: Elapsed time (1562ms) for this loop was more than 1 second so adding it to the lag count, which is now: 7763
[05:40:11 AM] INFO com.wurmonline.server.players.Player: Minge lost link 0 secstologout.
[05:40:12 AM] INFO com.wurmonline.server.players.Player: Xloey lost link 5 secstologout.
[05:40:17 AM] INFO com.wurmonline.server.players.Player: Firedancer lost link 60 secstologout.
[05:40:44 AM] INFO com.wurmonline.server.players.Player: Ravenloft lost link 0 secstologout.
[05:41:20 AM] INFO com.wurmonline.server.players.Player: Suniak lost link 0 secstologout.
[05:41:25 AM] INFO com.wurmonline.server.players.Player: Cronus lost link 60 secstologout.
[05:41:28 AM] INFO com.wurmonline.server.steam.SteamHandler: Server connected to steam
[05:41:31 AM] INFO com.wurmonline.server.zones.Zone: Zone at 704, 3136 polled 265 tiles. That took 441.72858 millis.
[05:41:33 AM] INFO com.wurmonline.server.players.Player: Robouk lost link 0 secstologout.
[05:41:46 AM] INFO com.wurmonline.server.Server: current mem in use: 2318M free mem: 515M Max mem: 4107M
player count: 25
bytes in: 0 bytes out: 0 total in: 45090042 total out: 376344527
Server uptime: 769800 seconds. Unanswered questions:0

 

We had a mass kick that booted 9 players in total, that's just some of the server log.

 

Share this post


Link to post
Share on other sites
13 hours ago, Iberis said:

Just had this hit us on Valoria tonight... Got a feeling it's that thing you talked to me about today Razor. If it is... damnit Razor you talked this up!!

 

 

We had a mass kick that booted 9 players in total, that's just some of the server log.

 

 

 

Sorry!    I told you it was coming when you hit 50 unique steam logins and multiple alts....   I can help with some of this ...  hit me up on Steam and i'll help you fix your wurm.ini and

Neko has the cleanup mods.   

[07:36:33 PM] INFO decaytickmod: Destroying log At x[3577.0513] y[12734.458]
[07:36:33 PM] INFO decaytickmod: Destroying wood scrap At x[3569.9812] y[12742.287]
[07:36:33 PM] INFO decaytickmod: Destroying log At x[3571.2585] y[12685.607]
[07:36:33 PM] INFO decaytickmod: Destroying log At x[3570.795] y[12701.203]
[07:36:33 PM] INFO decaytickmod: Destroying log At x[3561.8286] y[12740.749]
[07:36:33 PM] INFO decaytickmod: Destroying wood scrap At x[3563.1387] y[12750.04]
[07:36:33 PM] INFO decaytickmod: Destroying log At x[3433.0378] y[12818.163]
[07:36:33 PM] INFO decaytickmod: Destroying log At x[3454.773] y[12817.183]
[07:36:33 PM] INFO decaytickmod: Destroying wood scrap At x[3475.1145] y[12821.254]
[07:46:31 PM] INFO decaytickmod: Destroying dirt At x[12464.463] y[4070.1814]
[07:46:31 PM] INFO decaytickmod: Destroying dirt At x[12461.057] y[4074.8809]
[07:46:31 PM] INFO decaytickmod: Destroying dirt At x[12461.057] y[4074.8809]
[07:46:31 PM] INFO decaytickmod: Destroying dirt At x[12461.699] y[4070.0867]
[07:46:31 PM] INFO decaytickmod: Destroying dirt At x[12458.215] y[4057.8162]
[07:46:31 PM] INFO decaytickmod: Destroying dirt At x[12457.624] y[4054.4434]
[07:46:31 PM] INFO decaytickmod: Destroying dirt At x[12457.624] y[4054.4434]
[07:46:31 PM] INFO decaytickmod: Destroying dirt At x[12457.624] y[4054.4434]
[07:46:31 PM] INFO decaytickmod: Destroying dirt At x[12450.862] y[4074.8455]
[07:46:32 PM] INFO nofogspiders: Hey, I'm in CreateAchievement!
[07:46:05 PM] INFO decaytickmod: Destroying wood scrap At x[13341.42] y[8142.219]
[07:46:05 PM] INFO decaytickmod: Destroying wood scrap At x[13341.42] y[8142.219]
[07:46:05 PM] INFO decaytickmod: Destroying wood scrap At x[13341.42] y[8142.219]
[07:46:05 PM] INFO decaytickmod: Destroying wood scrap At x[13341.42] y[8142.219]
[07:46:05 PM] INFO decaytickmod: Destroying wood scrap At x[13341.42] y[8142.219]
[07:46:05 PM] INFO decaytickmod: Destroying wood scrap At x[13341.42] y[8142.219]
[07:46:05 PM] INFO decaytickmod: Destroying wood scrap At x[13341.42] y[8142.219]
[07:46:05 PM] INFO decaytickmod: Destroying wood scrap At x[13341.42] y[8142.219]
[07:46:05 PM] INFO decaytickmod: Destroying wood scrap At x[13341.42] y[8142.219]
[07:46:05 PM] INFO decaytickmod: Destroying wood scrap At x[13341.42] y[8142.219]

 

If you find out how many cores you have set this

USE_SCHEDULED_EXECUTOR_TO_SAVE_DIRTY_MESH_ROWS=false

which forces this to run on the core game thread limit instead of the executor

then set: 

SCHEDULED_EXECUTOR_SERVICE_NUMBER_OF_THREADS=8   (this depends on how many cores you have)  its 20 by default which is WAY to high. 

Edited by razoreqx
1 person likes this

Share this post


Link to post
Share on other sites

New patch today 1.1.1.1:

Leather adventurer hat - hair is sticking out through the hat.

Share this post


Link to post
Share on other sites

Looks around, where is this brand new person with no community interaction that is supposed to be responding to this but only made the OP and nothing else?

Share this post


Link to post
Share on other sites

Looks around, where is this brand new person with no community interaction that is supposed to be responding to this but only made the OP and nothing else?

Share this post


Link to post
Share on other sites

Just had a thing happen today on Valoria. A gm character had shoulder pads on from before the update. Tried taking them off and it caused a crash.

 

Quote

[05:07:43 PM] SEVERE com.wurmonline.server.Server: com.wurmonline.server.items.Item.isRiftLoot()Z
java.lang.NoSuchMethodError: com.wurmonline.server.items.Item.isRiftLoot()Z
    at com.wurmonline.server.spells.Spell.mayBeEnchanted(Spell.java:225)
    at com.wurmonline.server.behaviours.ItemBehaviour.getBehavioursFor(ItemBehaviour.java:1620)
    at com.wurmonline.server.behaviours.WrappedBehaviourProvider.getBehavioursFor(WrappedBehaviourProvider.java:116)
    at org.gotti.wurmunlimited.modsupport.actions.ChainedBehaviourProvider.getBehavioursFor(ChainedBehaviourProvider.java:203)
    at com.wurmonline.server.behaviours.BehaviourDispatcher.requestActionForItemsBodyIdsCoinIds(BehaviourDispatcher.java:426)
    at com.wurmonline.server.behaviours.BehaviourDispatcher.requestActions(BehaviourDispatcher.java:248)
    at com.wurmonline.server.creatures.Communicator.reallyHandle_CMD_REQUEST_ACTIONS(Communicator.java:7022)
    at com.wurmonline.server.creatures.Communicator.reallyHandle(Communicator.java:2372)
    at com.wurmonline.communication.SocketConnection.tick(SocketConnection.java:615)
    at com.wurmonline.communication.SocketServer.tick(SocketServer.java:172)
    at com.wurmonline.server.Server.run(Server.java:2411)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)

 

After that we booted up the server again.. every time that gm char logged back in the server would crash again.

 

Only way to get it fixed was to deleted the character the the shoulderpads entirely via the database. u.U;

Share this post


Link to post
Share on other sites

Thanks for reporting this before I made the same mistakes! I was wearing shoulder pads haha.

 

Also I am working on making them craftable, so this is a sign I definitely need to reproduce them as new items without the Rift loot flags.

Share this post


Link to post
Share on other sites

I have a problem with cave dwellings and locks.

Locks on the doors are gone (four different houses in mines)....and if you try and attach a lock...the timer starts, but at the end you get no confirmation that is has attached...and the lock just vanishes...and the door still has no lock.

Destroying door and rebuilding does not work, even if building something else (like portcullis).

 

Only way is to Annihilate the entire bugged buildings - rebuild - locks work.

Edited by Jukken

Share this post


Link to post
Share on other sites

Treasure chests have a chance of spawning with a horse statue inside, this statue cannot be loaded or removed by the player.

Share this post


Link to post
Share on other sites
  • #maxCreature count continues to be ignored.    Populations can extend by over 10k over the limit
  • Support tickets are still getting ID's screwed up across clusters.
  • HOTA are flagged as focus PVP and players are red, but you cannot attack them..  This is on Creative map.  PVP focus zones worked prior to last patch
  • duplicate authentication bug is still an issue.
  • wurm.ini player purge is still not working correctly and has no cleanup in database tables for achievements
  • fog spider event is still having executor thread issues and cause thread thrashing on populated maps.
  • Active HOTA still is bugged if the cluster is rebooted and requires the focus zone to be reset as one method of fixing.
  • Traders can be killed leaving all the trader loot on its corpse.   Even if perms are not set correctly the corpse should not be left behind for players to loot.
  • Mine doors still lose permissions randomly
  • when unarmored i show no bonus, "should show +30%  (casting + archery) (only fix is to relog with correct armor which is a pain)
    when equipped cloth armor i show no bonus, "should show +30%
    when equipped plate i show "+30% and -30%" , "should show - 30%
  • more to post..... 

 

 

Exploit:  Servers have the ability to fake alts as actual server counts.   This most certainly is not game breaking but it sure would make it hard for players to find public servers which actually have players on them :) 

Edited by razoreqx

Share this post


Link to post
Share on other sites

Some players on my server are getting duplicate authentication bug since last patch. Running a two-server cluster if that makes any difference.

 

The server seems to have a bug with altar domains, if the new system is enabled, no domains will occur. If disabled (override) - they occur. No idea on why this is.

Edited by Jukken

Share this post


Link to post
Share on other sites

Hell Horses, Lava Fiends, Hell Scorpius still do not spawn.

 

Since previous update creatures do not seem to be getting fat, they are not hungry and are grazing as normal, not starving. They are just staying at a nutrition level of 0 in the database.

(this is on a modded server will test further without mods and update post)

Edited by ausimus

Share this post


Link to post
Share on other sites
5 hours ago, ausimus said:

Hell Horses, Lava Fiends, Hell Scorpius still do not spawn.

 

Since previous update creatures do not seem to be getting fat, they are not hungry and are grazing as normal, not starving. They are just staying at a nutrition level of 0 in the database.

(this is on a modded server will test further without mods and update post)

 

You can fix this by putting down lairs where you want them to spawn.   This can be in caves or above ground.   Just make sure they're 50 tiles apart.   Great for respawning dungeons :) 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now