|
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-16. : 4:50 pm] O)FaRTy1billion[MM] -- Though the difference I guess is that it is not open source[2016-4-16. : 4:50 pm] O)FaRTy1billion[MM] -- Clokr_Clokr_ shouted: Things are very different if your editor containes a direct translation of the starcraft engine routines I suppose I'm pretty sure SCMDraft contains stuff directly ripped from SC/SE[2016-4-16. : 3:23 pm] Moose -- Clokr_Clokr_ shouted: Mini Moose 2707 I'm powerless in bash moose, what have I become D: a windows user?[2016-4-16. : 2:38 pm] Clokr_ -- Mini Moose 2707Mini Moose 2707 shouted: I'm powerless in bash moose, what have I become D:![]() [2016-4-16. : 11:45 am] Clokr_ -- Emulators for example are kind of legal as long as they don't include the bios (propietary code).[2016-4-16. : 11:39 am] Neiv -- But legal stuff is a mess, especially when different countries have different laws D:[2016-4-16. : 11:38 am] Neiv -- They only appeared to care about the name, not the fact that it's a rts engine that can read their data files?[2016-4-16. : 11:37 am] Neiv -- Also, a blizzard-related case: https://en.wikipedia.org/wiki/Stratagus[2016-4-16. : 11:34 am] Clokr_ -- I have no idea about legal stuff, but yeah it's probably hard to sue someone if they are not using propietary assets/code even it contains similar code which does the same.[2016-4-16. : 11:28 am] Neiv -- If you look at the source for the mpq libraries, they are clearly based on storm/staredit's code ![]() [2016-4-16. : 11:28 am] Neiv -- Yeah. I guess you can also argue that mpqs are a propietary format, and any libraries that are able to read them are as bad as copying the gameplay code. But blizzard has never cared about mpq editors (I think?)[2016-4-16. : 11:26 am] Clokr_ -- Things are very different if your editor containes a direct translation of the starcraft engine routines I suppose[2016-4-16. : 11:26 am] Clokr_ -- Good thing about editors is they use the game .mpq datafiles, so you are not really distributing any Blizzard propietary stuff.[2016-4-16. : 11:24 am] Neiv -- https://torrentfreak.com/blizzard-nukes-popular-html5-version-of-starcraft-game-151010/[2016-4-16. : 11:23 am] Neiv -- Even if that game's engine was created from scratch and a worse implementation than what our map editors have[2016-4-16. : 11:23 am] Clokr_ -- I knew about the HTML5 C&C which is still up somewhere. Very laggy though.[2016-4-16. : 11:23 am] Neiv -- But when that one "HTML5 starcraft" took their assets and advertised itself as a "recreation", that's something they'll care more about[2016-4-16. : 11:21 am] Neiv -- True, but I don't believe that they consider sprite animating to be that large part of the engine[2016-4-16. : 11:18 am] Clokr_ -- They don't need to know what iscript is, just check the editor has animations and that the source code is hosted for everyone to fork and build another SC engine. Of course at this point I only imagine Blizzard becoming aware of chkdraft if someone actually forks it to build a SC clone ![]() [2016-4-16. : 11:02 am] Neiv -- (Obviously they shouldn't be told about Chkdraft anyways, no reason to get attention from them)[2016-4-16. : 11:01 am] Neiv -- I doubt Blizzard has more than a single developer who knows what iscript is.. I doubt they care if their older games are reverse engineered in a way that doesn't cause them directly to lose sales.[2016-4-16. : 9:53 am] Clokr_ -- Also I'm pretty sure if Blizzard finds out there's an iscript-complete editor source code in github they will try to shut it down...[2016-4-16. : 9:52 am] Clokr_ -- But porting assembly is kind of boring IMO, it's more fun to make it your way[2016-4-16. : 9:51 am] Clokr_ -- I actually had to figure out what some iscript opcodes did, as all the iscript editing programs got them completely wrong[2016-4-16. : 9:50 am] Clokr_ -- Is he directly porting it from SC? Heh, a lot more is known since I wrote the SF:U iscript handler ![]() [2016-4-16. : 9:47 am] jjf28 -- all his: https://github.com/saintofidiocy/Chkdraft/blob/master/Chkdraft/src/Graphics2.cpp ; if he finishes it gives him like 1/5th authorship ![]() [2016-4-16. : 9:29 am] O)FaRTy1billion[MM] -- aw, my glasses broke. Now how am I supposed to see without my contacts? ![]() [2016-4-16. : 9:23 am] O)FaRTy1billion[MM] -- Clokr_Clokr_ shouted: Ah so good, SEN looks a lot younger with Farty back to coding I added stuff to ChkDraft ... I just never finished it ![]() ![]() [2016-4-16. : 9:23 am] O)FaRTy1billion[MM] -- fortunately all the ones that had a hardcoded offset were movzx edx,byte ptre ds:[eax*2 + thing] ![]() [2016-4-16. : 9:22 am] O)FaRTy1billion[MM] -- mov dl,xx / call whatever, and the function is movzx edx,dl / add edx,eax / movzx edx,word ptr ds:[edx*2 + offset] / retn[2016-4-16. : 9:20 am] O)FaRTy1billion[MM] -- NeivNeiv shouted: Buttonset ids would cause a issue, I think? And inconsistencies aren't good, bw has enough hardcoded things anyways D: I had to make one of these functions use mov DL,XX because of hardcoded ones so it's not 1 opcode then retn[2016-4-16. : 9:19 am] O)FaRTy1billion[MM] -- cool, flingy IDs in functions seem to be at least 16-bit too[2016-4-16. : 8:52 am] Clokr_ -- FaRTy1billionFaRTy1billion shouted: I don't know if it's better to just have a huge function with just tons of hardcoded *(int*)(stuff) = stuff, or to just have a bunch of hardcoded arrays of pointers and values Bear in mind a new patch is on the way, so use the option which is easiest to modify![]() [2016-4-16. : 8:51 am] Neiv -- Right, no need to cause additional headache by using the few weird onesO[2016-4-16. : 8:51 am] Clokr_ -- I guess, it is fine though if you can really use as many unit entries as you wish ![]() [2016-4-16. : 8:50 am] Neiv -- Buttonset ids would cause a issue, I think? And inconsistencies aren't good, bw has enough hardcoded things anyways D:[2016-4-16. : 8:49 am] Clokr_ -- You can probably use them just fine. They just won't be detected by triggers. But they might be perfectly fine as subunits, for example.[2016-4-16. : 8:49 am] O)FaRTy1billion[MM] -- I don't know if it's better to just have a huge function with just tons of hardcoded *(int*)(stuff) = stuff, or to just have a bunch of hardcoded arrays of pointers and values ![]() [2016-4-16. : 8:46 am] Neiv -- You could also just name the units 228 to 235-or-so "DO NOT USE", and let bw keep their special meaning ? ![]() [2016-4-16. : 8:45 am] Neiv -- Yea, unit ids are used a lot but they're 2 bytes everywhere I remember[2016-4-16. : 8:44 am] Neiv -- There's 358 units and bullets total, why would 256 flingies be acceptable D: |