This is a read only copy without any forum functionality of the old Modcraft forum.
If there is anything that you would like to have removed, message me on Discord via Kaev#5208.
Big thanks to Alastor for making this copy!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Rangorn

Pages: [1] 2 3 ... 20
1
Serverside Modding / Re: Summon gameobject permanent time with spell.
« on: September 04, 2016, 01:48:59 pm »
You should add a SQL query in the spellefffect for adding the gameobject in your sql table

2
"Retro-Porting" / Re: Lets play a game of mix-and-match: Spell.dbc
« on: July 13, 2016, 01:34:10 am »
thanks !

3
"Retro-Porting" / Re: WoD and Legion m2s to 4.3.4
« on: July 02, 2016, 08:15:05 pm »
1) Open the m2 file with 010 Editor (no need to use M2Template)
2) Just look at the first line of 010 Editor

If you have something like MD21....MD20.... (16 bytes), it can't work on Wod, and you have to replace the 16 bytes by this in the hexadecimal part :

4D 44 32 30 10 01 00 00

3) Save and quit

Should work after that

4
Tools / [TOOL] [WoD] WdtSupplies
« on: May 16, 2016, 05:33:01 pm »
WdtSupplies is a program for generating required files for Mapping in WoD.
It generate 4 needed files, but you need a WDT for this program.

REQUIRED
This program need java environnement, be sure java is installed on your computer.

HOW TO USE ?
1) Open "Launch" with notepad or another text editor
2) Replace "Test.wdt" by the name of your wdt, and save
3) Put your wdt file in the folder
4) Launch Launch !

https://mega.nz/#!jAMGAI5Y!_1rXG_-0NL51 ... nOCbcr-7Jo

5
Miscellaneous / Re: [QUESTION] MyDBCeditor issue
« on: May 14, 2016, 03:17:00 pm »
[deleted]

6
Miscellaneous / Re: [Legion] WDB5 format
« on: May 12, 2016, 02:41:10 pm »
[deleted]

7
Miscellaneous / Re: [Legion] WDB5 format
« on: May 12, 2016, 11:26:39 am »
[deleted]

8
Miscellaneous / Re: [Legion] WDB5 format
« on: May 05, 2016, 02:22:06 am »
[deleted]

9
Miscellaneous / Re: [Legion] WDB5 format
« on: May 04, 2016, 06:34:18 pm »
[deleted]

10
Miscellaneous / Re: [Legion] WDB5 format
« on: May 03, 2016, 07:30:54 pm »
Yeah, but i'm talking about the header

11
Random / Re: What tools would help you develop?
« on: May 01, 2016, 01:44:43 am »
Quote from: "stoneharry"
I was wondering what tools or things you would like automated to aid in your development process making content.

Things like going DBC <-> MySQL, doing data processing/transforming scripts, website scripts, and such. I can't really contribute to projects like Neo because I don't know about how 3d graphics and OpenGL works, and don't really want to spend so long learning it at this point in time, but I can automate manual tasks that are time consuming and help speed up development processes.

DBC, and if you can DB2 and DB5, DB2 is exactly like DBC but 7 more column in the header, DB5 is.... more complicated

12
Miscellaneous / Re: [Legion] WDB5 format
« on: April 29, 2016, 01:04:46 am »
[deleted]

13
Miscellaneous / Re: [Legion] WDB5 format
« on: April 28, 2016, 04:37:15 pm »
[deleted]

14
Miscellaneous / Re: [Legion] WDB5 format
« on: April 19, 2016, 08:40:20 pm »
Ok i'm done with WDB5

The furry already made a program for parsing All the files into csv format
https://github.com/Arctium-Emulation/Tools

I will maybe only contribute to the wiki by referencing structure + column name.

15
Miscellaneous / Re: [Legion] WDB5 format
« on: April 18, 2016, 11:54:55 pm »
Quote from: "Simca"
It is uint16; uint40 is an illusion created by record alignment.

When Blizzard writes records to files, the end of the record is aligned to the largest field size used.

In this file in question, the ID field starts at 0x1B into the record and lasts for 2 bytes according to the field structure block ((32 - 0x10) / 8 = 2). This puts the end of the field at 0x1D. However, the record size field in the header says the record is 0x20. The difference is because of the alignment I just mentioned. The largest field size used in the record is 4 bytes. The nearest values divisible by 4 bytes are 0x1C (which the ID field goes past) and 0x20, so the record is padded by 3 bytes to make it properly align at 0x20.

So yes, you can read it with that structure, but it would be better to read it as uint16 and then skip to the end of the record.

Ok i get it, thanks for your explanation :)
I think this could be helpful to write a fake-column with the amount of padding for each DB

Pages: [1] 2 3 ... 20