What happends when a company like Liandri finds a forbidden king's tomb with tresaures?Well sell the tresaures and convert the tomb to a Unreal Tournament Arena, but for some reasonsome workers disappear or got kill by something inside the pyramid during exploration and set up.

But Liandri didn't care about it and with this extra mystery will make this Forbidden Tomb a nice play to fight and die.

WARNING:This map is dangerous for any contender that doesn't know about them, BE CAREFUL.

And by using generic names, soon, another dude will do a map named like that. What's the purpose for using generic names which anyone can use ? Mismatches. Who cares anyway ? They are not stock files.AS another info, AlternatePath in a DM is USELESS. If you are using Editor to do the Bot Pathing I'm not interested - You need to learn this chapter. Editor is far from good at doing paths.

A sample of things which I don't load in my repositories.Each time when Bot will go for UDamage it will probably die - Where is the challenge then ? Happening of course if will not be skating between 2 nodes due to over-loaded spot for no reason.

Do you know how the problem of colliding names was solved decades ago?Namespaces

While unlike modern stuff you do not have much of a "namespace" system in UEngine itself (other than the package names themselves, which should not be relied upon anyway due to IsA amongst other things), since ancient times (pun intended) people used a notation to define a namespace in how they name things in the first place.

It's very simple: choose a notation in how to name things, and use it consistently.Then use a different notation to split up what is the actual name from the namespace.

Mappers and modders in UT do this for years, by simply adding their name or brand or some other thing as a prefix to their stuff:DM-FoT-ChronoShift (FoT is the namespace and ChronoShift is the actual name of the map)XC_Engine (XC = namespace, Engine = actual intended package name)...

The general notation used across even different platforms and languages is using either camelCase or PascalCase, and then use underscores or hyphens to separate the names, as shown above.

In your case, you can keep the name ForbiddenTomb, but the actual map could be called instead:DM-DiegoHoF-ForbiddenTomb (for example)

DiegoHoF can become the namespace for your stuff.In other things the first names used as namespace is also called the "vendor".

None of those names are trademarked so no one can ask you to change it, all you should do is to simply make sure they never collide with existing stuff, not necessarily change the name altogether.After all, there aren't many words in English to actually express what you're trying to pass across, compared to other languages at least, so it's easy to collide, and no one should ostracize you for it.

Sorry if i offend you but, your map is not complete in my opinion. Like paper said, there's too much open space... nowhere to take cover when needed. Pure crap, again sorry but maybe a little more practice mapping before posting/releasing them to the public. There's already enough crap out there, you need to get the community interested.

nogardilaref wrote:Do you know how the problem of colliding names was solved decades ago?Namespaces

While unlike modern stuff you do not have much of a "namespace" system in UEngine itself (other than the package names themselves, which should not be relied upon anyway due to IsA amongst other things), since ancient times (pun intended) people used a notation to define a namespace in how they name things in the first place.

It's very simple: choose a notation in how to name things, and use it consistently.Then use a different notation to split up what is the actual name from the namespace.

Mappers and modders in UT do this for years, by simply adding their name or brand or some other thing as a prefix to their stuff:DM-FoT-ChronoShift (FoT is the namespace and ChronoShift is the actual name of the map)XC_Engine (XC = namespace, Engine = actual intended package name)...

The general notation used across even different platforms and languages is using either camelCase or PascalCase, and then use underscores or hyphens to separate the names, as shown above.

In your case, you can keep the name ForbiddenTomb, but the actual map could be called instead:DM-DiegoHoF-ForbiddenTomb (for example)

DiegoHoF can become the namespace for your stuff.In other things the first names used as namespace is also called the "vendor".

None of those names are trademarked so no one can ask you to change it, all you should do is to simply make sure they never collide with existing stuff, not necessarily change the name altogether.After all, there aren't many words in English to actually express what you're trying to pass across, compared to other languages at least, so it's easy to collide, and no one should ostracize you for it.

I'm not good with names so i don't have a maespace yet and with my name is kinda hard(maybe DIE or DEG), for now i want to get experience with mapping and the feedback is good to have some kind of pattern to follow when making maps.

Hank wrote:Sorry if i offend you but, your map is not complete in my opinion. Like paper said, there's too much open space... nowhere to take cover when needed. Pure crap, again sorry but maybe a little more practice mapping before posting/releasing them to the public. There's already enough crap out there, you need to get the community interested.

Well, this is the only way to know if you are doing good or bad, making others see for our mistakes, maybe later i can make a FIX or ][ version with better judgement and planning