|
Members in Shoutbox
None.
Shoutbox Search
Shoutbox Commands
/w [name] > Whisper
/r > Reply to last whisper /me > Marks as action Shoutbox Information
Moderators may delete any and all shouts at will.
|
Global Shoutbox
Please log in to shout.
[2016-4-19. : 7:27 am] O)FaRTy1billion[MM] -- that might be good, except the problem is having to copy+paste that hundreds of times for every address ![]() [2016-4-19. : 7:25 am] Clokr_ -- That way you don't need to enter everything but you have an unified setting to work with and the data will be clear[2016-4-19. : 7:25 am] Clokr_ -- If you don't want to be redundant you can add flags in the whattodo member which mean: copy data from the last entry which didn't have this flag set[2016-4-19. : 7:24 am] Clokr_ -- I would still consider having just one struct of the type: unsigned int ptr, int whattodo, union{ struct data1 {...}; struct data2 {...}; ... }[2016-4-19. : 7:22 am] O)FaRTy1billion[MM] -- Clokr_Clokr_ shouted: Clarity > redundancy ya, but some of these that I haven't done yet get crazy, like I mentioned with the units.dat ![]() [2016-4-19. : 7:22 am] O)FaRTy1billion[MM] -- Clokr_Clokr_ shouted: ptr[999] ? I could do that, but I'd probably do like [20][2016-4-19. : 7:20 am] O)FaRTy1billion[MM] -- o, except I don't know how to have the ptr one be a variable sized array ;o[2016-4-19. : 7:19 am] O)FaRTy1billion[MM] -- it would be, I was thinking about that since I already have a bunch like it that are in a struct[2016-4-19. : 7:18 am] Neiv -- Having img_consts be a struct { factor, add, ptr } would be clearer though? If you don't mind having each patch there in a separate line ![]() [2016-4-19. : 7:18 am] Clokr_ -- It's still really messy, because you have here the pointers that you just replace, there the pointers where you have to inject assembly, etc[2016-4-19. : 7:17 am] O)FaRTy1billion[MM] -- and yes, less code. I can just do a nested loop instead of a copy of the loop for each array[2016-4-19. : 7:16 am] O)FaRTy1billion[MM] -- eh, I started with more arrays but then was like I don't want 1000 arrays[2016-4-19. : 7:16 am] Neiv -- I would have likely used multiple separate arrays instead of using zeroes to separate lists, but that's going to require more patching code[2016-4-19. : 7:15 am] O)FaRTy1billion[MM] -- I should just dump them in a seperate file so the actual arrays aren't immediately visible.[2016-4-19. : 7:14 am] Neiv -- FaRTy1billionFaRTy1billion shouted: http://pastebin.com/H6Xy3abV Is this bad design? I feel like it probably is, but I can't think of a better/easier way to overwrite lots of pointers with the same data. Ew, that's ugly D: Though I don't really see any clearly better way of doing that![]() [2016-4-19. : 7:14 am] O)FaRTy1billion[MM] -- so it just says flingy has 7 values, so it starts at [0] and replaces all the pointers it finds with the new address for the speed array until it reads a 0, then it starts replacing all the addresses it finds with the new address for the accel array, etc.[2016-4-19. : 7:12 am] O)FaRTy1billion[MM] -- Clokr_Clokr_ shouted: and you got hardcoded how many for speed, how many for accel, etc, oh, do you mean how it knows how long each list is? They're 0-terminated[2016-4-19. : 7:11 am] O)FaRTy1billion[MM] -- ya, those are the pointers to the respective arrays in SC's code that I will replace with pointers to my own, larger arrays[2016-4-19. : 7:09 am] O)FaRTy1billion[MM] -- flingy.dat has 7 values, so there are 7 lists in flingy_r[2016-4-19. : 7:08 am] O)FaRTy1billion[MM] -- so like the array of flingy.dat sprite values, the flingy.dat acceleration values, etc.[2016-4-19. : 7:08 am] O)FaRTy1billion[MM] -- those are the pointers to the flingy.dat value arrays to be replaced with the new pointer to the new array[2016-4-19. : 7:07 am] O)FaRTy1billion[MM] -- 406 pointers that will all be replaced with the same value, which is why I'm doing it how I did ![]() [2016-4-19. : 7:05 am] O)FaRTy1billion[MM] -- also units.dat will be crazy, because it has like 1400 or so pointers to replace ![]() [2016-4-19. : 7:04 am] O)FaRTy1billion[MM] -- a few are known values, and they're in a format sort of like that[2016-4-19. : 7:04 am] O)FaRTy1billion[MM] -- because I'm replacing them with unknown values, and there are tons of offsets that need the same values[2016-4-19. : 7:03 am] Clokr_ -- Why not just a big list of type: offset, nbytestoreplace, byte1, byte2, byte3, ...[2016-4-19. : 7:01 am] O)FaRTy1billion[MM] -- also what's going on is just massive lists of pointers to overwrite ![]() [2016-4-19. : 7:00 am] O)FaRTy1billion[MM] -- I liked it better as like 0x0049906B+2, but it got mad at me for that[2016-4-19. : 6:57 am] O)FaRTy1billion[MM] -- I did it because it was easier, but then the compiler yelled at me for having a number followed immediately by a + saying invalid suffix or something[2016-4-19. : 6:57 am] Clokr_ -- Not really sure what is going on, but let me tell you: those commas without white spaces look awful...[2016-4-19. : 6:46 am] O)FaRTy1billion[MM] -- http://pastebin.com/H6Xy3abV Is this bad design? I feel like it probably is, but I can't think of a better/easier way to overwrite lots of pointers with the same data. ![]() [2016-4-19. : 6:42 am] O)FaRTy1billion[MM] -- I should put all the arrays in a different file or something. This is getting kind of crazy ![]() [2016-4-19. : 6:41 am] O)FaRTy1billion[MM] -- I didn't know what to call the increase in flingy ID size[2016-4-19. : 6:41 am] O)FaRTy1billion[MM] -- // Currently no configuration; hardcoded ! dats[FLINGY_DAT].newEntries = 219; dats[FLINGY_DAT].doPatch = true; doThingyExpand = true;[2016-4-19. : 6:40 am] O)FaRTy1billion[MM] -- It compiles and runs, but I haven't enabled those patches yet[2016-4-19. : 6:40 am] O)FaRTy1billion[MM] -- I did most of sprites and images on Saturday, today was just finishing up a bit of code[2016-4-19. : 6:37 am] O)FaRTy1billion[MM] -- I havent' tested sprites or images at all. Sprites will probably work as well as flingy, images will probably not work. ![]() [2016-4-19. : 6:35 am] O)FaRTy1billion[MM] -- 12:30, and I just finished adding some entries to my images.dat patching arrays, and the code to apply the patches ![]() [2016-4-19. : 6:33 am] O)FaRTy1billion[MM] -- cool. Well I didn't get much done, but at least I didn't do nothing ![]() [2016-4-19. : 6:33 am] O)FaRTy1billion[MM] -- oh cool, and other numbers I didn't know appear to just be the line number or whatever to some storm calls[2016-4-19. : 6:28 am] O)FaRTy1billion[MM] -- ya, I'll just do and eax,0 / add eax,(number). Then I don't need to add more arrays/pointers/code ![]() [2016-4-19. : 6:21 am] O)FaRTy1billion[MM] -- I keep trying to make easy way to list where to replace and with what, but all I've ended up with is a ton of really awkward arrays ![]() [2016-4-19. : 6:19 am] O)FaRTy1billion[MM] -- I can fill it with NOP, or I can do and 0 / add new count ![]() [2016-4-19. : 6:12 am] O)FaRTy1billion[MM] -- Making everything available to both seems the better, more stable option[2016-4-19. : 6:08 am] O)FaRTy1billion[MM] -- I've noticed. I think it's usually ternary operators, I read something about that when I had really confusing code like this (but moreso) before |