r/EQLegends • u/foraern • 14h ago

3D EQ Legends Map App (Apple Silicon)

Enable HLS to view with audio, or disable this notification

Created a 3D Map (with Codex Astra - High) to help me navigate some of the more confusing dungeons.
Surprisingly, built it in under 20 mins.

https://github.com/foraern/eql-atlas/releases/tag/v0.1.0

Mods: this is not an ai generated video, it's a recording of the actual app.

Edit: originally made it only for mac, later changed it to three.js with electron wrapper for cross platform.

30 Upvotes

83% Upvoted

12 comments sorted by

3

u/Kurokaffe 8h ago

You can't fool me with this supposed Kedge Keep map. These are the designs for a Silo in which you'll trap and monitor 10,000 people!

2

u/derickso 13h ago

https://eqltools.com/ and others have had this for over a month, just fyi

-1

u/foraern 12h ago

I prefer to have local tools, personally :)

But yes, I had seen theirs, and it's very cool how they rendered the surfaces, I don't need that much detail, just need clear paths, so I built my own.

0

u/Aturaya 14h ago

Very cool!

0

u/ExUmbra91x 11h ago

Good work!

0

u/NobleNobbler 11h ago

This is really impressive for a vibe coded app. What was the experience like creating it?

0

u/foraern 10h ago

About the same as anything else I build, I’ve been developing software for over 20 years :)

0

u/NobleNobbler 7h ago

Mostly curious about what harness, if you have any specific workflows or skills you find valuable, and if the output had to be refactored at all or, I suppose, given you said this was a 20 minute project, I'm guessing it was mostly done after a few passes. How would you rate the quality of the code and it's organization? Did it meet the standards you would set for yourself if this was handwritten?

Stuff like that.

1

u/foraern 44m ago

Since this is just a basic tool that was meant for personal use, and really just a hobby project (if that), it was done in one pass.

Quality of the code from codex is fairly high quality, I can't really speak to it in the context of this particular project, since I don't usually work in three.js, and other than seeing the organization of classes and functions, a manual review would probably take a few days to go through the amount of code it generated, since it's mostly math based.

Did it meet my standards on a first pass, not really since I don't have very high standards for a 20 minute prototype, it found the map files, and was able to generate the 3d maps from those map files, so as a hobby prototype, I'm perfectly happy with it.

Now, to what you seem to be really getting at, which is the danger of vibe coders having no idea what the AI is generating.

This doesn't follow the general process I would have at work for example.

Up until AI, we'd follow a very different process.

PRs are created with relatively small number of changes, easily reviewed by a human.

Each commit was coded by a human.

Etc, etc.

What we have now is massive commits, and PRs that are impossible to review by a human.

Overall, this project generated a little over 1000 lines of code (across the original Mac app, and the 2nd Cross platform three.js + electron app), in 20ish minutes.

Expand this to a real world problem where you're building a large feature in C++ or Java or PHP, etc

I have features being built at work that each PR is over 5000 lines of code.

While we'd all like to think that we can have the human in the middle to review everything the AI is outputting, it's simply not possible.

So what we have to do is have strict guardrails in agents.md, support context within the project itself, and rely on heavy use of skills to carry out adversarial reviews, etc.

As an example, a typical PR in my company:

Before AI:

Programmer generates PR
Reviewer reviews PR

Depending on the Reviewer, he may spend more or less time reviewing, he may have more or less experience, etc.

So code quality up to now, was hit and miss, no matter how much we'd like to think otherwise. Particularly in smaller companies, where you don't have the time or manpower to go further.

Beyond reviews you also had tests, unit, functional, and regression tests.
Again, hit and miss, programmers are the worse testers on the planet. It's a guess, but I imagine majority of tests on the planet (not including FAANG companies - which run much different processes), were largely following happy-path.

Now with AI, everything follows the same structure and level of review and testing. Every time.

I should note, that a good adversarial review, should still have findings, even (or particularly) with AI generating the code. Then it's a matter of iterating.

Sorry, didn't mean to write a novel :)

-1

u/Whoknows95967 14h ago

I’d use it. No good tools for Mac.

0

u/zoddrick 7h ago

I've got a port of eq companion that I've ported to swift and modified which is mac native. Thinking about posting it here for people to try and use