Another Mapping Service

[dafels]

I've created another mapping service at
https://hnhmap.xyz

It works pretty well if you are a village or a group that wants to share markers and maps between each other. Your map is private with the users you decide to share the map with.

Some things you can do:

1. Create custom markers on the map
2. Upload your location on the map, so you are able to see where you are on the map (this is of course if you choose to do so)
3. Ping on the map
4. Manage who has access to the map, invite new users to the map, etc...
5. many more

To get access:

1. Register a user
2. Join Discord: https://discord.gg/PTdMrVeq3q, fill out the form in #request-access or just DM me in Discord the username you registered and I will create a map instance for you. (the people that you will want to share your map with doesn't have to do this)

Alternitavely you can host your own instance of the map on your own server, download the GitHub sources and deploy it on your server (I suggest you to use Docker for simplicity, there's also a guide for that in the repo. If you need help with it you can ask in Discord). Contributions are welcome also.

Note:
It is in testing stage at the moment, since I haven't used it extensively myself yet, but if there's any issues feel free to reach out on Discord.
I've tested this and verified it works with Ender/Hurricane client, probably also works on other clients where you can put in the map url

If you have any ideas I could implement into the map, feel free to suggest them and reach out on Discord

[derkami]

My updates are also in the works for 16.1.

[whateverisfine]

interesting, will check and give a feedback. Do you have any plans to add a cookbook?

[dafels]

My updates are also in the works for 16.1.

[dafels]

Do you have any plans to add a cookbook?

I can create one, but I am not sure if the common custom clients actually send that data out of box.

If not then it is probably not a option, since those clients would need to integrate with the cookbook and I am afraid it would need some coming forward from the client owners to implement in that case even though I could create PRs in those clients to send the needed data similar to how map is sent. Have to do a bit of research first. Even though it is a very important thing.

[whateverisfine]

Do you have any plans to add a cookbook?

I can create one, but I am not sure if the common custom clients actually send that data out of box, if not then it is probably not a option, since those clients would need to integrate with the cookbook and I am afraid it would need some coming forward from the client owners to implement in that case. Have to do a bit of research first. Even though it is a very important thing.

kami use single endpoint for map/cookbook in his project.

[Nightdawg]

GitHub sources

based

a worthy opponent

your worthy opponent shared sources, he's already winning

[derkami]

Do you have any plans to add a cookbook?

I can create one, but I am not sure if the common custom clients actually send that data out of box, if not then it is probably not a option, since those clients would need to integrate with the cookbook and I am afraid it would need some coming forward from the client owners to implement in that case. Have to do a bit of research first. Even though it is a very important thing.

kami use single endpoint for map/cookbook in his project.

I just used existing cookbook client implementation, changed some things because i didn't like the way it transferred date, and build a backend for it.
Since it was just to check If i could make it and not an important part of what I'm doing, I never payed it much attention.

Ard implemented this aswell and has sources for his implementation.
https://github.com/Cediner?tab=repositories

GitHub sources

based

a worthy opponent

your worthy opponent shared sources, he's already winning

I see. Well it probably will not happen this year for me. But I do have plans.

@dafels:
How much vibe was used for this?
I'll try this one out and feed it with all i have with an andyleaps compatible export.
Or not... Import is not Implemented yet.

Also what are you doing with 2 different worlds if grid_ids accidentally overlap?
This is why I'm currently updating all my shit to include the genus (GameUI.genus) to all requests, which will again create incompatibilities to all existing implementations...

I would like to avoid that if possible.
I'm currently testing my changes and if it checks out i'll have a single git commit on my client for that.
Maybe we can work on this compatibility problem together, that way we can produce a client side implementation that can be adapted by all custom clients.

[dafels]

I just used existing cookbook client implementation, changed some things because i didn't like the way it transferred date, and build a backend for it.

I'll probably just adapt to your client's way of sending the food data and create a public cookbook from that. Sadly, it is only your client(active) out there that has a food integration from what I have seen, even though having it is beneficial for everyone

How much vibe was used for this?

Most of it was vibed

Also what are you doing with 2 different worlds if grid_ids accidentally overlap?
This is why I'm currently updating all my shit to include the genus (GameUI.genus) to all requests, which will again create incompatibilities to all existing implementations...

Don't think this would be much of a issue for me, since I think barely anyone needs map in W16.0 now, so most of the maps will be W16.1 from start and yet doing anything about it would be very problematic since clients don't send that. Even though in my setup you could create user(map instance/tenant) for other world separately since all the maps are isolated on the tenant level. I think dealing with this in my case would be waste of time atm

[derkami]

Also what are you doing with 2 different worlds if grid_ids accidentally overlap?
This is why I'm currently updating all my shit to include the genus (GameUI.genus) to all requests, which will again create incompatibilities to all existing implementations...

Don't think this would be much of a issue for me, since I think barely anyone needs map in W16.0 now, so most of the maps will be W16.1 from start and yet doing anything about it would be very problematic since clients don't send that. Even though in my setup you could create user(map instance/tenant) for other world separately since all the maps are isolated on the tenant level. I think dealing with this in my case would be waste of time atm

Understandable.

The Food back end is astronomically simple.
Here are the models:

Code: Select all

public class FoodInfo
{
   public string genus { get; set; } = "unknown"; // this is already for my implementation, but since missing fields are getting ignored anyway on serialization and deserialization it doesn't really matter
   public string itemName { get; set; } = "";
   public string resourceName { get; set; } = "";
   public int version { get; set; } = 0;
   public int energy { get; set; } = 0;
   public double hunger { get; set; } = 0;
   public List<FoodIngredient> ingredients { get; set; } = new List<FoodIngredient>();
   public List<FoodFEP> feps { get; set; } = new List<FoodFEP>();
}

public class FoodFEP
{
   public string name { get; set; } = "";
   public double value { get; set; } = 0;
}

public class FoodIngredient
{
   public string name { get; set; } = "";
   public int percentage { get; set; } = 0;
}

You have basically 1 endpoint

Code: Select all

[HttpPost("client/{token}/food")]
public ActionResult Post(string token, [FromBody] Dictionary<string, FoodInfo> foodList)


You can just fill this Dictionary with the stored data and produce the json file the shubla front-end needs to function:

Code: Select all

Dictionary<string, FoodInfo> foods = new Dictionary<string, FoodInfo>();
// fill it however you see fit
string json = JsonConvert.SerializeObject(foods)


That's basically all. The frontend is nothing but a ripped compiled version of the cookbook which get's the json data fed in. I didn't had the muse to create a new frontend for that yet.