AfterWorld Survival Forum

Recently, players have asked to know where they will revive if the die / request revival.

I have provided a map with the revive boundaries where all 7 revive points are DNA registered.
However, that is not going to be much help to Newcomers as they will only have two of these registered (I assume a Newcomer has Mugen Village and New Urengoy DNA registered after they arrive at New Urengoy).

Suggestion: Add a special marker to the mini-map that allows a player to indicate a revive point. Have these markers indicate which one is closest to the player (e.g. marker blinks; different color in the marker list).

This will be more important in the Asian World map where there are likely to be dozens of revives scattered across the world.

I think revival points are part of the challenge of playing the game.   Automating/Eliminating all the challenges leaves in EU-WoW zone.

DL doesn't need to do this. However, someone will create an interactive map / utility that does the same since all you need is your map coordinates and a list of revive points.

are coordinates written somewhere into local drive log files? Like sau loots and chat are.

Without that coordinates data in log files as plain text, forget it. Creating tool which would use OCR would be just too much trouble. Both for coder and end-users.

The coordinates are written to the log files (see https://my.afterworld.deelogic.net/survival/knowledge-database/building-inside-the-swamp/msg4480/#msg4480 for an example where that data was used).
And the file is updated real time.

The coordinates are written to the log files (see https://my.afterworld.deelogic.net/survival/knowledge-database/building-inside-the-swamp/msg4480/#msg4480 for an example where that data was used).
And the file is updated real time.

This is only true when you press the Date/Time/Coordinates keyboard key, 'O' by default. Unless you use a macro program to repeatedly press this for you...

delayed action would work.
Press 'O' ingame, it will cause coordinates being written into log file. At the same time your code is waiting for hotkey 'O' and while noticing it pressed, starts it's assigned function.

First thing that function is doing after being initiated is going to brief sleep (about 200ms, giving game some time to write into logs) then accessing the log itself

It skims trough the log file end section with regular expression looking for coordinate data and extracts the latest entry.

Then your code compares extracted data against SQLite database file and returns closest match.
Technically doable by the degree you described (you are at xx.xx, go to the yy.yy for getting to zz) using pretested and stored coordinates for answer.

Not doable once you start wishing for real time predictions. Not without knowing exactly by meter how and where the revival zone borders go.

Quote from: Jarod "Brickwit" McBrickerton on March 31, 2014, 05:58:06 pm

Quote from: Event "Janе" Horizon on March 29, 2014, 09:27:41 pm

The coordinates are written to the log files (see https://my.afterworld.deelogic.net/survival/knowledge-database/building-inside-the-swamp/msg4480/#msg4480 for an example where that data was used).
And the file is updated real time.

This is only true when you press the Date/Time/Coordinates keyboard key, 'O' by default. Unless you use a macro program to repeatedly press this for you...

Why would a player need to be continuously reminded of where the revive boundary is?
Wouldn't it be enough that a player is at coordinates 12.45E 67.89N,  presses O and is told that they need to go to 24.68E 35.79N to revive at their selected outpost? They then use their mini-map to get to those coordinates?

I was reading what Shaqan said and your response as an attempt to analyse where a user is at any given time rather than comparing the current position to the Outpost locations. My bad, nevermind the quoted post.

I think your last post sums up the basic requirements pretty well. The only user input required would be the names of the towns where the player has already registered DNA and the rest would be automatic, especially if the utility watches for new registrations while it's running.

We all agree that it appears to work based on which location is closest when you die or manually call the revive bot, but it would take verification from the devs to know 100% for sure.

I think you're right about needing an SQL database, especially for growth. A simple list would work right now, but it's never a good idea to create a program with just a list of constants when that data is not 100% chiseled in stone. And since we already know that there will be additional points coming the best use of time is to build in the ability to add those points as easily as possible.

I still do not see why a database is required.

more flexibility. It does not concern end users anyway because SQLite is serverless by nature. Convenient way for storing data/variables outside your code and faster than using text files. Plus extra functionalities you get with databases but can't do with text files.