Help with VERSE Code - States this EXTERNAL is unexpected, but it is needed.

Hello fellow Verse users. I have been coding and all has been good for some days but again I have a problem with just ONE unexpected causing an issue. I have being going over and over it myself and I just need another set of eyes on it that may see something very simple that I have overlooked.


Thanks so much for the help
Shane

Ok firstly you dont need to use external{} on everything it’s mostly used on digest I dont believe you can use it in your code. That’s the main Issue I noticed by roughly looking at your screenshot. If you have any other errors after removing the external{} comment them here

I have tried to write the code without it but it causes a how load of errors. Once I get back into it tomorrow. I can post a pic of what it does when I try and remove this one EXTERNAL.

Like I stated last night, I have got back to my project just now and removed the offending EXTERNAL only and that shot the rest of my code. AS you can see in the pic. I have not dug around yet with this new Verse red madness yet LOL but I’m going to dig in and see if there is a way around that now from this point or do I have to revert back and find a new avenue to try.

I have know got the main section of my code looking good, and error free. I have now created a secondary file to handle to the class tag ownership that reads at the start of the file as that was an error that popped up as part of the change. Now just making a correction inside that file and hopefully all will be good. Fingers crossed. :crossed_fingers:

This is the Main Body of Code where the secondary file is referenced:

Ok so for starters on the pic 1 you don’t really have to make your tag’s as a seperate module also the format is not correct to properly setup gameplay tags I would recommend reading this

As for the 2nd picture As far as I can see your DominationSpawnManager device contains no code and thus is non functional

Thanks for the helpful answer and suggestions. I have done a clean up and and brought the code back together and not listening to other things I had read about Verse, I may be a Game Designer and Level Designer but as you can see Coding is never been my strongest position but I’m working to change that in a big way. So I appreciate the help. I just have one issue with the MODULE, but I’m going to deep dive into TAGS and try to learn where I’m messed up there.



Looking at the last screenshot that part with the module is not in verse I’d recommend asking the Epic Developer Assistant if it could convert it to Verse because that’s not the verse syntax
You can declare modules by doing

MyModule := module:

And public classes can be declared like this:
MyClass<public>:=class(ClassItExtendsFrom){}

1 Like

Thank you again for the great help, I was just finishing up reading and going over all the information about tags and this issue and I wondering if that might be the case with this. I will work with that, and thanks so much for the great help.