• Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About AllThingsGaming

  • Rank

Recent Profile Visitors

1413 profile views
  1. It's not really a bug, it's due to the changes on how they do STEAM authentication. They do it every time you go into or switch a server within the same node.. So you log into PvE, and it verifies you. Then when it redirects you to say a PvP node if you were on PvP, it then re-verifies you and adds the number to the new node and removes it from the first. Before it would only verify you on the login server.
  2. Wurm is not that intensive to need separate hardware honestly.
  3. Responded via PM, tclunatic. In other news, the PvP is really heating up, there was a massive fight over the previous HotA just the other day!
  4. I assume this is changing the REALDEATH column from 2 to 3? Only one I could see that was possibly related.
  5. Is it possible to undo a champion death?
  6. Just a quick update for those looking for a solid PVP server. We now have over 45 registered people playing. We average about 14 during peak US evening times, less during European times. And have a nice gathering for our events ran every weekend. Come one come all!
  7. This is a cacheing issue. If you edit the index.html file like it says to on this stackover flow page. You should never run into a cacheing issue again as long as you remember to change the version number every time you make a change. This should probably be added to the actual file that generates the files. <script type="text/javascript" src="data.js"></script> <script type="text/javascript" src="config.js"></script> <script type="text/javascript" src="map.js"></script> Should be <script type="text/javascript" src="data.js?version=1.0.0"></script> <script type="text/javascript" src="config.js?version=1.0.0"></script> <script type="text/javascript" src="map.js?version=1.0.0"></script> Then once the document is changed it would change to <script type="text/javascript" src="data.js?version=1.0.1"></script> <script type="text/javascript" src="config.js?version=1.0.1"></script> <script type="text/javascript" src="map.js?version=1.0.1"></script> This would force any browser to request the file from scratch and continue to cache it until the link changes. Could also generate a random string. More info on this located
  8. Beyond a joke is an understatement. CC is driving what little Wurm community we have further and further away. Get your ###### together CC.
  9. Good to know our database isn't blowing up!
  10. Well this makes sense... I thought my database was going wonky! So divide the numbers by 4 and that is the location or?
  11. Greetings, We have recently noticed that our POSX / POSY variables within our database are all outside of the scope of our map. Our map is 4096x4096, and the positions are coming in at 6000x6000 or something along those lines. If you locate the item through #itempos in-game, it shows the correct position. But, the database is not showing the proper position. We've also recently begun having items disappear, and we're not quite sure what is causing this to happen. It's been happening since the last two patches.
  12. The result of Code Club not testing their work. A STEAM restart is a temporary fix but it will continue to occur until they decide to fix it.
  13. Correct. The newest patch has rendered many Wurm Unlimited players unable to play due to the new bug. Code Club has gone down hill significantly, it's unfortunate.
  14. We looked into it and have yet to find a consistent copy of all the kills. Only found two of the many.
  15. @MootRed All you would need is to parse the data into an SQL database which a webpage shows as ranked. It would not be hard at all depending on how the kills are formatted.