Your developers encrypted the stored procedures.
CREATE PROCEDURE prc1 WITH ENCRYTION
Stored procedure code is stored in the table syscomments and is viewable by anyone. Encrypting the procedure removes this ability. Plus you can't script it.
Unless they have a very good reason, they should not be doing this. It does not matter since there is a decrypter available as freeware on the internet. Google dSQLSRVD.
I worked on a 3rd party application that encrypted the procs and if we had a database error we just decrypted the proc, found the bad code and sort of suggested to the 3rd party where they might need to make a fix.
Norman