Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong spawn container - Center Redwoods #276

Open
Damienlee69 opened this issue Oct 14, 2023 · 6 comments
Open

Wrong spawn container - Center Redwoods #276

Damienlee69 opened this issue Oct 14, 2023 · 6 comments

Comments

@Damienlee69
Copy link

Just spent half the evening troubleshooting why nothing would spawn in the redwoods on the center. Turns out Beacon and the wikis are using the wrong container. Both are using lost islands version, not the islands.
Using redwoods_lostisland_c, should be redwoods_c.

@thommcgrath
Copy link
Owner

This is because both the wiki and Beacon get their data from the data mining. According to the game's files, Lost Island is correct. See https://raw.githubusercontent.com/arkutils/Obelisk/master/data/wiki/TheCenter/npc_spawns.json

@Damienlee69
Copy link
Author

Damienlee69 commented Oct 14, 2023 via email

@thommcgrath
Copy link
Owner

Ah so console and PC are different in this case. Well... shoot. There's really nothing I can do about that. I don't have a mechanism for platform-specific map compatibility.

@Damienlee69
Copy link
Author

Damienlee69 commented Oct 14, 2023 via email

@thommcgrath
Copy link
Owner

No, not really. There are options I could explore long term, but the root issue is that Beacon projects are inherently not platform specific. So how do I know which spawn points are correct for your map? So that would need to change, which is a big deal. Then I'd need to add an extensible compatibility system that can support any number of platforms. Right now, compatibility is just tracked with a single number. So making this work right is a big problem. As far as a note goes, it wouldn't really help anything as working around it is rather difficult. Since ASE is at the end of its life, I'm not going to put any effort into this.

For ASA though, we just don't know yet, and we won't until release. If I need to expand how compatibility is tracked for ASA, so be it. My pricing plan for Beacon is to charge by the game. I'm expanding beyond just Ark games, so it seems more fair to charge a lower price for each game than a larger price for all games. Based on what we know of ASA, it'll be different enough from ASE that it will be a separate game in Beacon, so it will be a separate purchase. But there will be upgrade pricing for anybody that already owns Omni for ASE.

@Damienlee69
Copy link
Author

Damienlee69 commented Oct 15, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants