ENT Gaming

@HazarDous There is a series of maps that are well protected and any bot (including ent ones) can't host it. It would be fixed by recompiling bot with latest stormlib library. That would be wonderful but maybe hard to do, so could you add a way to add a map configuration file for a map we upload and use that in bot? The Map in particular is eden rpg 2.6a fix2 eng.w3x, load code 9d5f0. From now on all versions will be protected such that bot can't read the mpq file, but if I could have a way of linking the config file myself, it would be able to use those values without the need of reading the map mpq.

Note that map works if you manually host with warcraft so its not a map problem.

Maps might use the S/SSProtect as well. Korean tend to use this protection, which makes them not hostable outside Korean Platforms. But it's easily fixable.

@null the map can be hosted normally without a bot in English warcraft and we already got a bot hosting it with the right config file so it's not a problem of Korean platform

I agree, there'are dozens of maps I can't host because the bot is outdated.

juvian wrote:@null the map can be hosted normally without a bot in English warcraft and we already got a bot hosting it with the right config file so it's not a problem of Korean platform

The map has initial MPQ corruption in the HEX then. Updated bots can cope with this depending on the config, but ENT can't. And if ENT doesn't want to update, you will have to learn HEX and fix the initial corruption in the MPQ so ENT can read it.

@null Yeah it does, but even if I know hot to fix it, developer wants it to stay that way so won't go against that. My easier solution proposed was just having a way to edit the map config you guys generate automatically when uploading map (the file bot uses when you host with !load code) instead of !map. I can get a working config file myself and bot could host it fine that way. It's just adding the possibility to edit a file you already use and make

Any update?

juvian wrote:@null Yeah it does, but even if I know hot to fix it, developer wants it to stay that way so won't go against that. My easier solution proposed was just having a way to edit the map config you guys generate automatically when uploading map (the file bot uses when you host with !load code) instead of !map. I can get a working config file myself and bot could host it fine that way. It's just adding the possibility to edit a file you already use and make

Provide such bot config file and we will look into it.

Given the majority of maps works just fine, we will not recompile the ghost code.

@aRt)Y Thanks for replying. I think this was the correct config: https://drive.google.com/file/d/0B-9phZ ... sp=sharing

Map has been updated like 10 times since then though, unless there is a way to change map config from client, if you manually make an exception for this map and edit it yourself there wouldn't be much use.

Hopefully the bot will be updated so we can host new maps.

@NVS @h3rmit @hellralser

Could use your input on this, if you are knowledgeable in this matter, thanks.

Suggestion: Update bot/stormlib to allow ENT to host some "well-protected" maps.

* Is stormlib the issue?
* Easy to fix?
* Many maps affected?

Depends if it's easy or not

Do you use the Public Ghost ++ or the source code?

Stormlib is definitely an issue and a suggestion is to use the stormlib that Ladik uses.
Using Warcraft's III storm.dll is also one way, though, that is much harder.

Regarding to how many maps are affected;
pretty much almost every map outside the english WC3 platform (korea, china or even russia. They have tons of maps that is unhostable on ENT)

The OP has a map from Korea I think (Eden RPG?) - that map is unhostable on ENT. But I believe the mapmaker was kind enough to provide us (here on ENT) with a non-protected map so we could host it.

Using stormlib sounds like an easy solution, not sure how ghost++ checks map integrity tho

Upgrading stormlib is the way to go. I can confirm that v9.22 of Ladik's StormLib can open the map in question (whereas v9.21 failed for me).

As far as changes needed for the bot itself, this commit on Grief's version can probably shed some light. I have no clue if the patch will apply to ENT's version.

Using Ladik's StormLib v9.21:


Using Ladik's StormLib v9.22:

While you guys are at it, incorporate Japi(http://japi.sourceforge.net/) into ent would make tons of maps hostable since Ent uses java to host.