AfterWorld Survival Forum
Discussions => Ideas and suggestions => Topic started by: Event "Janе" Horizon on March 27, 2014, 07:07:44 pm
-
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.
-
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.
-
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 (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. :)
-
k, had no way for checking it out, sitting behind laptop
-
The coordinates are written to the log files (see https://my.afterworld.deelogic.net/survival/knowledge-database/building-inside-the-swamp/msg4480/#msg4480 (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...
-
The coordinates are written to the log files (see https://my.afterworld.deelogic.net/survival/knowledge-database/building-inside-the-swamp/msg4480/#msg4480 (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?
-
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.
-
I do not think a database is required.
There are only 7 revives at the moment; of which a player will have between 2 and 7 revives registered.
You do not need to 'pre-test' every point between every revive - the rule is that you revive at the nearest outpost where you have registered your DNA.
So ...
1. draw a straight line between yourself and each DNA registered revive.
2. workout which line is the shortest. This is the nearest revive.
3. if that is your chosen revive point - TA DA - revive now.
4 If you want to revive at an output that is not the nearest - work out where along the line between you and the chosen revive that a point is closer to the chosen revive than any other revive.
5. move directly towards that point until you are past it and - TA DA - revive.
or something like that.
-
The coordinates are written to the log files (see https://my.afterworld.deelogic.net/survival/knowledge-database/building-inside-the-swamp/msg4480/#msg4480 (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.
-
So it would need something along the lines of vector calculations. Are you 100% sure that revivals work on "closest approach" principle?
SQL would still be in order. Easier to adjust to coordinate grid shifts and/or add new revival points in single database file than to modify bunch of global constants in code itself.
-
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.
Even if all 50 Asia world outposts are implemented - these still would static points on the map and easy to add to a list. So the below web code will still be more or less instantaneous.
NOTE: the mini-map doesn't seem to show you your exact coordinates (e.g. 54N 97.78E --> 54N 97.79E jumps to 54N 97.81E). May need to put a 0.04 buffer in the to ensure you get to the right revive.
<html>
// This code is public domain. It can be used and changed without violating copyright.
// However, it would be nice to have an acknowledgement of Event "Jane" Savon's contribution.
<script>
// Data
var defaultRevives = [
["Mugen Village",49.56, 85.79],
["New Urengoy",58.61, 94.61],
["Norilsk",60.72, 101.14],
["Saransk", 50.98, 100.68],
["Saransk West",51.16, 94.69],
["Surgot",54.59, 87.98],
["Turukhansk",56.17, 101.87]
];
// Classes
function Player(north,east) {
var mNorth = north;
var mEast = east;
this.GetPosition = function() { // --> Point
var point = new Point();
point.North = mNorth;
point.East = mEast;
return point;
}
}
function Point() {
this.North = 0;
this.East = 0;
this.ToString = function() { // --> String
return this.North.toFixed(2) "N " this.East.toFixed(2) "E";
}
}
function Revive(name,north,east) {
var mName = name;
var mNorth = north;
var mEast = east;
var mId = Revive.id ;
this.GetId = function() { // --> id
return mId;
}
this.GetName = function() { // --> name
return mName;
}
this.GetPosition = function() { // --> Point
var point = new Point()
point.East = mEast;
point.North = mNorth;
return point;
}
}
Revive.id = 0;
function Revives() {
var list = new Array();
this.Add = function(revive) { // --> void
list[revive.GetId()] = revive
}
this.GetByName = function(name) { // --> revive
for (i=0; i<list.length; i ) {
if (list[i].GetName() == name) {
return list[i];
}
};
}
this.GetList = function() { // --> revives list
return list;
}
}
// Functions
function GetNearestRevive(revives, point) { // --> Point
var nearestRevive = null;
var nearestDistance = Math.pow(2,32) -1;
var reviveList = revives.GetList();
var reviveCount = reviveList.length;
for (i=0; i< reviveCount; i ) {
revive = reviveList[i];
position = revive.GetPosition();
dist = Math.pow(
Math.pow((point.East - position.East),2) Math.pow((point.North - position.North),2)
,0.5);
if (dist < nearestDistance) {
nearestDistance = dist;
nearestRevive = revive;
}
}
return nearestRevive;
}
function SetRevives(reviveList) { // --> Revives
var revive;
var revives = new Revives();
for (i=0; i<reviveList.length; i ) {
revive = new Revive(reviveList[i][0],reviveList[i][1],reviveList[i][2]);
revives.Add(revive);
}
return revives;
}
// Main
var revives = SetRevives(defaultRevives);
var player = new Player(54,97.77);
var revivePoint = GetNearestRevive(revives,player.GetPosition());
alert("Player at " player.GetPosition().ToString() " revives at: " revivePoint.GetName());
var player = new Player(54,97.78);
var revivePoint = GetNearestRevive(revives,player.GetPosition());
alert("Player at " player.GetPosition().ToString() " revives at: " revivePoint.GetName());
</script>
</html>
-
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.
-
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.
That theory went out of airlock.. been working on little program past few days. Started in Python but realized I don't know it well enough and switched back to AutoIT
(https://www.upload.ee/thumb/3981474/hhihi.png) (https://www.upload.ee/image/3981474/hhihi.png)
Stopped at 55.16N 97.10E and pressed Ctrl+D.
by that theory I should have ended up back in NU, since it was closest, Turukhansk was actually bit more distant that SarW. Nevermind the order of outposts in GUI, except for present pos coordinates, names are just static labels, so I know they align properly. Editor console had the live data
-
Well, this melts my brains :o
55.16N 97.10E is definitely to the right of the red NU-Turukhansk line on my map.
However, the red line is drawn perpendicular to the midpoint of a line directly between NU-Turukhansk.
So every point on that line should be equal distant to NU-Turukhansk.
So a line from 55.16N 97.10E to Turukhansk should be shorter than from that point to NU.
Yet it isn't.
{pop} there goes my sanity.
-
btw, how were the revival center outpost coordinates taken? says 58.61N 94.61E for New Urengoy.
But if you go outside, and stand next to the wall to the Outpost building (building side with the translukators in it) you'd get ingame coordinates of 58.82N 94.5E
Have'nt compared other building coordinates yet.
-
The coordinates in the wiki might be from different actual points rather than a consistent location relative to the buildings themselves. One player might have use the position right outside the door on one end while a second might have walked to the closest point (s)he could reach from outside, while a third might have used the coordinates on the in-game map.
The hard part is knowing the precise location to use when determining where we'll be cloned, especially if a utility is going to be developed to tell a player which Outpost is closest to them. The other hard part is not knowing if there are other variables at play with the whole system, which wouldn't surprise me in the least.
-
I suppose actual "Outpost"'s are sort of dedicated "world" not actually inside the building. Operating the building door simply gives you access to it. Building sizes inside and outside do not look like they actually match.
-
I suppose actual "Outpost"'s are sort of dedicated "world" not actually inside the building. Operating the building door simply gives you access to it. Building sizes inside and outside do not look like they actually match.
The outposts are definitely separate to the outside world. DL mentioned something about they are too complex in some game engine way to allow you to simply walk into them as we could in Alpha.
However, I do not think the slight differences in coordinates can result in such a large discrepancy in the location of the revive point.
I suspect that the N & E coordinates are not 1:1 ... i.e. 1oN is not the same distance as 1oE - which is why the lines on the map look and act right but reviving using the coordinates is wrong.
-
I suspect that the N & E coordinates are not 1:1 ... i.e. 1oN is not the same distance as 1oE - which is why the lines on the map look and act right but reviving using the coordinates is wrong.
This is correct. Whether by design or accident, the latitude coordinate changes faster when running 50m N/S than the longitude coordinate changes when running 50m E/W.
-
Ok, that's what's screwing up the calculations then.. Thanks for pointing it out :)
-
Ok, that's what's screwing up the calculations then.. Thanks for pointing it out :)
Search and you'll find my measurements of 1o<-->meter conversion.
-
ok, will do, when I get bored enough with the game again.