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

Interiorid & VirtualWorld #13

Closed
PatchwerkQWER opened this issue Sep 12, 2015 · 4 comments
Closed

Interiorid & VirtualWorld #13

PatchwerkQWER opened this issue Sep 12, 2015 · 4 comments
Milestone

Comments

@PatchwerkQWER
Copy link

Hi,

I think this will be really useful. Should you add VirtualWorld and Interiorid parameter in export? But let it as string. Because I love readability. So I have maps with interoir in define for easy way to change it like #define BANK_INT 30 or #define EVENT_VW 11.

Cheers

@Pottus
Copy link
Owner

Pottus commented Sep 14, 2015

You could certainly modify it afterwards fairly easily. My best thought would be to create a more in depth export dialog for all the settings but don't think I would really get around to doing it but Crayder might. It's probably only a couple hours work I would think.

@Crayder
Copy link
Collaborator

Crayder commented Sep 14, 2015

Modifying the output afterwards is extremely simple. If I were to do this I don't think I would use defines, I'd like to keep it relatively simple for the newbies and such. This is a bit extensive though, not that I won't consider it. Instead of a "more in depth export dialog" I'd rather just add one more dialog asking whether to use the player's current virtual world and interior. That way it's more easily understood.

@Pottus
Copy link
Owner

Pottus commented Sep 14, 2015

Well you could update the map format to have a map data table to extend the data stored by the map. This is the route I would take if you look at tsmain.pwn and check out the sqlite_UpdateDB() you will see it is very easy to update the map format with just a couple queries.

@Crayder Crayder added this to the Do before 1.9 milestone Oct 4, 2015
@Crayder
Copy link
Collaborator

Crayder commented Aug 27, 2016

Done on the inprogress branch, untested

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

3 participants