|
Development Forum |
 |
|  The Mossy Shee
Jesseth
 

|
9/30/2014 | |
in my adventures in making and editing agents, I've come across a problem that's really throwing me off-
I'm working on the wind chime agent listed as 'chime' here and initially it was working just fine,
BUT
when I decompiled it into a folder, replaced the c16 and recompiled it, it no longer shows up as an injectable agent. After some poking around in jagent and other programs I found out that windchime-1.cos (or something to that equivalent) was missing
thinking i could just mend this by removing the agent and replacing it with the original, I did just that, but APPARENTLY the cos file/s are still missing, despite it being the original agent. If I decompile it, they're still not there and it seems as though they were never there.
I'm kind of at my wit's end.
Edit: after some retries i got the original wind chimes to work, but decompiling it gives an error message warning that a script-1 is missing or incorrect.
I don't want to annoy anyone by blathering around like a complete newbie, but I'm honestly confused as to what the matter is with the agent and why it just can't be edited. If anyone has any advice, I'd appreciate it c':
The Mossy Shee & Co |
 Peppery One
Papriko
    
|
10/1/2014 | |
For me it de- and recompiles fine using Monk. I did not test the agent ingame, but the recompiled agent can be decompiled a second time just as fine as the first one.
Also, over here the cosfiles are called "WindChime <C3> script.cos" and "Windchime <DS> script.cos"
Lets play plants! Photosynthesis... Photosynthesis... Photosynthesis... |

Malkin
     Manager

|
10/2/2014 | |
What kind of computer do you have?
I just tried decompiling the Chime agent with Jagent, and I got the error 'IOError parsing chime.agents : (FileNotFoundException)' and it was trying to find the file WindChime <C3> script 1.cos. The further explanation (The filename, directory name, or volume syntax label is incorrect) was provided.
I'm thinking there could be a problem with the PRAY file, and that's why Jagent is having trouble reading it?
My TCR Norns |
 Peppery One
Papriko
    
|
10/2/2014 | |
To provide more information: I used Jagent/Monk too and my OS is Ubuntu 12.04. Even though there apparently only has been used 1 cosfile to compile, it successfully managed to compile (and decompile) them from/into 2 cosfiles.
Lets play plants! Photosynthesis... Photosynthesis... Photosynthesis... |

PuppyPie

|
10/6/2014 | |
Hi! Sorry I took so long to reply! ><
Hmmm, Malkin, what OS was that on? (Windows?)
In any case, I'm almost positive the problem is that on some OS's, certain characters aren't allowed in filenames that are fine on other OS's 
In this agent, the name uses angle brackets instead of the more common parentheses, so when Jagent tries to make, eg, "WindChime <C3> script.cos" it's able to on me and Papriko's linux computers, but not yours and Malkin's (I'm guessing Windows? :>? )
I never thought about this XD, I'm sorries!
Once I know exactly which OS's are having problems with exactly which characters, I'll release a patch to Jagent that will, as they say, "sanitize" the filename according to which OS it's running on ^w^
But, Malkin, that's something we prolly hardly ever think of! This could affect other tools too!
Making agents on one platform that might not be decompilable/functional on another!
(oh biscuits, what if someone somewhere used angle brackets in FILE OOPE! I wonder if such an agent would run on Linux but not Windows 0,0 )
Idk, just a thing to add to troubleshooting lists ^^'
(although actually in this case, they could very well have written it on windows, since the only offending characters are in the agent *names*, which is only used as part of an actual filename by some tools--such as Jagent XD' )
The puppy formerly known as RProgrammer / RP ^,^ |

Malkin
     Manager

|
10/6/2014 | |
Yeah, I'm trying to decompile the Chimes agent on a Windows 8 machine. Thanks for looking into it! 
My TCR Norns |
 The Mossy Shee
Jesseth
 

|
10/6/2014 | |
ah, so it's possibly operating system based! yeah I get the same error when decompiling the wind chime, and interestingly I get the same when trying to decompile the curlshoot agent too, and one thing I noticed they have in common is this:
I can force decompile them with revelation instead of jagent, but they seem to be inherently screwed by doing so (maybe it's just straight up ignoring or deleting the parts that aren't allowed? a mystery) but ONE thing i noticed is that the 'broken' agents have their script file labeled as 'filename'.ps and the working agents do not.
I don't know if that helps at all but it's an interesting conundrum!
also I realised that THIS is specifically the problem I'd been having with agents. The curlshoot is one of the first ones I'd been working on and the wind chime not long after. A few of the others I've worked on I've gotten a friend to test play and they actually work!
Looks like there's one or two agents I might just need another person to work on instead of me.
The Mossy Shee & Co |
|