ire-mudlet-mapping / achaeacrowdmap Goto Github PK

Placing this here as a reminder to myself to look into the feature system of the map that was implemented after the crowdmap was originally started in place of room marks.

While writing some scripts to navigate Eleusis I ran into a few bugs while using crowdmap. Here are the details:

42090 needs the south exit to be locked.
42092 needs the north exit to be locked.
42090 and 42092 both connect to each other via the special exit push door.
Comment: A directional exit and door is present there but it is locked and that's the only way in or out.

42100 and 42098 both connect to each other via the special exit push gate

6765's down exit should be set to 41875, but it is currently 13201.
Comment: The up exit from 13201 is fine

Thanks

Currently, the GitHub pages site is a placeholder since we only really use it as a CDN. However, we could use the data and space to host an interactive viewer if the map. See https://github.com/Delwing/mudlet-map-reader for the main project.

Good evening,

It seems that when mapping "create exit line" is causing Mudlet to crash. Specifically I had been trying to turn the solid line into a "dot dot dot" or "dash dash dash" and mudlet would just nope itself out of existance.

This is perhaps a translation error in the JSON file creation. Some of the general data is appearing buried in the "Haila-ele" area userData (First image). Area continent lists, ferry rooms, mapping landmark rooms, etc. This data should likely be appearing under the top level userData object (Second image).

For a future PR we found some rogue labels in the latest PR and they should be removed at some point.

#110

Would a tool like this be useful for diffs of the upcoming JSON map? https://github.com/trailofbits/graphtage

New potential danger rule to ensure all wormholes are locked by default in the map.

Let danger check, whether areas are locked.

Hashan's commodity shop has a feature of "shop" which should be changed to "commodityshop"

New issue has arrived. I was able to map without error on 4/10/22 but attempts to add to the map on 9/10/22 produce this error in every room.

(mapper): Oops! Has a small problem ([string "Script: mmp.mappingNewroom"]:268: attempt to index
field 'envids' (a nil value)).
view steps
(mapper):

Dense canopy.
The sun sets, its dimming rays lancing across the sky and lighting the dim
edges of cloud that hang there. A reddish orange rose blooms here, splashing
the environs with vibrant colour.
You see exits leading north, south, west, northwest, and in.
550h, 512m, 1396e, 1475w ex-rl

(mapper): Room: Dense canopy #: 12706 area: Aerinewild, the (198)
(mapper): Coordinates: x:9, y:-2, z:0, locked: nope, weight: 1
(mapper): Environment: ? (4)
(mapper): Exits (5):
in -> A bough-roofed cottage (56028)
northwest -> Sunny vale (12689)
south -> Secluded corner (12701)
west -> Virescent dell (12698)
north -> Emerald hollow (12710)
(mapper): Stuff you can do:
Clear all labels (in area) (whole map)
Check for mapper & map updates (force map)
(mapper): version 22.9.1.

vlua gmcp.Room.Info
{
area = "the Aerinewild",
coords = "198,9,-2,0",
desc = "As you enter this section of the forest, the branches overhead appear to reach out to one
another and intertwine like clasped hands. The light from the sun barely filters through, casting a
hazy glow over the path upon which you walk. The small path that meanders through the trees here is
slightly overgrown and the pin clover that lies along either side of it brushes up against your
ankles as you walk by. The heady smell of the trees fills your senses and reminds you of the years
that have gone into the creation of this ancient wonder of nature.",
details = {},
environment = "Forest",
exits = {
in = 56028,
n = 12710,
nw = 12689,
s = 12701,
w = 12698
},
map = "www.achaea.com/irex/maps/clientmap.php?map=198&building=0&level=0 9 7",
name = "Dense canopy",
num = 12706
}

in
(mapper): Oops! Has a small problem ([string "Script: mmp.mappingNewroom"]:268: attempt to index
field 'envids' (a nil value)).
view steps
(mapper):

A bough-roofed cottage. (indoors)
A plush velvet cushion has been set out here. An opalescent bottle capped with
a little ship on a cork has been left here. A blanket lies here, the dark cloth
folding upon itself. A plush velvet cushion has been set out here. A sturdy,
spacious oaken bunkbed stands here. A dark couch with soft leather seats waits
here. There are 2 porcelain cups painted with a smoky city containing blueberry
honey tea here. A thick green blanket has been strung to the branches here.
Glancing nervously about the surroundings, Hiedra surveys the locale with a
paranoid eye.
You see a single exit leading out.
550h, 512m, 1398e, 1475w ex-rl

(mapper): Room: A bough-roofed cottage #: 56028 area: Aerinewild, the (198)
(mapper): Coordinates: x:10, y:-2, z:0, locked: nope, weight: 1
(mapper): Environment: ? (-1)
(mapper): Exits (1):
out -> Dense canopy (12706)
(mapper): Stuff you can do:
Clear all labels (in area) (whole map)
Check for mapper & map updates (force map)
(mapper): version 22.9.1.

vlua gmcp.Room.Info
{
area = "the Aerinewild",
coords = "",
desc = "Nestled amidst gnarled roots and the sturdy trunk of their parent tree, living wood
composes the ligneous walls of this secluded cottage. Piled stones rise in a low wall at the
broadest angle of the natural structure, a rugged gap left in the flower-clad rockwork to permit
entrance and exit from the open-air home. Softening the hard dirt underfoot sprawls a series of
woven rugs in a dizzying array of bright and vibrant colours, set all about the indentation of a
small firepit at the centre of the space. Wisps of fragrant smoke drift in languid streams from the
smouldering embers left within to escape through the absent roof, ascending towards the swaying
boughs far above.",
details = { "indoors" },
environment = "Nothing",
exits = {
out = 12706
},
map = "www.achaea.com/irex/maps/images/lost.png 2 2",
name = "A bough-roofed cottage (indoors)",
num = 56028
}
https://ada-young.com/pastebin/o8XqOAEJ

VIEW STEPS RODUCES :
stack traceback:
[string "Script: mmp.mappingNewroom"]:317: in function <[string "Script: mmp.mappingNewroom"]:312>
[string "Script: mmp.mappingNewroom"]:268: in function <[string "Script: mmp.mappingNewroom"]:89>
[C]: in function 'xpcall'
[string "Script: mmp.mappingNewroom"]:88: in function <[string "Script: mmp.mappingNewroom"]:86>

As part of #16 I noticed that the special exit was not used until I locked the existing exits from 42090 and 42092. I suggest that special exits should possibly be considered first priority when it comes to determining the way to exit a room.

Potential new danger rule to review if there are any shops (rooms with the "shop" feature) with a down exit, they should not have a down exit per the PR checks.

53005 - Inside the world tree.
ISSUE : Looping failure
(9 - send("embrace flame") mmp.customwalkdelay(10))
I cannot fathom the meaning of "send("embrace".

• Recommend re-visiting the spe link.
  Fixed in Aster Keep, Ancyra, Aerinwild, Oh My! Update.

Since the introduction of danger and the recent addition of the minified JSON map, we have a number of files that don't need to be published to GitHub pages or could be generated before publishing. I propose we restructure the repository a little to account for this.

I'd like to introduce a new default branch development similar to the current gh-pages, but with the static content for the webpage in a subdirectory. We could then have a GitHub action copy the map data on every commit to the default branch and generate additional content as well. Then we publish a subdirectory to the gh-pages branch, which will be the source for the website.

A plateau high in the mountains (60724, in Actar, the Valley of) -> worm warp -> In the shallows of Lake Muurn (7988, in Muurn Lake)

60724 is locked with Merrywick availability. This wormhole does exist, but for the time being loops the player to the Cave. How should this be dealt with?

New area opened up. it can be mapped to Area 94

Petitioning the higher-ups to allow a roommark for the Everglade (pronoun changing rom) to be added to the crowdmap.

There should probably be a file in the repo that contains all the valid room marks to be used in a danger rule to ensure those are the only marks in the crowdmap. Currently the list only exists in the wiki...also if it were in the repo it could be tracked and reviewed if anything is changed.

Then if we wanted to add a new room mark it would have to be added to both the file and the map.

Wonder if this rule could check both ways? Compare the file to the map and vice versa? Not sure what would be best here.

Uploading the minified JSON map is a manual process. We could automate it.

Room 11935 in the LHG is not positioned correctly.

A recent map update has affected the shop names in Delos

I'd like to add a new danger check that prints a warning if the main map file is not modified. It will do nothing, if the file is modified. The warning will not make the check fail, but might give a hint if the file name is wrong.

We want our maintainers to upload a Mudlet JSON map as well. However, I don't think we use it for for diffs as they are often huge and the map diff comment is better suited in my opinion. Additionally, it doesn't always seem to reflect the actual map data in the binary file.

If we stop uploading it manually, we may be able to generate a JSON map file from the binary map and thus get rid of a manual step.

In the latest PR there is an extra room ID = 76 that is overlapped on the entrance of lupine hunting grounds.

Hi! Is there any interest in a realtime crowd mapping system? I was reading about how database replication works and I figured hey that crowdmap could be doing this! Here's how I think it works:

1. The mapping efforts generate a transaction log of what changes need to change in the map db
2. This log goes in a central (append only?) database or log storage
3. A client retrieves this log and plays it to generate a local map db
4. For updating, the same client requests logs newer than what they already have; playing through it updates their db

• The central log database occasionally does a full scan and drops older entries that are no longer necessary

It's a very rough idea! Thoughts, anyone?

Aster has been opened up and there are a lot of new rooms to map.

Room 4497 and 4498 have the "infinite weight" checkbox ticked in Hashan, which basically prevents pathing through those exits. Not sure if this is intentional or not?

One of the default room marks, bank, takes one to the Ashtan bank, overriding user set room marks (reported by Kogan via message)

When creating the map explorer, I noticed we have some areas without names. Maybe we should clean them up by either giving them a useful name or removing them.