- Joined
- Mar 25, 2015
- Posts
- 10,512
- Reaction
- 13,536
- Points
- 3,748
< ispoiler ko sana, baka hindi mabigyan ng hustisya yung english ko, or .... wag nalang, para lahat masaya. > 
ps. kung irerepost niyo to in any social media, kindly credit niyo naman sa akin, at sa PHC. sayang english ko. haha
Kindly Go to https://phcorner.net/threads/762861/ for your Cabal Files.
Step by Step ..
Join the 3 parts of Client New Age in one folder and Extract the Client.
The Enc Tools folder contains the "xor.xml" which contains the xors of the Client files.
Replace in your enc tools so you can unzip / encode the enc's or dec's.
CentOS Files are compatible with either CentOS 5.8 or 5.9, 6.3 ~ 6.9.
After replacing the centOS files with the files in the CentOS files New Age V8.0 folder, go to the following folders:
Cabal and Cabal / Templates
1 - Cabal Pasta:
Search for: Your Password Here
E Modify the following INIS with the SQL SA password:
AuthDBAgent
CashDBAgent
DBAgent
DBAgent_01
EventDBAgent
GlobalDBAgent
PCBangDBAgent
The other entries with Centos IP (if it is via hamachi his ip if it is NO-IP in the same way)
Search for: Your IP Here
Only WorldSvr containing 1 ip to modify
All other INISs with the name World_01_XX Remaining contain 3 IPS each.
2 - CabaL Folder / Templates:
Search for: Your Password Here
E Modify the following INIS with the SQL SA password:
AuthDBAgent
CashDBAgent
DBAgent_01
EventDBAgent
GlobalDBAgent
PCBangDBAgent
Modify OBDC.ini with your SQL IP
The other entries with Centos IP (if it is via hamachi his ip if it is NO-IP in the same way)
Search for: Your IP Here
All other INISs with the name World_01_XX Remaining contain 3 IPS each.
After replacing the file WorldSvr.bin, click right side on it and go to properties and leave as in print worldsvrbin.png
After service cabal Config and choose your settings like number of channels and rates
After that service cabal Restart and ready configured CentOS part.
For your already created char's have access to the new maps Perform the following Query on the DBs:
update account.dbo.cabal_newchardata_table set WarpBField = 2097151
update account.dbo.cabal_newchardata_table set MapsBField = 2097151
update server01.dbo.cabal_character_table set WarpBField = 2097151
update server01.dbo.cabal_character_table set MapsBField = 2097151
Run this Trigger on DB Server01:
New Chars Start With All Map Codes
So every time you edit your char it won't lose either
access to maps.
CREATE TRIGGER [Maps] ON [dbo]. [Cabal_character_table]
FOR UPDATE AS begin
update Cabal_character_table set WarpBField = 2097151, MapsBField = 2097151
where Login = 0
end
Paste and Press F5
To Make Brazuka Work Like an Event NPC or T-Point
NOTE: Do this so that it does not generate bugs and do some service from stopped centos.
Go to DB EventData
Tables> dbo.cabal_ems_event_table> edit top 200 rows> go to npcIndex column and change all rows with ids 10 to 49
After changing go to dbo.cabal_ems_event_npcscript_table> edit top 200 rows> go to npcIndex column and change all rows with ids 10 to 49
If there is no id 10 leave it like this.
And then it's ready, and have fun = D
SQL QUERY For manual execute
- // CREATE A NEW ACCOUNT
USE [ACCOUNT] exec dbo.cabal_tool_registerAccount 'login', 'password'
or..
USE [ACCOUNT] exec dbo.cabal_tool_registerAccount 'login', 'password', 'your @ email', 'NOPE', 'NOPE'
- // Add GM IP
USE [ACCOUNT] exec cabal_addgmip 'IP'
NEXT ...
The client has been well-tuned so that there are no more closures, I have come to various ways and solutions to
end the closures, but still close what should I do?
I did the test on 4 machines, 2 with W7 and the other 2 with W10
In all that the closures continued I did the same procedure and resolved and had no
more problems or headaches with closures.
Especially with the W10 it still suffers from several upgrades and some end up with Cabal compatibility.
Follow these steps that should solve:
1 - Make sure your PC or notebook has all updated drivers (this is essential)
2 - Always delete the cabalmain.rtp file if it appears on the client after closing.
(It's a file that contains error logs than because it closed the cabal, but it's not always good to keep it, and the cabal won't reopen. It doesn't allow and as if it were a cabal application cache. Always delete -O.).
3 - Go to CabalMain properties. in the compatibility tab put as in print CabalMain.png that came with these files. put in w7 compatibility and always run as administrator.
I hope this resolves. If you have questions just look for me.
-/taong-bato.
ps. sorry sa mga nagbabasa, alam kong na nosebleed kayo . hahaha.
ps. kung irerepost niyo to in any social media, kindly credit niyo naman sa akin, at sa PHC. sayang english ko. haha
Kindly Go to https://phcorner.net/threads/762861/ for your Cabal Files.
Step by Step ..
Join the 3 parts of Client New Age in one folder and Extract the Client.
The Enc Tools folder contains the "xor.xml" which contains the xors of the Client files.
Replace in your enc tools so you can unzip / encode the enc's or dec's.
CentOS Files are compatible with either CentOS 5.8 or 5.9, 6.3 ~ 6.9.
After replacing the centOS files with the files in the CentOS files New Age V8.0 folder, go to the following folders:
Cabal and Cabal / Templates
1 - Cabal Pasta:
Search for: Your Password Here
E Modify the following INIS with the SQL SA password:
AuthDBAgent
CashDBAgent
DBAgent
DBAgent_01
EventDBAgent
GlobalDBAgent
PCBangDBAgent
The other entries with Centos IP (if it is via hamachi his ip if it is NO-IP in the same way)
Search for: Your IP Here
Only WorldSvr containing 1 ip to modify
All other INISs with the name World_01_XX Remaining contain 3 IPS each.
2 - CabaL Folder / Templates:
Search for: Your Password Here
E Modify the following INIS with the SQL SA password:
AuthDBAgent
CashDBAgent
DBAgent_01
EventDBAgent
GlobalDBAgent
PCBangDBAgent
Modify OBDC.ini with your SQL IP
The other entries with Centos IP (if it is via hamachi his ip if it is NO-IP in the same way)
Search for: Your IP Here
All other INISs with the name World_01_XX Remaining contain 3 IPS each.
After replacing the file WorldSvr.bin, click right side on it and go to properties and leave as in print worldsvrbin.png
After service cabal Config and choose your settings like number of channels and rates
After that service cabal Restart and ready configured CentOS part.
For your already created char's have access to the new maps Perform the following Query on the DBs:
update account.dbo.cabal_newchardata_table set WarpBField = 2097151
update account.dbo.cabal_newchardata_table set MapsBField = 2097151
update server01.dbo.cabal_character_table set WarpBField = 2097151
update server01.dbo.cabal_character_table set MapsBField = 2097151
Run this Trigger on DB Server01:
New Chars Start With All Map Codes
So every time you edit your char it won't lose either
access to maps.
CREATE TRIGGER [Maps] ON [dbo]. [Cabal_character_table]
FOR UPDATE AS begin
update Cabal_character_table set WarpBField = 2097151, MapsBField = 2097151
where Login = 0
end
Paste and Press F5
To Make Brazuka Work Like an Event NPC or T-Point
NOTE: Do this so that it does not generate bugs and do some service from stopped centos.
Go to DB EventData
Tables> dbo.cabal_ems_event_table> edit top 200 rows> go to npcIndex column and change all rows with ids 10 to 49
After changing go to dbo.cabal_ems_event_npcscript_table> edit top 200 rows> go to npcIndex column and change all rows with ids 10 to 49
If there is no id 10 leave it like this.
And then it's ready, and have fun = D
SQL QUERY For manual execute
- // CREATE A NEW ACCOUNT
USE [ACCOUNT] exec dbo.cabal_tool_registerAccount 'login', 'password'
or..
USE [ACCOUNT] exec dbo.cabal_tool_registerAccount 'login', 'password', 'your @ email', 'NOPE', 'NOPE'
- // Add GM IP
USE [ACCOUNT] exec cabal_addgmip 'IP'
NEXT ...
The client has been well-tuned so that there are no more closures, I have come to various ways and solutions to
end the closures, but still close what should I do?
I did the test on 4 machines, 2 with W7 and the other 2 with W10
In all that the closures continued I did the same procedure and resolved and had no
more problems or headaches with closures.
Especially with the W10 it still suffers from several upgrades and some end up with Cabal compatibility.
Follow these steps that should solve:
1 - Make sure your PC or notebook has all updated drivers (this is essential)
2 - Always delete the cabalmain.rtp file if it appears on the client after closing.
(It's a file that contains error logs than because it closed the cabal, but it's not always good to keep it, and the cabal won't reopen. It doesn't allow and as if it were a cabal application cache. Always delete -O.).
3 - Go to CabalMain properties. in the compatibility tab put as in print CabalMain.png that came with these files. put in w7 compatibility and always run as administrator.
I hope this resolves. If you have questions just look for me.
-/taong-bato.
ps. sorry sa mga nagbabasa, alam kong na nosebleed kayo . hahaha.
Last edited: