Aside from the 200-something warnings generated by ServUO when installing VNc, here are 20 fatal compile errors that prevent users from using VNc with ServUO 51.
I have asked about the changes to the gumps previously, over a month ago, now while I understand that people have lives and are busy, it would be nice to get an opinion on this, because there's no way I'm going to re-write 1000 lines of code to compensate for these changes...
So the questions remain;
Is ServUO going to go back to being user-friendly? -While I realise hard work has been put in to the software, I believe the goal of making things easier for end users has slipped away somewhat...
There are a lot of people using ServUO now, and a good proportion of those users want to use VNc, or have used VNc prior to ServUO 51 and ended up reverting back to stock RunUO in order to support it.
I've simply had enough of support requests flooding my inbox to do with ServUO's and more-so because I feel that this issue has been brushed aside as unimportant, when in actual fact, it's depriving many shard owners of accessing advanced features that do not normally come with ServUO or RunUO.
I understand that it is not the responsibility of the ServUO team to cater for VNc and vice-versa, but I was told this;
Are you *sure* you are "expanding" on things? -All of these issues arise from "rewriting" portions of code to the point where they become incompatible, I've downloaded a copy of ServUO and merged VNc 2.0.0.4 in to it to see the gory details.
If you don't want to revert changes, or make any attempt to keep the code compatible without changing the API, then could you at least consider a preprocessor directive that lets us third-party developers know when our software is being run in the ServUO environment? -A simple #ServUO would suffice, then I'll be happy to re-write my own code to support your new changes, by using preprocessor conditions, for the benefit of anyone who wants to use ServUO and VNc together.
Sorry if I'm being pushy, awkward, anal, or whatever, but you have to understand that, as a lone developer working on a large project, I'd rather spend my time coding towards meeting my goals of new and exciting content/features, rather than coding compatibility work-around's. As time goes on, this is getting more and more frustrating and it sucks having to tell people that they'd have to ue RunUO stock, when they are clearly happy with ServUO.
The differences between ServUO and RunUO are noticeable, you guys have done a great job, but it would be nice if I had the opportunity to communicate effectively with your team in order to remedy these situations before they arise. All I'm asking is a little information and cooperation.
Thank you all.
I have asked about the changes to the gumps previously, over a month ago, now while I understand that people have lives and are busy, it would be nice to get an opinion on this, because there's no way I'm going to re-write 1000 lines of code to compensate for these changes...
So the questions remain;
Is ServUO going to go back to being user-friendly? -While I realise hard work has been put in to the software, I believe the goal of making things easier for end users has slipped away somewhat...
There are a lot of people using ServUO now, and a good proportion of those users want to use VNc, or have used VNc prior to ServUO 51 and ended up reverting back to stock RunUO in order to support it.
I've simply had enough of support requests flooding my inbox to do with ServUO's and more-so because I feel that this issue has been brushed aside as unimportant, when in actual fact, it's depriving many shard owners of accessing advanced features that do not normally come with ServUO or RunUO.
I understand that it is not the responsibility of the ServUO team to cater for VNc and vice-versa, but I was told this;
Any changes to the Gump framework have and will be done in ways that all legacy gumps will work as they always have. We're only expanding on things, not rewriting the whole thing. So nothing to worry about here.
Are you *sure* you are "expanding" on things? -All of these issues arise from "rewriting" portions of code to the point where they become incompatible, I've downloaded a copy of ServUO and merged VNc 2.0.0.4 in to it to see the gory details.
If you don't want to revert changes, or make any attempt to keep the code compatible without changing the API, then could you at least consider a preprocessor directive that lets us third-party developers know when our software is being run in the ServUO environment? -A simple #ServUO would suffice, then I'll be happy to re-write my own code to support your new changes, by using preprocessor conditions, for the benefit of anyone who wants to use ServUO and VNc together.
Code:
Error 203 'Server.Gumps.GumpButton' does not contain a definition for 'ButtonID' and no extension method 'ButtonID' accepting a first argument of type 'Server.Gumps.GumpButton' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\Base\SuperGump_Buttons.cs 82 58 Scripts
Error 204 'Server.Gumps.GumpButton' does not contain a definition for 'ButtonID' and no extension method 'ButtonID' accepting a first argument of type 'Server.Gumps.GumpButton' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\Base\SuperGump_Buttons.cs 82 77 Scripts
Error 208 'Server.Gumps.GumpButton' does not contain a definition for 'ButtonID' and no extension method 'ButtonID' accepting a first argument of type 'Server.Gumps.GumpButton' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\Base\SuperGump_Buttons.cs 106 56 Scripts
Error 220 'Server.Gumps.GumpButton' does not contain a definition for 'ButtonID' and no extension method 'ButtonID' accepting a first argument of type 'Server.Gumps.GumpButton' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\GML\GmlWriter.cs 304 31 Scripts
Error 206 'Server.Gumps.GumpCheck' does not contain a definition for 'SwitchID' and no extension method 'SwitchID' accepting a first argument of type 'Server.Gumps.GumpCheck' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\Base\SuperGump_Switches.cs 87 55 Scripts
Error 222 'Server.Gumps.GumpCheck' does not contain a definition for 'SwitchID' and no extension method 'SwitchID' accepting a first argument of type 'Server.Gumps.GumpCheck' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\GML\GmlWriter.cs 318 31 Scripts
Error 224 'Server.Gumps.GumpCheck' does not contain a definition for 'SwitchID' and no extension method 'SwitchID' accepting a first argument of type 'Server.Gumps.GumpCheck' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\Base\SuperGump.cs 762 65 Scripts
Error 211 'Server.Gumps.GumpImageTileButton' does not contain a definition for 'ButtonID' and no extension method 'ButtonID' accepting a first argument of type 'Server.Gumps.GumpImageTileButton' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\Base\SuperGump_TileButtons.cs 116 66 Scripts
Error 212 'Server.Gumps.GumpImageTileButton' does not contain a definition for 'ButtonID' and no extension method 'ButtonID' accepting a first argument of type 'Server.Gumps.GumpImageTileButton' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\Base\SuperGump_TileButtons.cs 116 85 Scripts
Error 213 'Server.Gumps.GumpImageTileButton' does not contain a definition for 'ButtonID' and no extension method 'ButtonID' accepting a first argument of type 'Server.Gumps.GumpImageTileButton' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\Base\SuperGump_TileButtons.cs 141 60 Scripts
Error 218 'Server.Gumps.GumpImageTileButton' does not contain a definition for 'ButtonID' and no extension method 'ButtonID' accepting a first argument of type 'Server.Gumps.GumpImageTileButton' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\GML\GmlWriter.cs 226 31 Scripts
Error 205 'Server.Gumps.GumpRadio' does not contain a definition for 'SwitchID' and no extension method 'SwitchID' accepting a first argument of type 'Server.Gumps.GumpRadio' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\Base\SuperGump_Radios.cs 87 53 Scripts
Error 223 'Server.Gumps.GumpRadio' does not contain a definition for 'SwitchID' and no extension method 'SwitchID' accepting a first argument of type 'Server.Gumps.GumpRadio' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\GML\GmlWriter.cs 331 31 Scripts
Error 225 'Server.Gumps.GumpRadio' does not contain a definition for 'SwitchID' and no extension method 'SwitchID' accepting a first argument of type 'Server.Gumps.GumpRadio' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\Base\SuperGump.cs 763 62 Scripts
Error 215 'Server.Gumps.IGumpContainer' does not contain a definition for 'X' and no extension method 'X' accepting a first argument of type 'Server.Gumps.IGumpContainer' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\UI\Lists\Menus.cs 211 25 Scripts
Error 216 'Server.Gumps.IGumpContainer' does not contain a definition for 'Y' and no extension method 'Y' accepting a first argument of type 'Server.Gumps.IGumpContainer' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\UI\Lists\Menus.cs 212 25 Scripts
Error 201 'Server.Mobiles.PlayerMobile' does not contain a definition for 'SetMountBlock' and no extension method 'SetMountBlock' accepting a first argument of type 'Server.Mobiles.PlayerMobile' could be found (are you missing a using directive or an assembly reference?) Z:\SVN\ServUO\Scripts\VitaNex\Core\Items\Throwables\Base\BaseDazingThrowable.cs 63 8 Scripts
Error 209 Cannot access protected member 'Server.Gumps.Gump.Entries' via a qualifier of type 'VitaNex.SuperGumps.SuperGump'; the qualifier must be of type 'VitaNex.SuperGumps.DesktopGump' (or derived from it) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\DesktopGump.cs 116 6 Scripts
Error 210 Cannot access protected member 'Server.Gumps.Gump.Entries' via a qualifier of type 'VitaNex.SuperGumps.SuperGump'; the qualifier must be of type 'VitaNex.SuperGumps.DesktopGump' (or derived from it) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\Framework\DesktopGump.cs 116 13 Scripts
Error 217 Cannot implicitly convert type 'Server.Gumps.IGumpContainer' to 'Server.Gumps.Gump'. An explicit conversion exists (are you missing a cast?) Z:\SVN\ServUO\Scripts\VitaNex\Core\SuperGumps\UI\Lists\Menus.cs 216 16 Scripts
Sorry if I'm being pushy, awkward, anal, or whatever, but you have to understand that, as a lone developer working on a large project, I'd rather spend my time coding towards meeting my goals of new and exciting content/features, rather than coding compatibility work-around's. As time goes on, this is getting more and more frustrating and it sucks having to tell people that they'd have to ue RunUO stock, when they are clearly happy with ServUO.
The differences between ServUO and RunUO are noticeable, you guys have done a great job, but it would be nice if I had the opportunity to communicate effectively with your team in order to remedy these situations before they arise. All I'm asking is a little information and cooperation.
Thank you all.
Last edited: