Expansion Disable Not Working?
Is the setting in the Variable table, "Expansions" not working? I've set this to 0 and still can create all classes. I also tried setting, "World:ExpansionSettings" inside the rule_values to 0 and still doesn't restrict Vah Shir, Froglok, etc.. I locked out the non classic zones, just not sure why its not locking out those.
Another quick question is, why is the setting to disable tutorial button still allowing people to go to tutorial? Thanks, Silentrath EDIT: I am all up to date with the latest changes. |
Do you have this rule disabled?:
Code:
World:UseClientBasedExpansionSettings |
Got it working! Had it set to on another ruleset! My bad, thank you!
|
Ah okay, I don't know if what I said helped or not if it was on another ruleset, but you're welcome? Haha.
|
Quote:
|
Haha, okay. You're welcome, glad you got it working.
|
Quote:
|
I wonder how to check it also, I have installed a fresh database etc etc, and that value is not in my variables or rule_values. Now I cannot lock expansions out. Does it need to be added manually?
EDIT : Ok I added 1 World:UseClientBasedExpansionSettings false manually and it worked other than the gnome pal/sk and Halfling rng/pal those you can still make even if you set expansion setting to 0. Any idea on those? |
Quote:
|
Titanium Client is the one I'm using.
|
Yeah that is probably why. Try with UF and just see what happens.
|
Generic howto:
Assuming you are using ruleset 1 (default). Code:
SELECT * from rule_values WHERE ruleset_id = 1 AND (rule_name = "World:ExpansionSettings" OR rule_name = "World:UseClientBasedExpansionSettings"); World:ExpansionSettings's rule_value should be set to your highest expansion, with a number like: 1=Classic, 2=Kunark, 3=Velious, 4=Luclin, 5=PoP, etc. World:UseClientBasedExpansionSettings rule_value should be set to false. If you're using a freshly copied PEQ database, this record will likely NOT exist. If the UseClientBasedExpansionSettings rule does not exist, run this: Code:
INSERT INTO rule_values (ruleset_id, rule_name, `rule_value`) VALUES (1, "World:UseClientBasedExpansionSettings", "false"); Code:
UPDATE rule_values SET rule_value=2 WHERE ruleset_id=1 AND rule_name="World:ExpansionSettings" LIMIT 1; As far as the non-classic class combos: Unsure that has been addressed but a ruleset could be created for this specific option to be toggled, if the client does select a bad combination and tries to create, it could reject at that point. Unsure that's in yet though. |
Weird when I set it to 1 for clientbasedexpansionsettings, that's kunark for me, I can make an iksar. But setting it to 0 is classic. Eitherway theres still gnome pal/sk and hlf rng/pal. Its ok though, just not 100% classic, which I don't think will matter that much, unless it would be an easy fix.
I would make a ruleset but I'm still not proficient in how to set it up. Entering in the table is np, but maken sure it can talk to the code is another story for me lol. I am not good with c++ |
Quote:
If you want to change race/class combos then edit the table char_create_combinations and change the required expansions for those combinations. |
I could be wrong but I am fairly sure that Titanium clients can make certain combinations no matter what the setting in char_create_combinations
|
All times are GMT -4. The time now is 04:11 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.