Let us make silverlight maps till html5 is done

New mapmakers are screwed because they don't have any old silverlight maps to make scenarios for. HTML5 is still a work in progress and html5 scenario editor is not out yet. Please let us create new silverlight map for the meantime till html5 is done. Maybe a one week grace period?

Silverlight editor working 99.999999999999999% perfect (no joke i am making a map with it right now)
but yes, scenario editor should be enabled in sl

Furthermore, I consider that NWE must be destroyed

Sounds fair to me. Sorry guys, we've been having some issues getting the editor done. Gotta ask the admins to see what they thinks.

Kirjoittanut j-e-s-u-s, 15.08.2018 at 05:11

Silverlight editor working 99.999999999999999% perfect (no joke i am making a map with it right now)
but yes, scenario editor should be enabled in sl

Scenario editor does work but you need an existing silverlight map to make a scenario for. This is where the problem comes in if you're a new mapmaker without any silverlight maps.

Support

Kirjoittanut Witch-Doctor, 15.08.2018 at 09:29

Kirjoittanut j-e-s-u-s, 15.08.2018 at 05:11

Silverlight editor working 99.999999999999999% perfect (no joke i am making a map with it right now)
but yes, scenario editor should be enabled in sl

Scenario editor does work but you need an existing silverlight map to make a scenario for. This is where the problem comes in if you're a new mapmaker without any silverlight maps.

i see, then full support

Furthermore, I consider that NWE must be destroyed

Yeah , i agree and i have suggest it before , but allow as to create new maps and scenarios in the old editor

Support!

Indeed support

PLEASE DO THIS PLEASE

PEOPLE ARE GETTING ANGRY WE HAVE BEEN WAITING

This is very possible you just need an old map to map make if you dont have one you can ask someone that does to make you a collaborator and let you make the map

Kirjoittanut Brsjak, 16.08.2018 at 19:00

This is very possible you just need an old map to map make if you dont have one you can ask someone that does to make you a collaborator and let you make the map

Lol but then you dont own the map and you're trusting the other person not to jew you out of your work.

Had a talk with the admins about this. This is not going to happen, I'm afraid . This also means that we're going to block the ability to create new scenarios once the new scenario editor is out. My advice would be for everybody to help us making more tests to it on the test server before we release it to live, since we want to avoid having a half-backet product in the live server.

Kirjoittanut clovis1122, 19.08.2018 at 16:03

Had a talk with the admins about this. This is not going to happen, I'm afraid . This also means that we're going to block the ability to create new scenarios once the new scenario editor is out. My advice would be for everybody to help us making more tests to it on the test server before we release it to live, since we want to avoid having a half-backet product in the live server.

Why cant we delete saved borders in html5. Why can't we even click on it like silverlight.

Kirjoittanut clovis1122, 19.08.2018 at 16:03

Had a talk with the admins about this. This is not going to happen, I'm afraid . This also means that we're going to block the ability to create new scenarios once the new scenario editor is out. My advice would be for everybody to help us making more tests to it on the test server before we release it to live, since we want to avoid having a half-backet product in the live server.

I'd like a reason why they refused to do this.

Kirjoittanut Witch-Doctor, 19.08.2018 at 19:21

Why cant we delete saved borders in html5. Why can't we even click on it like silverlight.

Thought you could.

Kirjoittanut Guest, 19.08.2018 at 20:27

I'd like a reason why they refused to do this.

It's cruel, but we need to get the editor stable and functional and for that we need the people to use it. The fear is that if we don't block SL then almost nobody will feel comfortable switching over to HTML5, which generates less feedback and less bug reports.

The Map Editor is supposed to be complete. I think that the current bugs (some of them breaking like the cloning issue) leaked because we did not tested it well enough when it was in the Test server. So I think that the decision of blocking new maps in SL, although with drawbacks, was proven to be correct.

The scenario editor is on the Test Server and I've only got a couple of people to test it (Helly, Tunder, j-e-s-u-s and a couple more). We've found many bugs related to the Map Editor but I've see nothing related to the Scenario Editor. I guess that when we release it to LIVE all the issues and god know what type of bugs will appear.

Note that I'm not blaming the community for not testing the features. From the programmer perspective you usually write unit or integration tests that runs every time that you try to push a new change, to make sure that everything's still working. In other places they either pay for QA services or they have their own QA team. Companies like Facebook even have bounty programs. We don't have cash, so asking the community to test the changes before we release them to LIVE is our best offer right now...

Clovis1122 do u need more people to test?
can you direct me to the test server pls?

Kirjoittanut Apeman, 20.08.2018 at 01:57

Clovis1122 do u need more people to test?
can you direct me to the test server pls?

https://atwar-game-test.com/

Kirjoittanut clovis1122, 20.08.2018 at 01:24

Kirjoittanut Witch-Doctor, 19.08.2018 at 19:21

Why cant we delete saved borders in html5. Why can't we even click on it like silverlight.

Thought you could.

Kirjoittanut Guest, 19.08.2018 at 20:27

I'd like a reason why they refused to do this.

It's cruel, but we need to get the editor stable and functional and for that we need the people to use it. The fear is that if we don't block SL then almost nobody will feel comfortable switching over to HTML5, which generates less feedback and less bug reports.

The Map Editor is supposed to be complete. I think that the current bugs (some of them breaking like the cloning issue) happens because we did not tested it well enough when it was in the Test server. So I think that the decision of blocking new maps in SL, although with drawbacks, was proven to be correct.

The scenario editor is on the Test Server and I've only got a couple of people to test it (Helly, Tunder, j-e-s-u-s and a couple more). We've found many bugs related to the Map Editor but I've see nothing related to the Scenario Editor. I guess that when we release it to LIVE all the issues and god know what type of bugs will appear.

Note that I'm not blaming the community for not testing the features. From the programmer perspective you usually write unit or integration tests that runs every time that you try to push a new change, to make sure that everything's still working. In other places they either pay for QA services or they have their own QA team. Companies like Facebook even have bounty programs. We don't have cash, so asking the community to test the changes before we release them to LIVE is our best offer right now...

You want to know the real reason people don't test? It's because anything they make on the test server will be deleted once released and they lose everything they worked on.
Clovis I just started map making, and I can tell you that losing your progress is the most frustrating thing imaginable. Nothing kills your motivation more than working on something then having it completely removed and you have to redo it all over again. Imagine spending 2 hours writing some code and then your program (ex. Visual Studios) crash and you lose EVERYTHING. You want to just turn off the computer and go away for a few days.

As for the deleting borders thing. If you delete a country, the border of that country remains and cannot be selected or deleted. You can't even assign it a different country. Forcing to delete it will cause a pathway error.
This is even worse for no-go zones. You can't even select it to delete it once you've made it and saved.
Tunder and I have been trying to work out this bug so you can ask him for details.

Kirjoittanut Witch-Doctor, 20.08.2018 at 02:39

You want to know the real reason people don't test? It's because anything they make on the test server will be deleted once released and they lose everything they worked on.

Alright I agree with everything else, but here I'd say the test server wasn't intended for permanent work, whatever is there can be erased the next day. I think it's fine if we make tests at a small scale (e.g creating a new scenario with 2 countries to see if everything works).

Let me know when you guys have the details of the bug so that I can work on it.

Kirjoittanut Sascha, 20.08.2018 at 01:58

Kirjoittanut Apeman, 20.08.2018 at 01:57

Clovis1122 do u need more people to test?
can you direct me to the test server pls?

https://atwar-game-test.com/

thanks Sascha
ive passed it on to the Clan.

Kirjoittanut clovis1122, 20.08.2018 at 01:24

Kirjoittanut Witch-Doctor, 19.08.2018 at 19:21

Why cant we delete saved borders in html5. Why can't we even click on it like silverlight.

Thought you could.

Kirjoittanut Guest, 19.08.2018 at 20:27

I'd like a reason why they refused to do this.

It's cruel, but we need to get the editor stable and functional and for that we need the people to use it. The fear is that if we don't block SL then almost nobody will feel comfortable switching over to HTML5, which generates less feedback and less bug reports.

The Map Editor is supposed to be complete. I think that the current bugs (some of them breaking like the cloning issue) leaked because we did not tested it well enough when it was in the Test server. So I think that the decision of blocking new maps in SL, although with drawbacks, was proven to be correct.

The scenario editor is on the Test Server and I've only got a couple of people to test it (Helly, Tunder, j-e-s-u-s and a couple more). We've found many bugs related to the Map Editor but I've see nothing related to the Scenario Editor. I guess that when we release it to LIVE all the issues and god know what type of bugs will appear.

Note that I'm not blaming the community for not testing the features. From the programmer perspective you usually write unit or integration tests that runs every time that you try to push a new change, to make sure that everything's still working. In other places they either pay for QA services or they have their own QA team. Companies like Facebook even have bounty programs. We don't have cash, so asking the community to test the changes before we release them to LIVE is our best offer right now...

I tested the scenario editor pretty extensively it seems like its in good shape. That's why I did not send you any bug reports on it because everything I thought was required of it seems to work accordingly.

Kirjoittanut clovis1122, 20.08.2018 at 03:44

...

If you have troubles finding players to test the editor you could host a "bug bounty event" with small rewards for every new bug someone finds.
Should help to catch the bugs faster if it's not already to late for that.

Kirjoittanut Sascha, 20.08.2018 at 06:52

Kirjoittanut clovis1122, 20.08.2018 at 03:44

...

If you have troubles finding players to test the editor you could host a "bug bounty event" with small rewards for every new bug someone finds.
Should help to catch the bugs faster if it's not already to late for that.

the issue seems to be clovis thinks the map editor is almost fine and its the thing that's still riddled with game breaking bugs, to my knowledge after my testing the scenario editor they are holding back waiting for bug reports seems to be functioning properly.

Kirjoittanut Helly, 20.08.2018 at 06:59

the issue seems to be clovis thinks the map editor is almost fine and its the thing that's still riddled with game breaking bugs, to my knowledge after my testing the scenario editor they are holding back waiting for bug reports seems to be functioning properly.

sure they could do this for both editors

If you're desperate enough for testers, I can start messing with it on Thursday.

I do not personally believe, as I've stated previously, that the switch to HTML5 was smooth or necessary when it is and will continue to be the inferior version of the game by far. I'm not blaming you for anything Clovis considering you're new to the team and have been a chill dude for years, but Protobytes seriously needs to get its shit together. Why wasn't AW ported into Unity and packaged onto Steam? It's written in C#, no? Fuck you could even use XNA and have a package ready product in a few weeks, not two years! I mean, I've been releasing horrible indie games on Steam and other platforms for years; if they fear doing this then rest assured, it's a very simple process.

As well: the old argument "Being on a browser makes Afterwind more accessible" is redundant and outdated now that this game has approximately 150 daily active players and hasn't received any major activity in years. This game literally has to rebrand itself (again) and launch onto a user friendly platform of it doesn't want to continue falling off the map into obscurity.

But yes, if it makes a difference I'll help test it too.

Kirjoittanut Sascha, 20.08.2018 at 06:52

Kirjoittanut clovis1122, 20.08.2018 at 03:44

...

If you have troubles finding players to test the editor you could host a "bug bounty event" with small rewards for every new bug someone finds.
Should help to catch the bugs faster if it's not already to late for that.

The reward should be an hour of east eu duel training with the legendary Sascha ukr mentor.

Kirjoittanut clovis1122, 19.08.2018 at 16:03

This also means that we're going to block the ability to create new scenarios once the new scenario editor is out.

sigh