CMT, Tagspace, tagslots, script space, and version numbers.

[n00b1n8R]

Pretty old news tbh.

As long as they give a way to unlock it (perhaps release an app to change the variable when the time comes too?) I'll be happy.

[Reaper Man]

So, uh, what happened to the installer app suggestion that jcap and I came up with?

[Masterz1337]

Nothing happened, we're still going to do that as planned. From what I understood of it, you guys wanted us to do an exe of the mod, which would install the maps, 1.08, and MTV.

[Reaper Man]

Yeah, that's spot-on.

[ramis92]

I see 1 potential problem with using OS and 1.08 with SPv2. I don't know how probable this may be, but what if there is another security exploit or something and another update is released?

[FRain]

Re-package the installer and re-release?

[Kornman00]

As long as I' upgrading the maximum allowed tag memory I'll increase the max allowed tag instances too.

This kind of change would be made as an update to the OS code so people that develop OS extensions don't cause future conflicts. While I doubt there will ever be an update again, it will be easy enough to update the OS source (if it even needs to be) to reference any different addresses.

[Syuusuke]

When you say you locked dev...are you saying you disabled all the cheats and other "unholy" commands that could affect gameplay or did you really lock developer mode?

[jcap]

Basically the devmode scenario is this:

There's some things that can "break" the campaign, such as getting in a vehicle after you cheat_bump_possessioned'd a character. You will not be able to get back out, and if the game saves...

So it's kind of a measure to check that people won't break it and then bitch. To be honest, I think it's completely stupid, since by cheating in the first place you are taking the risk yourself. Furthermore, you can just use a stupid trainer that modifies the memory, or you can disable the script through console and cheat anyway.

Dumbass move.

[BobtheGreatII]

Basically the devmode scenario is this:

There's some things that can "break" the campaign, such as getting in a vehicle after you cheat_bump_possessioned'd a character. You will not be able to get back out, and if the game saves...

So it's kind of a measure to check that people won't break it and then bitch. To be honest, I think it's completely stupid, since by cheating in the first place you are taking the risk yourself. Furthermore, you can just use a stupid trainer that modifies the memory, or you can disable the script through console and cheat anyway.

Dumbass move.

Yeah... I kind of agree... why restrict it? I think there is more complaining taking it away than there would be if you had left it. Like he said, if they break it, it's their fault, no one elses. Should know better when they're glitching the game.