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

Byond seems to take incorrect files when set in the map maker. #28085

Closed
WJohn opened this issue Jun 5, 2017 · 8 comments
Closed

Byond seems to take incorrect files when set in the map maker. #28085

WJohn opened this issue Jun 5, 2017 · 8 comments
Labels
Bug Correct Functionality BYOND Issue We are trapped in the belly of this horrible machine Needs Reproducing Nobody will fix your issue unless you do this

Comments

@WJohn
Copy link
Contributor

WJohn commented Jun 5, 2017

If you try to set the sound to /sound/weapons/Laser.ogg, it will automatically be replaced with /sound/vox_fem/laser.ogg.

This doesn't just happen with sound files, icons suffer from this too (and presumably others?) If you try to set, say, an indestructible riveted wall to /icons/turf/mining.dmi and pick the "rock" icon, the sprite will fail because it will automatically re-select to /icons/obj/mining.dmi.

This seems to affect only var editing in the map maker, but I don't know if it extends to anything else.

@WJohn WJohn added Bug Correct Functionality BYOND Issue We are trapped in the belly of this horrible machine labels Jun 5, 2017
@WJohn
Copy link
Contributor Author

WJohn commented Jun 5, 2017

Still happening even after clean compile.

@MrStonedOne
Copy link
Member

@Cyberboss
Copy link
Member

Should this really remain in OUR issue tracker?

@MrStonedOne
Copy link
Member

We have always kept byond bugs open.

Keeping bugs that can't be fixed open lowers dupes because issue search by default does not show closed issues, and most people would assume a closed issue is fixed and it happening again would warrant a new issue anyways.

Like, @Cyberboss, I'm banned from microsoft, reddit, RES, and a few other github repos because I believe firmly that cantfix or wontfix is not a reason to close an issue report.

Do you really think i'd ever let this issue get closed here?

@MrStonedOne MrStonedOne added the Needs Reproducing Nobody will fix your issue unless you do this label Jul 3, 2018
@MrStonedOne
Copy link
Member

Can somebody confirm this issue still exists in 512, no action was done on the byond side, but 512 changed a bunch of things in the map maker.

@SuperNovaa41
Copy link
Contributor

No longer an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Correct Functionality BYOND Issue We are trapped in the belly of this horrible machine Needs Reproducing Nobody will fix your issue unless you do this
Projects
None yet
Development

No branches or pull requests

5 participants
@WJohn @MrStonedOne @Cyberboss @SuperNovaa41 and others