You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 3, 2022. It is now read-only.
So how we really should go about this is to have Map and MapVariant content types.
Maps are the actual models and navgrids etc. a MapVariant belongs to a map and specifies things like spawn positions, objects on the map, etc.
This allows us to have multiple different MapVariants for the same Map, so if you want a variant where every player spawns on the center of the map and the edges are full of aggressive dragons for example, you can do that.
I see map variants as a replacement for Riot's .mob file, and in terms of implementation it should be used over the current hardcoded values we have. It could be it's own issue to implement map variants in the first place if that's what you suggest.
We should regardless definitely extract the info from the mob file like you said.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Turret positions and level props missing.
add that from MapObjects file, turret positions also should be there in some cases.
The text was updated successfully, but these errors were encountered: