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.

Sign up for GitHub

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

Jump to bottom

Terrain.emptySquares compatibility #10

Open
Ragora opened this issue Nov 20, 2015 · 1 comment
Open

Terrain.emptySquares compatibility #10

Ragora opened this issue Nov 20, 2015 · 1 comment
Labels
High Priority Task
Milestone
1.0 Release

Comments

@Ragora
Copy link
Member

Ragora commented Nov 20, 2015

It should be checked that the values stored in a terrain block's emptySquares variable in Tribes 2 correspond to the same exact tiles in Torque3D. If they do not, then some engine breaking needs to take place to restore the old tile identification system.
@Ragora Ragora added this to the 1.0 Release milestone Nov 20, 2015
@Ragora
Copy link
Member Author

Ragora commented Nov 22, 2015

The values do not appear to line up exactly, unfortunately. In fact, I'm not sure if Torque3D actually uses the emptySquares value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
High Priority Task
Projects
None yet
Milestone
1.0 Release
Development

No branches or pull requests
1 participant
@Ragora