• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
It already has India unless you mean SWMH (the map mod) in which case it's planned to have some of western India but not the whole thing. Also that's not happening for a fairly long time.

They could have the entire empire of Rajasthan and just leave out the Deccan and Bengal regions. Maybe include like certain parts of the Deccan, but virtually none of the Bengal.

And they can use this explanation.
-----------------
Eastern India or Bengal has nothing to do with this setting with this game. Eastern India's history has been completely inseparable with Southeast Asia as noted with this map:

http://upload.wikimedia.org/wikipedia/commons/2/25/East-Hem_1200ad.jpg

You also have the fact that the portrait design for Indian people don't fit well with the Dark Dravidian people or the More Asiatic looking Bengalis.

Bengali: http://marlandphotos.files.wordpress.com/2011/02/day-58.jpg
Dravidian: http://i1.trekearth.com/photos/7812/img_4176.jpg

And Punjabi: http://sikhcentre.files.wordpress.com/2009/08/1.jpg

Punjabi matches what Paradox has provided as the Indian phenotype. So... we can safely say that only Western India fits in with Crusader Kings given with what we are limited to use.
----
That is a reasonable excuse for altering the scheme Paradox had with India to fit in with what is more correct out of what can be used in historical accuracy.

What we could do to take into account of this change is to add Romani people, since Gypsies began to pour out of India starting in 900 CE, after an Iranian Muslim Shah forced them out of their native Rajasthan.

http://dnaconsultants.com/images/gypsy migrations.jpg
 
Every since the last Beta patch came out, my game crashes anywhere from seconds to minutes in, so I'm assuming whatever what "patched" broke HIP. :(

Hmm. I don't have this problem at all. Try the following:
  • Verify the integrity of your game cache through Steam.
  • Download and reinstall HIP with the EMF 2.04 Beta (simple instructions can be found here), which is fully compatched to the current beta patch (2.2.0.9) and features some other improvements.
  • When you reinstall HIP with the EMF beta, also try deselecting CPR if you had it previously selected (its installer default is 'no'-- deselected). CPR carries with it some baggage on possible points of failure due to all of its DLC dependencies and the fact that the beta patches have heavily screwed with the code related to portrait DLCs. If everything works afterward and you want to try re-enabling CPR, then you can just run the installer again and make sure to select it the second time. To do so, you won't have to go through the EMF Beta installation instructions twice if you just use the installer's 'COPY' method, as that will retain all the source module files in your mod folder and allow you to keep re-running HIP.exe until you get the combination you want.
Let me know how it goes.
 
I would really love to see it in there! You can use or modify it any way you please. I don't even want credit.

I'll make sure Aasmul, elvain, or theKing sees this. Aasmul's jamming out a thesis on a major deadline right now, but it's possible he'll have time to take a look after Thanksgiving. The whole SWMH team is rather bogged down or unavailable right now, unfortunately, so no promises. The EMF/PB teams have been maintaining/updating SWMH since 2.2 came out, but its not our province to make any changes like these: those are decisions for the owners.
 
Do you plan to release a new version of the mod since the 2.2.1 patch is out ?

thats, sort of a dumb question

the question you meant to ask is "when is it likely?"
 
Well, of course I meant: "How much time does it require to release a new version of the mod since the ne CK 2 patch is out?"; so it isn't such a dumb question, is it ?

except you didnt say it, you asked a stupid persons question of "gonna bother?"
 
The new HIP release will be tomorrow, November 19th. Fun fact: it's also my birthday tomorrow, so this release shall be known as the "Ziji's Birthday-Themed Update." It will not feature events about birthdays, but it will fetch a lot fewer bug reports. :p
 
The new HIP release will be tomorrow, November 19th. Fun fact: it's also my birthday tomorrow, so this release shall be known as the "Ziji's Birthday-Themed Update." It will not feature events about birthdays, but it will fetch a lot fewer bug reports. :p
glad to learn about it here.
 
glad to learn about it here.

There was a thread that I posted yesterday about it in our dev forum, you damn rogue. :D

EDIT: Or were you referring to the fact that it's my birthday today? Hehe.
 
Excellent and thanks for the reply. Dumbass question number 2 (spot the HIP noob), are savegames compatible or do we have start a new game after update?

This, I cannot definitively answer. We really can't guarantee any save-compatibility across the beta patches or across normal patches (so, any vanilla patches). We will never be able to know whether Paradox broke save-compatibility in some way when they're not only changing the moddable part of the game but also the EXE. You can try your old savegames. It's quite likely they'll work, although there's a reasonable possibility some stuff might not work correctly in unexpected ways somewhere down the line. That said, nothing about our mods is save-incompatible since the last release as long as you use the same modules for the same savegame. In the case of EMF, this is reflected in the fact that the major version number (2) hasn't changed for this release (we'll be releasing 2.04). PB also uses the same versioning system now (releasing 4.04). We always increment the major version number when save-compatibility is broken with the previous version.

TL;DR: Beware save-compatibility whenever Paradox releases a patch. EMF and PB use a special versioning system to show you when they're definitely save-incompatible with the previous release, and today's release will not feature any such incompatibilities due to our changes. When a new vanilla patch isn't in question, those version numbers can always be trusted.
 
There was a thread that I posted yesterday about it in our dev forum, you damn rogue. :D

yeah, after it was announced here with an ETA.